Bulk Emails from a chat input — without Redis, queues, or worker services
A developer created a feature for their portfolio site that allows users to send bulk emails to recruiters directly from a chat input. The system generates tailored emails and streams progress in real-time without using traditional background processing tools. This approach aims to provide a more controlled and personalized experience compared to typical automated job application tools.
- ▪The feature enables users to paste recruiter emails and job descriptions into a chat box for bulk emailing.
- ▪It utilizes Next.js on Vercel and Neon Postgres without relying on Redis or worker services.
- ▪The system processes emails in real-time and provides live updates in the chat interface.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/roshan_ican/bulk-emails-from-a-chat-input-without-redis-queues-or-worker-services-4oak |
| Publication time | Sun, 17 May 2026 14:37:16 +0000 |
| Retrieval time | 2026-05-17T14:52:13.162Z |
| Last seen | 2026-05-17T14:52:13.162Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 4CP558Mvlfut |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 611585) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } 〽️ 𝙍𝙤𝙨𝙝𝙖𝙣 Posted on May 17 Bulk Emails from a chat input — without Redis, queues, or worker services #ai I built a feature into my portfolio site that lets me paste a list of recruiter emails and a job description directly into a chat box. Once I type my unlock passphrase, it automatically: generates a tailored email for each recruiter, attaches my resume, sends the emails, and streams live progress back into the same chat bubble. The fun part is the architecture behind it.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
