Increasing the surface area of blogging
tomcritchlow.com
tomcritchlow.com
> The problem with feeds is that they render in the browser like a bunch of code. They’re not at all user friendly.
I read this and was thinking oh no! No! You can absolutely make it readable!
And then it turned out he linked to mine. :D
If you want something a bit less over-the-top and more sensible, Ton has one: https://zylstra.org/opml/tonzylstra.opml
Have mutable design on immutable data is awesome for long-term concerns. And having the data raw!
In the early days of XSLT client side support was limited. IE still dominated the web in the early 2000s. IE 5/5.5 only supported the XSLT working draft and made up more than half of IE's market share. In 2001 if you were excited about client side XSLT it was only available to fewer than half of your visitors at best.
You could do XSLT on the server side and spit out HTML but that was just one of several ways of converting your raw data to HTML. For most developers it was easier to go from a SQL database through ASP, PHP, or whatever to HTML.
So in the early days it didn't gain much momentum. By the time browsers supporting client side XSLT were dominant AJAX was pretty well established as the new hot thing. JavaScript was ingesting XML with little interest in having the browser handle it directly.
The tooling in the early days wasn't that good either. Dreamweaver 8 added support around 2005 but I think by then the AJAX train had sailed. Before then developing an XSL stylesheet meant a lot of rerunning a processor and reloading a page. For the same effort you could just do the work in PHP or ASP and get more programmability.
Today everyone has a browser capable of doing client side XSLT very efficiently but XML is seen as old and crusty. No one wants to go back and learn XSLT because most developers seem to have doubled down on JavaScript.
Since XML as an endpoint format has been ignored for so long I would bet it doesn't have a good SEO story. While it can carry all the metadata Google or Facebook wants, if they don't crawl it then it doesn't matter.
> Error loading stylesheet: An unknown error has occurred (80004004) > https://maya.land/assets/opml.xsl
OMPL URLs hosting lists of feeds should be automatically updated across feed readers following an OPML feed. You should be able to “subscribe” to OPML feeds the way you subscribe to RSS feeds.
The only reader I’m aware that supports this is Tt-rss. FreshRSS plans to support it soon: https://github.com/FreshRSS/FreshRSS/issues/4191
I think this ability will allow for a lot of important, and cool usecases (your follow list on Twitter/YouTube/GitHub) is just an OPML feed that you subscribe to.
Related: I've only just now signed up for a newsletter on Substack and it turns out SS is basically a feed reader. Like - the iOS app is literally a feed reader. A list of articles, the concept of what is read vs unread, a vague stab at a discovery mechanism. It's Feedly, only not as good.
I hadn't realised how much hype surrounds so little that is actually new...
The (arguably) most popular blogging system ignoring OPML meant feeds were much rarer than RSS. The rarity of OPML feeds kept them from getting any native browser support. Most of the time you only see them as a way to import/export a list of feeds from dedicated RSS readers.
I know there is an rss-activitypub server out there. Are there other projects/solutions like that? Something that'll work for static blogs?
And it offers full OPML import/export. I.e. you can come and go whenever you want. The project is https://lenns.io
If your target is just offering an aggregator like "Google News for the content you want", well, I can understand but for people who want to control their source of information, reducing propaganda and crap of modern websites/services, it's not a real option...
Not sure if thats true but it sounds true so maybe it's true.
PS I love RSS, it plays by Tim BL's rule of simple rules make complex ecosystems.
This wasn't always the case.
https://news.ycombinator.com/item?id=18202028
https://www.gijsk.com/blog/2018/10/firefox-removes-core-prod...
I don't think Chrome ever supported RSS, though.
and you want to be able to post a long form blog and "collect" micro posts of your and maybe others into it as well.
Clicking on that with Safari has the first row flickering a lot for some reason.
At that point arrive the discoverability problem: how to find good contents.
IMVHO the sole way is the classic Usenet: a public aggregator no one really own of cohorts of people with similar interests (groups) BUT not limiting them to any particular cohort (subscribe groups you like at Reddit we divide users by, at Facebook by, ...) because those groups are formed out of their posters for their poster interests NOT for some corporate/business purpose.
Essentially: the classic usenet + the classic web 1.0. The web part is just a way to see content and decide, RSS is the mean to read it once selected, ngs to follow changes. Anything else I know/see is by large far less effective.
Also how to handle spam, thats been a killer for usenet lately
Ah, but USENet is decentralised, Reddit is not.
> Also how to handle spam, thats been a killer for usenet lately
Last time I checked, the spam still being posted on USENet is Zombie-spam by long forgotten bots. A strong kill-list in a good client should easily minimise that problem.
There has been a revival of USENet by the smolnet and Web 1.0 people - some of the groups are active with almost no spam.
Also on Usenet scoring, killfiles etc are yours so you can ban my posts because you do not like them, but others will see them, while on Reddit if a mod ban someone it's for all or no one.
Spam on usenet was and issue because at that time antispam was not good as today, today we can filter spam enough, if just there is enough interested public. So far usenet is far from being dead, it's used by few to share mostly pirate binary contents like Radarr/Lidarr/Sonarr series. With commercial orgs. That's not usenet of course, but that's still possible and it's useful enough to prove it's strength and flexibility.
Just see another example: Popcorn Time. A super-success people have abandoned simply because instead of install an app most prefer going to streaming websites, not really because of legal actions or ban. ZeroNet is built on the same principle, it's legal, made to share websites, nearly no one seems to be interested again because they can find some place to write text hosted by someone else. Or: the issue is cultural not technical. People en masse do not comprehend the meaning of freedom so they ignore it until it's tangibly lost and at that time it's too late.
Against such phenomenon there is no technical solution, only social ones...