So two big questions:
- If clients are now integrating #RSS with the #SocialWeb, when are they going to start integrating #email and #InstantMessages too?
- At what point do these clients stop being clients and start being #webfeed browsers?
So two big questions:
@David If the idea is to be able to notify your users of new articles whenever they are released, I would instead encourage you to promote the use of #webfeed #syndication protocols like #RSS and #Atom, which provide the same benefit without harming the privacy of your users nor requiring any potentially hazardous permissions on their machines.
@jimmylittle @Green_Footballs If the full post fits in an #RSS / #Atom #webfeed reader and you've got such a feed setup, there might be no reason for anyone to visit the site directly for them which would also skew the statistics.
@arkd #MiniFlux for reader and go to https://rssproxy-v1.migor.org/ to create a feed out of almost every website #RSS #WebFeed #Feed #FeedReader
@toady Wikipedia does offer atom feeds for its front page (https://en.wikipedia.org/wiki/Main_Page) news, although it doesn't advertise them in the UI.
@aras miniflux, independent and open source #RSS #FeedReader #WebFeed
Some of the #Fediverse software is not setting #CORS headers for their #Atom & #RSS #WebFeed
They should. But they aren't.
...
Adding #CORS headers makes it so Atom & RSS WebFeeds can be pulled at the client end (and doesn't have to run through a server).
If you care about #privacy , you should care about this. As not having it have to run through a server protects privacy more.
...
For example, the Atom & RSS WebFeeds should have this CORS header:
Access-Control-Allow-Origin: *
I ranted somewhere in march about email newsletters. Decided to write about it back then, but never published. Until today:
https://shivering-isles.com/Why-web-feeds-are-better-than-newsletters
It's definitely not the ultimate truth but hey, I think it's somehow productive ranting :X