Why your blog still needs RSS
journal.paoloamoroso.com
journal.paoloamoroso.com
For example, I wrote a feed generator that targets a specific software package release page. It scrapes the page and converts it to an Atom feed [1]. I then wrote a matching systemd service, which triggers the scraper once a day [2] and writes it to a file, no hosting required. My RSS reader is pointed to that file.
[1]: https://github.com/claui/release-feed-mediola/blob/fca39e897...
[2]: https://github.com/claui/release-feed-mediola/blob/fca39e897...
I am able to get a lot of generally unavailable feeds using https://github.com/RSS-Bridge/rss-bridge running on my server. Perhaps this code could be someday brought in as a catch-all last resort.
Good question.
Maintaining a server feels like a chore to me, nor am I willing to pay for cloud services as long as a local Python script (plus systemd unit plus PKGBUILD) will do.
Besides, this particular target site is extremely niche. So I figure it’s probably not worth the burden to port my code and contribute it to rss-bridge, let alone for the upstream folks to maintain it.
There is not usually support in reader software though, so a little scripting is still required, unless they use a Git hosting platform that exposes those as RSS (GitHub and GitLab do).
I'd post a comment pointing this out, but a 'Discuss' link to a 3rd party site, not part of the blog, remark.as tells me I need to login to write.as
At this point I conclude the writer's failing to drink their own coffee let alone eat any dog food.
I'll definitely bring this feedback to the Write.as developer, thanks. I also added a link to the RSS feed to the blog's About page.
https://journal.paoloamoroso.com/about
I think I agree with your overall point, but it is mentioned on the site where to find the RSS feed.
There is lots of interesting content out there. For an individual to develop themselves, they need free reign to information. RSS allows and enables an individual's learning about reality (on the web).
The reverse is mediated information. Corporations/governments would rather steer you to where they want you to go - to the sandboxed areas, the paddling pools of the internet. Many people think the internet is just youtube, facebook, instagram and twitter. These are social mediating platforms.
RSS is probably the most anarchic technological development of the internet we have had. More important than crypto or mobile phones. Continued unmediated access to the information you are interested in, without being distracted is what every individual should be striving for.
No wonder Google bent over backwards to try to kill it.
This is a negative way of looking at the reality- rarely mentioned in articles about RSS: RSS may be "dead-" however, there are many mobile apps that are fed by RSS feeds. Having one may risk some loss of revenue- but you'll lose even more by simply being omitted from these aggregator apps, all of which (i mean, ok.. probably all) link back to the source website. That's a huge potential for added exposure and revenue.
Fowler's blog does this (or maybe Feedly does?) but not many others, afaik
People who think like this need to get over themselves.
Worst of all, the lazily copied versions of my work introduce serious errors because the authors don't know what they're talking about.
Oh and some copies are used for phishing scams, so that's another concern.
This is what stops me from open sourcing the whole website, since it's just Markdown. It would be good to open it up to contributions, but the website is already copied enough as it is.
I understand that but lack of RSS is not going to prevent that. It's barely a roadblock for those who steal.
Publishing your website at all does that. Feeds are not at all required to scrape websites.
This has nothing to do with "web scraping". Scraping means downloading. What you are complaining about is copyright infringement: they are downloading your web pages and re-uploading them elsewhere. That's completely unrelated.
So it's fine if someone took the fruits of your labor and sold it without permission?
This isn't even true. If you publish information on the web, then people are going to download it to their computers. That's the whole point of providing it. When someone accesses your website, your web server actively responds with the web page.
Complaining about people doing this is like complaining that someone asked you for money and then you gave it to them. Yeah, they asked, and you gave it to them? If you don't like it, don't give it to them.
In other words, if you don't like people scraping your website, don't give them your web pages when they ask for them.
It's thanks to the original HN thread where people linked their blogs and then someone crawling them for RSS feeds to make an OPML summary, I just get the posts daily now (after getting the list of feeds from GitHub).
I actually wrote about some of the challenges of doing that on my own blog, in the "Ever wanted to read thousands of tech blogs? Now you can!" post: https://blog.kronis.dev/articles/ever-wanted-to-read-thousan...
https://til.simonwillison.net/django/building-a-blog-in-djan...
Atom support was easy, thanks to Django's built-in syndication library (a feature for over 18 years at this point https://github.com/django/django/commit/944de9e9e638bc239b03...)
[1]: https://du.nkel.dev/
It's like an SSG where you can write templates with modern components frameworks, and write content in MD / MDX. No JS is shipped by default, but you can opt in to it for interactivity.
There are many high-quality templates, but making your own custom styling and layouts is easy, and you can write CSS in whatever way you like.
MkDocs and Jekyll are more for docs in my opinion, but Hugo is pretty good if you hate javascript.
I would recommend Astro over 11ty 100% of the time, though. Both are JS, with slower build times etc than with Hugo, but Astro integrates better with the rest of the ecosystem.
Gatsby has apparently fallen off a cliff, wouldn't even consider it.
mkdocs, on the other hand, is made with a 100% focus on content, which is why I selected mkdocs for my blog. But different users will have different needs and there are many different blog types out there, so :thumbsup:
Anyway, I completely understand your points, this is not meant to be ranting at astro!
Like Hugo it lets you create statically-rendered, CDN hostable websites, but includes dedicated support for authoring and publishing blogs, here's what the primary blog view looks like:
https://razor-ssg.web-templates.io/blog
https://razor-ssg.web-templates.io/feed.xml (RSS Feed)
Other generated views for exploring blog archives:
- https://razor-ssg.web-templates.io/posts/ (explore blog archive)
- https://razor-ssg.web-templates.io/posts/author/lucy-bates (by author)
- https://razor-ssg.web-templates.io/posts/tagged/dev (by tag)
And for those wanting a privacy alternative to Disqus and Mailchimp, it can also integrate with CreatorKit [1] - a Free OSS .NET App you can self-host to enable Comments on Blog Posts including managing Newsletter mailing lists subscriptions which includes support for generating and sending Monthly Newsletters from new content added to your Razor SSG website - all features we're also using to power our blog features [2].
PHP-Markdown-Extra is the closest thing to a standard with more than GitHub-Flavored-Markdown; several other Markdown engines use its featureset as a baseline for compatibility for anything not present in GFM, even blocking the shipping of new features until after PME agrees on a syntax. So you can think of CommonMark as the lowest common denominator, GFM for an intermediate version, and PHP-Markdown-Extra as something suitable for building more advanced websites.
11ty.dev
Even on this blog, there is only an email newsletter UI, and no evident way discover and to access the RSS feed unless you intentionally inspect the webpage source code or have installed a browser add-on.
BTW, I love the word 'lagniappe'. It really should be more widely used.
I don't remember that being the case. The tech press probably had various opinions on RSS. The ones I read were all fine with it, if they mentioned it at all, but that could just be my bubble. At any rate, what damaged RSS' adoption was not articles about it. People not knowing how to use it definitely didn't help. Content sources wanting to create walled gardens (how did that work out?) hurt a lot. Google Reader going away hurt a lot too. Everybody spending 100% of their time on Facebook or Twitter probably hurt the most. But tech press articles, that's one I don't remember being a major factor.
Anyhow - Pale Moon retains both features and for the weirdos who hate RSS for some reason, there's an about:config toggle to hide the feed detection icon altogether.
It was buggy and in a format that was almost useless.
If you complained about losing the RSS reader on the Mozilla to Firefox transition, then yeah, that was a loss. But the FF one was never an option.
Creating an account is as easy as SSH'ing into our content management system: `ssh new@prose.sh` (no email necessary).
And publishing a blog is as easy as copying files to our server: `scp hello-world.md <user>@prose.sh:/`
We also host an RSS-to-email service at https://feeds.sh using the same tech.
> 
if images are getting uploaded to imgs, how does referencing them with root work? it doesn't seem to work for me. is it supposed to show the pic?
You can try dropping the file extension which will force the service to use webp. If that doesn't work, you can email me your user profile and I can dig in further.
This plays well with federated microblogging (mastodon and friends). RSS can play both the role of signaling that new content is available and (if desired) providing that content. The signaling aspect is more fundamental imho.
A user-centric web should aim to help people manage information overflow without dependency on gatekeepers and their opaque and manipulated algorithmic timelines. There is a certain catch-22 with supply (of RSS feeds) and demand (users with RSS readers).
The ideal would be that users could consume and share RSS feeds with the lowest possible friction and highest possible privacy, e.g. have feed readers integrated into the browser (live bookmarks [1] sadly removed from firefox) or their email client [2] (thunderbird offers this).
[1] https://support.mozilla.org/en-US/kb/live-bookmarks
[2] https://support.mozilla.org/en-US/kb/how-subscribe-news-feed...
Preferably a self-hosted aggregator and some Android app that can sync with it.
It has no consideration for mobile support or concepts like synchronizing.
The idea is I don't need a RSS feed because I publish 100-800 entries in one README.md file, then announce that batch of items (samsquire/ideas samsquire/ideas2 samsquire/ideas3 samsquire/ideas4 samsquire/ideas5)
In other words, a batch of entries is already a feed, because it's just a big document and that document should be immutable when I announce it finished.
To append to a journal, I append to the bottom. To append to the blog, I prepend to the top.
Low tech but it really encourages me to write down my thoughts.
If a blog like thing doesn't have RSS, and it's good, then I think "shame I'll never see anything this person writes ever again".
If you don't want to invest in seeking that author again into something you were freely getting that was good, then the sad outcome is the lack of effort/investment on both sides (not providing a RSS feed, not remembering the author's website or name)
See: why open source software is never good enough, even though it is free. See: if you don't invest in your blog/website, why should I invest my time into it?
I have the same problem with GitHub projects. People spend a lot of time creating a wonderful GitHub project (they focus on the code), which is good, but they don't invest in the README.md and create good documentation. So I might star it and forget about it.
If you're creating a GitHub project, please write copious amounts the ideas, mental model and thoughts on the README.md
It's probably entitled because I want to benefit from other's GitHub projects. But when I'm presented with a paragraph about the code, it would be a lot of investment to work out how it is built, how it works, what is useful about it.
Regarding caring if other people read my stuff, I would like people who are interested in the same things as me to read it or to introduce an idea I think has merit. But introducing ideas properly requires exposition. So I need to follow my own advice and create exposition for my thoughts for consumption by others.
Your content needs to be maybe three orders of magnitude better, to have the slightest chance of getting polled.
I would rather write a bot that scrapes your site and creates an RSS feed, than poll it manually.
A blog without an RSS feed is like a restaurant 20km away that's open one random hour a week. The food may be amazing, but I'll never eat there. 167 times out of 168 visits it'll be closed.
So even trying to visit that restaurant sounds like masochism.
If you write a blog, or open source, and hide it in a basement behind a door labelled "beware of the leopard", then it's just cause and effect that nobody will consume it.
Finding and following are two different things.
I can find / stumble upon interesting sites in any number of ways. But if I am interested, do you expect me to remember your URL? To remember to regularly to type in a URL and see if there are new posts?
I have NetNewsWire to inform me of new posts, so unless you show up there, life is too short for manual checking.
Not that I"m specifically picking on you, but I'm just seeing a lot of statements in the article and no data. It's "all hat, no cattle," so to speak.
(I'll reply to your email in a bit, was a little busy these days)
Maybe I'll write a markdown heading to RSS script?
Got whatever reason, people would actually pay for a news list.
For my main blog [1], I manually update the feed.xml, on my „micro“ blog [2] I have a cron job doing it.
With Hey Homepage, I also built-in the RSS reader. I'm following a lot of 'dev blogs' that I find here on HN. I'm now in the process of curating an automatic newsletter for myself out of all the feeds I follow (752 feeds and counting, although I should remove some).
My dream goal is to make this more interactive. I would love to be able to shoot simple messages to other websites and thank them for their content or add something to the discussion (just like happens on centralized HN here). If I for myself can get rid of Big Tech as the middle man between my website and others, I would be really happy. Right now, I use simple comment forms under my post, but I soon found out what the boundaries are for decentralized software like this. Still, I think RSS has way more potential than it is used for nowadays.
This goes for news sites as well. I used to subscribe to the RSS feed of a local news site, for example. At some point they turned it off. I haven't been back to that news site.
You can aggregate feeds, not federate them.