https://trwnh.com/unstable/what-is-web

or: the many webs interpretation, what #web means to me, and how do we build the #socialweb

> we define "social web" as "people who want to be social on the web", but this probably depends on what you consider “web”, because we certainly already have many many ways to be social on the internet [...] i think that “web” means “anything with links”.

> in a more practical sense, it's “anything accessible by a web browser” [...] pull from those acronyms the “hypertext web”

the way extensibility works in a closed-world #fediverse is that "every implementer talks to every other implementer". or maybe there is a central registry of extensions that everyone submits to their authority, as stewards of the "protocol" that is used to build the "network". this trades out the n:n relation between implementers and other implementers, for an n:1 relation between implementers and the central registry.

the way extensibility works in an open-world #Web is you just do it.

11/?

to build the #fediverse as its own "social networking protocol" then seemingly requires that we instead go with the closed-world assumption, contrary to the #Web

it requires ahead-of-time communication and coordination, where implementers need to be willing and available to talk to any other implementer, and this load grows with every new implementer.

it requires you to be aware of other extensions, present and future, because your extension might conflict with someone else's extension.

10/?

this is the fundamental divide between #fediverse thinking and #Web thinking, where #ActivityPub straddles the line between both.

i've seen it said that the "open-world assumption" at the foundation of the Web is actually an undesirable thing for a "social networking protocol", and as a consequence, specs built on that open-world assumption are "completely unsuitable" for that "protocol".

but do we need a "social networking protocol"? do we even need "social networks" in the first place?

9/?

but before you build a "protocol" for a "network", consider: what even is a "network", in this context? and, here's the hot take: do you even *want* that kind of "network"? do you want a separate reified #fediverse network?

because the answer that #ActivityPub gives is actually a different one. There is no "AP network", because AP as a protocol is not enough to build a concrete network. it is intended to provide, and exists in context of, the larger #Web.

8/?

I want to take a #web page and mangle it in such a way it looks the same, but is self-contained...

Ideally in a way that supports:
- adblock
- #stripping un-used #css/#javascript
- spits out the fewest files (images don't need to be data url'ed)
- A #selfhosted API

...mostly for automatically #archiving articles I reference by url... I'm not planning on doing this to an SPA or some react nightmare...

I'd prefer it not be a #screenshot, or a print-to-pdf, but maybe that's chill too?

A data hoarder’s dream come true: bundle any web page into a single HTML file. 📦✨

💾 monolith: CLI tool for saving complete web pages.

🦀 Written in Rust!

⭐ GitHub: https://github.com/Y2Z/monolith