Mailcoach [1] has a clean UI and extendable automations, but self-hosting is not free of charge.
2,166 karma · joined January 5, 2017
https://bunny.net/blog/introducing-hop-js-a-safe-free-cdn-fo...
Just wanted to add that DMARC isn't really about the DKIM signature itself; it's about whether the domain in RFC5322.From aligns with either SPF or DKIM.
So if SPF is aligned, DMARC will pass even if DKIM fails.
I used to ask an LLM for executive summaries by pasting an article URL into a fresh conversation each time. Now, I don't open a new thread or even write a follow-up comment on the same thread. Instead, I simply edit the prompt (of a single thread) with the new link.
This doesn't apply to certain special posts, such as "Ask HN: Who wants to be hired?"
Comments are always editable there.
RSS is far better than a (digest) newsletter; you can browse individual posts at your own pace, keep some unread for later, and revisit them across sessions.
With newsletters, you either read the whole thing in one sitting or leave the email unarchived forever.
If only every newsletter had an RSS feed. But of course they don't - can't show you ads!
I really appreciated the folks who did reach out - some of whom I honestly didn't expect to. But I was deeply disappointed that others I've worked more closely with didn't bother. I was already in shock, and that just made things worse.
Hard to imagine; you don't really get it until it happens to you - hopefully never.
I doubt it's feasible without human curation (of the content produced) in the loop - at least not with the current state of AI. Also, writing docs should be a team practice. A tool like this could actually cause more harm than good if engineers lean on it too heavily. I mean, interviews capture a moment in time; without regular updates, context will drift.
More importantly, this leans hard on human memory, and most people have terrible ones. That can be partially fixed by prompting to explain why they made specific tradeoffs proactively. For example, the LLM could detect that a tradeoff was made and then ask: why this one? And potentially list the alternatives.
It's a cool idea. You can build a proof-of-concept in a few days with AI prototyping tools.
I'll try to force light mode initially and will definitely fix the dark mode later. Thanks a lot for flagging this!
Feeds are a user right, not a publisher favor. In that spirit: I recently built RSSible - a tiny tool that lets you turn any webpage into an RSS feed via CSS selectors. I've built this for myself; already using it for HN, Product Hunt, tldr.tech, r/science, IMDb latest shows, RubyOnRemote, and many more.
It's still early, but if anyone here is curious to try or test, I'd love feedback. (You can see live demos on the site)
RSSible: https://rssible.hadid.dev/
Don't get me wrong, I use catch-all too (don't tell spammers).
Next time a legit email ends up in your spam folder, use this tool to figure out why: https://mxtoolbox.com/EmailHeaders.aspx
I've had a few cases myself, and it's always been the sender's fault.
Grey listing doesn't scale; not for me.
With Gmail, you can configure an external SMTP server using "Send mail as" setting. Super convenient. Tons of mail services offer a generous free tier for personal use (e.g., Mailgun 100 emails/day).
It's not really worth paying just to send a few personal emails from @yourdomain.com each month.
If their DMARC alignment relies on SPF only, it will break. But if it relies on DKIM (far more common) or both SPF and DKIM (best practice), forwarding won't cause any issues.
If your email breaks when forwarded, your setup is broken. Tons of people use Cloudflare Email Routing or similar services; you must account for them.
That being said, I forward mail addressed @mydomain.com to my Gmail, and I've had a couple of cases where legit messages landed in spam because it was SPF-aligned only.
Outbound emails sent via "Send mail as:" using SMTP remain unaffected.
[1] https://www.sciencedaily.com/releases/2025/09/250927031224.h...