Kill the Newsletter: Convert email newsletters into Atom feeds
kill-the-newsletter.com
kill-the-newsletter.com
It's less clutter. No string attached. Formatting is better.
And yet.
Even youtube channels have rss, and it's advertised... nowhere.
I don't feel like I present the email option with any more prominence either. Interesting user behavior.
I really don’t get it. If you want an RSS just use that.
But i guess people are used to not have an RSS available so they don’t even bother checking.
At some point I just have to assume that people have motives and not worry about it.
(In the case of newsletters → feed → email it may be avoiding giving our your email address?)
It would be awesome if KTN provided an easy way to upgrade/redirect at KTN feed to an original feed, if one exists. I'm not sure how conveniently redirects would be handled by RSS clients...
I know some advantages of email:
* I already have an email reader that I use every day.
* The newsletter was designed for email, so it'll probably look better.
But what do I get by going with Atom?
that is a point for email.
I find RSS/Atom more a-sync while e-mail tends to be more interrupt-driver (even with filters and folders (or *hawk*spit* Gmail's tags)).
> But what do I get by going with Atom?
Not having your e-mail address yet one more database?
I would, however, subscribe to an RSS feed.
https://github.com/radically-straightforward/radically-strai...
import server from "@radically-straightforward/server";
import * as serverTypes from "@radically-straightforward/server";
import sql, { Database } from "@radically-straightforward/sqlite";
import html, { HTML } from "@radically-straightforward/html";
import css from "@radically-straightforward/css";
import javascript from "@radically-straightforward/javascript";
import * as utilities from "@radically-straightforward/utilities";
import * as node from "@radically-straightforward/node";
import caddyfile from "@radically-straightforward/caddy";
import * as caddy from "@radically-straightforward/caddy";Worth it imo, to just have it all in one place.
Imagine I'm a mischievous newsletter publisher who doesn't like the idea for some reason: What prevents me from finding all subscribers with XYZ@kill-the-newsletter.com addresses, and then deleting all of them by visiting https://kill-the-newsletter.com/feeds/XYZ, or reading all other newsletters they are subscribed to by checking out https://kill-the-newsletter.com/feeds/XYZ.xml ?
rss2email was originally written by Aaron Swartz.
I had the thought that maybe it would actually be neat to go the other direction, to be able to subscribe to feeds, but have new posts emailed like newsletters, but I never tried that out.
For a time, I used Android. The absence of a decent RSS reader on android made me jump back to iOS. My smartphone OS choice came down to being able to read newsletters as feeds.
I even wrote a PSA on my blog to let them know they don’t have to do it and yet they do it anyway. I guess some people just find it convenient.
That’s what I really want
this is already way more complicated than "moms" want to do: generate a new email, use that email in this new form, get a feed reader (wtf is that mom says). while this is perfectly fine for power users, it just makes me smile how often we forget there are a far larger number of non-power users that are out there
Non-technical users can simply subscribe to the newsletter with their email address. If they don't understand what this project is about, they probably don't need and don't want it.
Users that prefer RSS over email use kill-the-newsletter for outlets that don't offer RSS.
And from what i've read, even the technical users prefer it most of the time.
So who is it marketed towards with a title of Kill The Newsletter?
I have to monitor my phone, Teams, Slack, email, and some other bespoke notification channel my employer invented. It's too much, I don't want more. As much as possible I try to get stuff pushed into email, as once it's there I can interact with the message in the same way, no matter the source.