pikematchbox
> Now it’d be fine to use href if only they had the full URL:
Totally agree. This hits on what we're actually going to ship for how to create in-line octothorpes with plain anchor tags, and the docs should reflect the primacy of this approach.
> Suppose you want to be on _two_ rings, and they use the same keyword, but differently—what do you do? “You can only be on one ring” is a rather unnecessary and limiting restriction.
Also agree, which is why that is not a restriction. We have two live demos of thorping to multiple rings from the same URL.
Term collision is very much something we've been thinking about. For now it has to be handled manually. But because we're building the whole system off of an RDF base, we have a lot of low-level tools to define and process different vocabularies in some powerful ways. The same term having different meanings on different servers is the most immediate application of this, and it's high on our roadmap.
A lot of the questions on the "Further questions, problems, observations" list for Reversible are front and center for us, and we're hoping to demonstrate some answers to them as we roll things out to more real world users.
When my collaborator saw this he said "isn't our whole point 2003 had some good ideas that we want to revisit with perspective from today.”
Also -- Memepool was an early fav of mine and an inspiration for https://mothra.click/, which I built in 45 minutes for my wife, who has never owned a smartphone, so I could send her links. Getting lazy about updating it meant "Wanting to post to mothra.click easier" had a non-zero impact on the existence of Octothorpes.
So caveats are that our documentation isn't fully up to date, some features aren't part of core yet, and we're still in a fairly rapid test and update cycle.
I've compiled a bunch of answers to this and a discussion on Lobste.rs in a blog post > https://ideastore.dev/blog/shrodingers-launch/ but will address some specific questions about the protocol in-line here.