A list of /uses pages detailing developer setups, gear, software and configs.

Hardcore IndieWeb fully embraces existing IndieWeb principles; there’s really nothing new or different there. The key aspects of Hardcore IndieWeb are control over your content and portability of your website:

• If your content doesn’t primarily exist on your own hard drive, you don’t fully control your content.
• If you don’t have a copy of your published HTML and web assets on your own hard drive, it’s not truly portable.

“Did I just read 2,500 words that tell me to write my own HTML and upload it to a web server?” Yeah. You did.
If this seems like ridiculous advice in 2026, I think that’s largely the result of how we’ve strayed so far from the original simplicity we had when working with the web.

Yes indeed.

In fact, yes for many reasons.

My hope is that as web standards improve, build tools can become slimmer and simpler, because abandoning them altogether is not a good option on larger projects.

For small apps, it doesn't matter.

Ok this is fun. The HTTP code 309 should be returned when the path /8675 is called

Why? https://en.wikipedia.org/wiki/867-5309/Jenny

Another slash page that can become a standard to a personal identity website.

Another ode to the web built by hand for the craft

How Google is slowly killing the web and

If you do care about the web, about people’s ability to participate in it as more than mere passive consumers, this needs to be taken seriously. De-googlifying your mental apparatus becomes more urgent today. Find other search engines, don’t use the Chrome browser. Or wake up in a slopified AOL kind of environment where your access to information is limited to what Google’s synthetic text extruders deem relevant.

Degooleify

When ChatGPT appeared in 2022, I quickly realized the Web was being forced into another battle. This one is different. With BBSs, the Web won because it was more accessible. With Flash, the Web won because open standards eventually became powerful enough. With mobile apps, the Web survived because search, links, and publishing were still essential.

This is the browser losing its position as the primary interface to knowledge.

Stack Overflow was the warning shot of the web searches being replaced by AI.

The website will becomes even more infrastructure: Websites will increasingly become infrastructure for machines. They will feed models, agents, search systems, APIs, datasets, crawlers, and private knowledge bases. A source of truth and data.

Emails will remain, but younger generations do not think in folders, inboxes, subjects and signatures. They think in threads, voice notes, reactions and instant replies.

If people stop browsing, stop searching, and stop clicking, then visibility depends on whether AI systems decide your content matters.

Then browsing and URLs will be lost little by little.

People will not say, "Today I reject the open Web." They will simply ask the assistant because it is faster. Convenience wins. Convenience replaces nostalgy, all the time. It almost always wins. The Web's biggest enemy is not ideology. It is not regulation (well, a bit yes). It is not even AI itself. It is convenience.

So the web can become a nerd medium again, like IRC, FTP, Gopher or Bulletin Board System.

Now I am watching AI become the next interface. The pattern is obvious. Interfaces change. Behaviors remain. People want answers. People want connection. People want tools. People want convenience. People want to publish, learn, buy, flirt, argue, create, complain, and feel less alone with their questions. The container changes. The hunger does not. The Web we know is going to disappear. Not because it failed, but because it succeeded so completely that its content can now be absorbed into the next interface.

Maybe this article will be read by humans. Maybe it will be summarized by an AI into two polite lines for someone curious on the other side of the planet. Maybe that person will never visit this page. That is probably the future. A little sad. A little funny. Very predictable.

vaguebooking: an intentionally vague but highly personal and emotional post designed to elicit concerned responses from friends and family, often viewed as a desperate bid for attention or validation.

There is also a word "vagueposting" that defines the act as posting without enough context for the post to make sense on its own, prompting others to ask what's going on.

Another definition came from Twitter with "subtweeting". These subtweets were considered passive-aggressive, vague, attention-seeking, bitter, or anti-social.

On the contrary, vagueness is sometimes just privacy management. That's why we need to cultivate spaces online where people feel safer, and are safer.

Collect publications on the AT protocol (Bluesky) and presents it the way a classic feed reader would.

Note it's similar to microformat in HTML.

A design system documentation tool

The GOV.UK website is usable on the PSP web browser.
Interestingly there is 3..574 users visiting GOV.UK on games consoles: Xbox 2,062; Playstation 4 1,457; Playstation Vita 25, ... (2022)

Not everyone has a big monitor, or a multi-core CPU burning through the teraflops, or a broadband connection.

As always serving raw HTML and CSS for the win. In comparison to NextJS, Astro delivered the same features for 5% of the original bundle size.

Une autre FAQ bien utile

Adding query string for a referral (with ?via for example)

1. can broke the URL such as https://int10h.org/oldschool-pc-fonts/fontlist/?foo. Altering a URL gives you a new URL. The new URL could point to a completely different resource, or to no resource at all, even if the alteration is as small as adding a seemingly harmless query string.
2. There is already the HTTP Referrer header for that. It's governed by the Referrer-Policy

Another post describe this problem: https://chrismorgan.info/no-query-strings

Somewhere out there, someone wrote a really good blog post today. You'll probably never find it. Google won't show it to you. Social media buried it under engagement bait.

Bubbles tries to surface it. Community voting applied to thousands of personal, independent blogs, with identity and discussion routed through the Fediverse.

Hacker News and Lobste.rs have community voting figured out, but non-tech content gets drowned by the tech majority. Kagi Small Web curates thousands of personal sites, but has no community-driven ranking. Blog directories help you find blogs, not today's best blog post. Social platforms own the conversation. Mastodon is decentralized and ad-free, but you only see what the people you follow share. RSS is great, but solitary. There's no collective signal telling you what's worth reading today.

There are reasons to be negative about the future of the web. The author reminds what is awesome about the web. There are many topics: Accessibility, animations, building stuff, optimizing, semantic markup, styling.