Two standard URIs we need in [current year]:
1. Music. I should be able to share a platform agnostic link to a song that your music service can match and open correctly
2. Maps. This one should be like especially straightforward. Why can’t I send you a link from Apple Maps that opens in Google Maps or Open Street Map or whatever.
Let’s go standards body people. I know y’all are on Fedi
Edit: hey maybe check replies before replying. A ton of people have already mentioned geo:// 🙂
I like that one. Does songs and albums. The only quirk is that you need to give it the link to a song/album on one of the services to start with, but then it gives you a link to choose the platform you want to listen on.
Example: https://album.link/y/OLAK5uy_ngChY-hNoXPKyCTOr7SNjLuZA42IMslJE
This is the first time I've ever heard of Quobuz, and I'm not 100% sure you didn't just make it up lol
@puzzler @danirabbit @PopeASDF
Yes, sharing coordinates and not a proprietary format link from a phone application is not straightforward. If I had to explain it to someone via text or voice, I'd probably fail to be understood.
@danirabbit Uh... Hi! I do standards work. Not for that, though. 🙃
And yes, the music one in particular is incredibly frustrating. Yes, it's a library science problem and library science is hard but still...
@faithisleaping Oh hi librarian here and can I just be very specific: that's a *music* library science problem. As a non-music librarian I for one am backing away rapidly from this problem but I do look forward to the conference presentations and journal articles, k thx thoughts and prayers.
@danirabbit wait there isn't a map one? o.o I thought ... *checks* UGH the fucking "Default Maps App" thing from windows 10 was "BINGMAPS:" all along? UGH!!
Yes definitely 100000%
I'm still convinced that a big issue with Fedi adoption is the lack of standard ActivityPub URIs for sharing links. It's gotta be confusing for people when you link to a post and it goes to the originating server instead of opening on your Fedi server of choice, or even maybe having your browser pull up a server-picker like system app picker does when you don't have a default set.music://song=<song-name>/artist=<artist>/album=<album>/year=<year>/ISMN=<ISMN> perhaps?
That should give just about enough information to find any given song.
@danirabbit there are geo: uris which have
mixed support
Danielle Foré
craftxbox
matt wilkie
Alavi | علوی
soc
PopeASDF 
Kat 
jer
Kate
John🥛
Miriam's on Medical Leave
�
Ángela Stella Matutina
LastOfThem
Faith, Purple haired feminist 🧋 
Zeborah
Kay Ohtie 🔜 FWA
Lisa Melton
Rusty Corgi
Mark Whybird
Lunaphied
Krutonium://
Kraftwerk-Das Model Collapse
James Beyer
Justin Fitzsimmons
MisterMultiverse
Charlotte 
/Cinny 
sodiboo 
geo:. but like, maps applications support linking to a particular business, to a particular address, to a particular region, and a variety of other things. this is all quite nontrivial to communicate in a URI. maps apps also generally support things like a location sharing link; this would likely not work cross-application, and i think it overall would make for a confusing user experience to inconsistently copy a "standard" link or a "proprietary" link depending on what you want to link to.@sodiboo and there's their #PlusCodes initiative: https://maps.google.com/pluscodes/
@sodiboo @danirabbit @charlotte In the end, a lot of these are just "convenience features", not necessary for a "bare-minimum standard" that all providers and clients alike *could* and *would* implement.
– IDs are often times tied to a single provider's database, so probably no two providers could agree on using the other one's as point of reference. Also, if that provider goes out of business, the whole system stops to work. This system wouldn't federate well at all
1/
@sodiboo @danirabbit @charlotte referencing to a place *would* theoretically be possible, however, this, again, would need to some debate, as some would wish for this to be the official name in the native language (either encoded or a slug), while others would opt for the English name. Best one *can* probably do, is plain text search.
As with IDs, there would need to be a global identifier with a standard pattern to it which everyone, not just a single monopolistic company, can agree on
2/2
There's two important considerations there @danirabbit.
* Making the specification for the URI scheme. This is a matter of figuring out what clients need, what servers need, and how to agree on a canonical way to specify the unique item we're referring to.
* Implementation in clients for that URI scheme. This is a matter of whether it's *of benefit* to the people who make decisions about the features and maintenance of those clients.
So, to take the Maps example:
* The 'geo' URI Scheme already is standardised. https://en.wikipedia.org/wiki/Geo_URI_scheme
* Client applications will implement it, *if* the decision makers see benefit. OpenStreetMap supports it fine: https://wiki.openstreetmap.org/wiki/Geo_URI_scheme
To take the Music example:
* We already have 'https' URIs for pointing to specific audio data. That should be good enough, right?
* The people that want to gate-keep who gets to play music, absolutely hate open standards for playing music. And artists are, of course, concerned about their recordings propagating beyond their control. So, what incentive do music platforms have to support a standard link to music?
Without that, it goes nowhere.
@danirabbit There’s a map URI that seems to work on iOS:
maps:?q=52.3606,4.8755&z=13
No idea if it works on Android.
Not much documentation on it.
https://www.iana.org/assignments/uri-schemes/prov/maps
For #2 we already have Latitude and Longitude which should be service agnostic provided they use the same geodesic reference 🙂
Latitude : 53° 1' 40''
Longitude : - 4° 16' 51''
@cubeofcheese
You shouldn't even have to see it. On your map app, you put a pin and share it. The app makes up the uri and sends that to your date. Their maps app opens the link.
Include a comment with the street address or code phrases to be dropped with the bartender, and you're set.
@xinit @cubeofcheese @danirabbit
Sure. It's just a formatting issue rather than not having a framework.
KML/KMZ is one option. Others are bound to exist.
@danirabbit the maps part is totally solvable, no question. iOS should just implement geo uris.
Music is basically impossible though. You could at best have a uri that triggers a best effort query based on metadata, like what Google assistant does when I say "play shallows". But there doesn't exist a universal music database that would allow you to have actual unique identifiers. This is why music streaming platforms can get artists and songs confused. Would be nice though
FiXato
Zuri (he/him) ❌️👑 | 🕐 CET
Siguza
Face Thumb
I AM BANKSY ☕ / 🗑🔥
bignose
Dmian 🇪🇺
gtb
Simon Zerafa
CubeOfCheese
Damir
🌸 lily 🏳️⚧️ 
θΔ ⋐ & ∞music:?provider=musicbrainz&id=…)@sticklandtim Yes, you missed the point, I'm afraid.
Since you mention it, What3Words is objectively bad and should not be used. Since you appear to be in the UK, I recommend using Ordnance Survey grid coordinates to share locations. The free OS Locate app lets you obtain them quickly and easily. https://w3w.me.ss/
Tim Stickland
Peter Brett
Kristian Thy