Since we are in the fediverse, I think it would be convenient to have a fediverse-wide resolvable fediverse URI scheme, that would look like so:
fediverse://
edit: Found a relevant FEP: https://codeberg.org/fediverse/fep/src/branch/main/fep/07d7/fep-07d7.md
It’s an intriguing idea and might well be in line with the founding principles of the internet.
As I understand it, the URI is supposed to define the type of data you will find at the address, allowing you to use a client dedicated to that type. So: use a Gopher client for
gopher://data, a newsgroup program fornntp://data, and of course a web browser forhttp://.So the issue here would be to define what “fediverse data” actually looks like. This is quickly becoming quite a technical challenge.
Personally I like the idea of standardizing communication paradigms with a protocol, but you do first have to decide what the paradigms are. A few obvious suggestions:
Since the ActivityPub protocol seems to be the de-facto glue to this fediverse thing, maybe that’s where to look first.
it’s not really about the type of data, it’s more about how you get it. web browsers could open gopher URIs for a long time, it was just a separate access method.
but the thing is, it doesn’t really make a difference today, because we’ve decided that http is some sort of base protocol.
someone decided to try making a custom
matrix://scheme (it’s called a scheme btw) for matrix clients and it’s just been a nightmare. clients don’t know what to do with the url, servers block it, we had to patch it out to get it to properly encrypt messages to our local homeserver. and matrix just uses http on top anyway.no, i think they should be reserved for protocols that are important enough to be in the <1000 range of ports. like SSH, or Doom multiplayer.
Interesting anecdote. Yes I’m aware that the “ht” in
httpis now basically a historical artifact. It all feels a bit dirty but, as you say, doing things the way the architects intended is probably not worth the effort.