S E A N
K . H .
L I A O
Apparently it's not enough to just convert
thoughts -> text/markdown -> html and dump it over https to people's browsers.
Nooo, the interwebs bemoan
centralization and the lack of discoverability,
and in true internet form,
dream up a thousand new protocols to keep blogging on life support.
Note: not using any of the below
old tech - not very connected
It works, why change it? they say
rss: designed when people thought XML was a good idea,
people have strong opinions on what you SHOULD put in here
atom: a protocol upgrade to rss
webring: sites with links pointing to each other,
traditionally with forward/back in a ring,
occasionally with a central directory
IndieWeb - loosely connected
Self host, but still sort of connect to each other?
Abstract ideas of being "people focused",
no real tech standards.
webmention: centralized server watches sites,
if watched sites link to you, you get notification based on link hidden in your site
microformat: overload your site with html classes and hrefs
so it can be turned into super verbose json
micropub: http/microformat based protocol for content management systens
syndication: sites directly publish content from other sites, not just a link
Fediverse - connected clusters
Expand beyond blogging!
Does this really make sense for decentralization?
Mostly clones of popular services
activitypub: the OO people got their hands on HTTP/JSON,
publish / subscribe in a decentralized way(?),
main protocol for fediverse
XMPP: chat protocol, in XML!
mastodon: twitter clone
pixelfed: instagram clone
peertube: youtube clone
Sometime derided by the same people as above,
but I think these are truly decentralized,
decoupling content from the serving protocol.
WebSub: PubSubHubbub, extended rss/atom, push content with subscriber webhooks
AMP: first step in content first, even if people hate it
WebPackage: trusted web content bundled together, no longer tied to http!
uses SXG / WebBundle
Signed HTTP Exchange: SXG, resource with a signature to trust origin,
you know the content was from the domain at some point, even if you didn't retrieve it directly
WebBundle: resources bundled together