Earlier quoted context omitted.
No. You need only one, either Atom or RSS.
I believe you can also however add on to Atom/RSS. Many feed readers now also support the WebSub [1] standard which allows them to receive instant push notifications of new articles. It kinda speeds up getting things as you don't have to rely on exclusively the pulling model. Sites like WordPress, Blogger, FeedBurner, Mastodon, and Friendica I believe are all examples of sites that support it. It basically extends At…
Kill the Newsletter – Convert email newsletters into Atom feeds
121–127 of 127 posts
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#122Earlier quoted context omitted.
You have to view and manage and then delete them. 99% of my inboxes are emails from non-humans. I'm ready to stream them like RSS or Twitter.. and catch the ones I care about.
You don’t have to do those things. The earth will not stop if there are unread emails in your inbox.
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#123It’s a nice surprise to check HN and have my project featured on the front page. Thanks polm23 for posting and everyone else for the nice words!
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#124Nice idea. Related - Is there anything that can add the select number of Twitter accounts I want to follow to this Atom or RSS feed? Without exposing myself to toxic replies, toxic suggested tweets and toxic trending topics? I've thought for years there should be something like that. Presumably it's a grey area with APIs or scraping.
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#125It’s a nice surprise to check HN and have my project featured on the front page. Thanks polm23 for posting and everyone else for the nice words!
Seems it'd take significant costs to run it, how do you still manage to do that?
Also, you can support me: Recurring (Patreon): https://patreon.com/leafac / One-time (PayPal): https://paypal.me/LeandroFacchinetti
In terms of server costs, it all runs smoothly on a $6/month DigialOcean droplet. Even when I end up on the front-page of HN (it’s the second time this happens). And there’s also the ~$10/year for the domain.
There’s actually a fun story behind this: The biggest constraint is bandwidth (~500GB/month). I was using S3 and at some point that’d amount to $50/month. But DigitalOcean droplets give you 1TB/month, so to save money I rearchitected the whole thing to just use the filesystem. It turned out to be simpler and nicer to maintain, too. Fewer moving parts.
Fun stuff…
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#126Earlier quoted context omitted.
One of my favorite hacks: I made a google appscript that scans a list of RSS feeds to email weekly digests. Surprisingly simple, and much more useful then running a separate RSS reader in my opinion. I have to confess: little automations like this with low barrier of entry is where I find most value in tech. Simple and practical.
I use a self-hosted RSS reader, I'm curious if you could use something like that and have some email digests generated from that. I know tt-rss supports sending email digests. You could set it up to check sites on a less frequent schedule and then the setup sounds just like what you're talking about. You may be fine with your solution so this comment is more geared towards others who are interested in a similar solut…
The "email digest" approach is basically DIY newsletter. While this approach works for me, it may not work well for others. YMMV.
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#127I think we should go the opposite way. I think we should push more onto email. email is pretty ubiquitous. Nearly everyone online has email. It's as close to universal as anything else for accessing people. Instead of having a dozen different chat apps, push chats to email. Instead of a half dozen Slack wannabe apps, push all that to email. We should expand the email protocol to support that.
Two reasons why I don't think this is a good idea: 1. Mixing different applications in one inbox would be a mess for a lot of people (e.g. your IM would drown out important work email) 2. Privacy - avoiding unique online identifiers when they're not needed is a good idea