F
@trwnh I was thinking that if we started typing at the TLD end, it would take longer before we reached the point where the browser could show a useful completion.
This doesn't make sense, though, because the browser can just match on a substring anywhere in the URL.
There I go again, posting rubbish on the Internet. One of these days I'll learn 
@trwnh I think we've got them the right way round - URL bar autocompletion wouldn't work anywhere near as well if we started with the TLD.
Fediverse software developers:
How long have you been working on software for? Software in general, that is, not just Fediverse stuff.
Please boost for visibility, and all that!
@trwnh ...or stop paying your bill. I've seen things in the JSON-LD @.context that resolved to porn sites.
@trwnh One early source of confusion for me - and I think some others, too - was the distinction between "a URL that's meant to be dereferenced" and "a URL that's being used as a unique identifier, in a JSON-LD / RDF type way".
I can see the merit in allowing anyone to define brand new, guaranteed unique identifiers based on their control of a domain name - but allowing that namespace to overlap with actual dereferencable URLs was maybe not so clever, in my view.
@julian This is exactly my point 1 from here: https://socialhub.activitypub.rocks/t/desired-changes-for-a-future-revision-of-activitypub-and-activitystreams/4534/10
My opinion is that this should actually be the standardised behaviour.