"sorry bro, i'm on apple music"

You know how for every xkcd.com comic, there is a corresponding page on explainxkcd.com that is unique for the xkcd comic? And all the user had to do was to click into the link, add "explain" before "xkcd.com" and be directed to the explain page of that day's strip? Imagine that kind of domain hack, but for "https://open.spotify.com/track..." links, or "https://spotify.link/xxx" links, their Apple Music counterparts and users can quickly modify the link and paste the link into chat.

  • ideas
    • domain hack each service (openspotify.com maybe, or sharespotify.link )
    • create backend that processes the whole link as a long param and append original link to ingest (https://backend.com/https://spotify.link/xxx)
      • will need investigating to see if that is supported in browsers
    • default service
      • i've seen some services which act as a linktree for a song, which makes the user click on the service that they want
        • this is another unnecessary click
      • set default checkbox
      • save preference sets cookie, redirect to service 2 (domain hack) endpoint that redirects it to service..n until last one redirects to song (maybe reverse breadcrumbs or linked list on get param)
      • possibly can be implemented as a PWA (cache links, work offline, no server fees)
        • client actually figures out what the final song is? might not work because CORS
        • cache locally, and also on thin backend