I think every email newsletter should offer an RSS feed as a matter of course. With all of ours, you just stick /rss on the end of the URL and off you go :-) e.g. https://javascriptweekly.com/rss With that said, I think there are some interesting opportunities for turning certain types of email into RSS feeds generally . I think it'd be really cool to have all of the random and very low priority emails landing at the…
Another HN today is talking about tracking pixels in newsletter mails so the sender can evaluate effectiveness. I bet a general mail-rss bridge with many subscribers would make them sad.
Kill the Newsletter – Convert email newsletters into Atom feeds
101–110 of 127 posts
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#102I think it came down to personal preferences. I tried to use RSS but it's yet another app that I cannot form a habit to check it. Plus I like the personal look and feel of each email newsletter I got. I instead of relying on email as a real time news feed. But getting too many emails I have to category and make miss some exciting development news. I though of this, why not combine all of the newsletter and display th…
But for me, the more import aspect is being in charge when to use a tool than what the tool is and having habits around it.
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#103Earlier quoted context omitted.
Another HN today is talking about tracking pixels in newsletter mails so the sender can evaluate effectiveness. I bet a general mail-rss bridge with many subscribers would make them sad.
I seem to recall years ago google was looking to make that sort of thing useless because they would always download all images in an email and serve them from their cache... wonder what changed?
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#104I think it came down to personal preferences. I tried to use RSS but it's yet another app that I cannot form a habit to check it. Plus I like the personal look and feel of each email newsletter I got. I instead of relying on email as a real time news feed. But getting too many emails I have to category and make miss some exciting development news. I though of this, why not combine all of the newsletter and display th…
RSS being pull and not push is a great feature IMO. You check up on your feeds when you want to, if you never do it might not really be worth your time or you might not enjoy it. If you really want some kind of reminder then some readers like tt-rss can send daily digest.
I actually really like the idea of being able to convert newsletters into RSS feeds. I have a decent amount of newsletter I currently get and for a lot of them the only reason I have them in newsletter form is because they offered no RSS option. So if I wanted to stay up to date one of my only options was newsletters.
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#105Earlier quoted context omitted.
I've been using NewsBlur since G killed Reader. Great service!
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.
You may be fine with your solution so this comment is more geared towards others who are interested in a similar solution.
I am sure managed RSS platforms also offer some kind of email digest if you don't want to self-host.
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#106Aside: a question for proponents of syndication (e.g. Atom, RSS) – as a publisher, are there other formats that should be investigated?
No. You need only one, either Atom or RSS.
It basically extends Atom/RSS to have another feature. Clients that don't support it can still pull like normal. Wikipedia summarizes the technology a bit nicer than the first link [2]
[1]: https://www.w3.org/TR/websub/ [2]: https://en.wikipedia.org/wiki/WebSub
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#107Nice 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.
I’m sure there's a way to do it but Twitter dropped RSS/Atom support from their API in 2012 [1], so it would require scraping or using some sort of other endpoint-managed control of the feed. There have historically been usage limits on how many tweets you could retrieve without paying, but I’m not sure how much that has changed since Twitter overhauled its API last year. It’s a shame that many of the tools and featu…
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#108Earlier quoted context omitted.
I guess I've just never really considered my email address as some kind of secret thing that warrants a privacy concern.
Neither do I, really, but I would be concerned about newsletter hosts being able to build a profile of my interests based on what I'm subscribed to. If I can just use Atom/RSS over HTTP instead I can avoid that easily.
Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#109Re: Kill the Newsletter – Convert email newsletters into Atom feeds
#110Earlier quoted context omitted.
Not exclusively relevant to a developer. I have one or two things in my feeds that can’t be expressed in RSS, such as HTML markup in my titles (which I use for , and I think ). I also have angle brackets in a title, which I would be afraid to do in RSS because I’m confident that some clients would butcher it, and they wouldn’t even be wrong since RSS don’t care.
This, to me, makes me ask what the purpose of a feed even is. If it's to deliver data then RSS, Atom, JSON, or YAML shouldn't make any different at all. But if it's to deliver data and markup... now we're making decisions a client could override at best or result in unreadable/a11y unfriendly content at worst. Maybe it's just me but I've never considered the feed as a place to be putting markup but even if we want to…
RSS doesn’t say what format any of its content is in. You have to guess if it’s plain text or HTML. This can easily go wrong. The result is that you can’t trust the handling of characters like in titles or in supposedly-plain-text descriptions in RSS feeds.
Seriously, just use Atom.