I've been spending some time on Quake resources these past few weeks. Writing tools to parse Quake data files, writing a QuakeC VM, etc. What's great is that the resources from that era are old-school HTML pages. No Javascript, no cookie banner. Easy to save and parse. Easy to search into.
If you produce actual interesting content that are archival worthy (which I think Chip and Cheese does) you should really make sure your content delivery platform is as simple as possible. Take HN as an example.
What matters is the content of your article, not how they are presented. Most of the time, presentation these days gets in the way between you and the content. And substack clearly does.
I consider simple HTML pages as a quality signal. Whereas if the content is posted on a large platform, I'll consider it likely to be rubbish (if I can read the content at all without demands to install the app, sign up, or subscribe).
Comments
I've been spending some time on Quake resources these past few weeks. Writing tools to parse Quake data files, writing a QuakeC VM, etc. What's great is that the resources from that era are old-school HTML pages. No Javascript, no cookie banner. Easy to save and parse. Easy to search into.
If you produce actual interesting content that are archival worthy (which I think Chip and Cheese does) you should really make sure your content delivery platform is as simple as possible. Take HN as an example.
What matters is the content of your article, not how they are presented. Most of the time, presentation these days gets in the way between you and the content. And substack clearly does.
I consider simple HTML pages as a quality signal. Whereas if the content is posted on a large platform, I'll consider it likely to be rubbish (if I can read the content at all without demands to install the app, sign up, or subscribe).