@espectalll I fixed that in master and nightly. The acct: URI is normalised and remote subscribes work for anyone who has updated that. Maybe @hannes2peer wants to merge this on #quitter.se: http://status.hackerposse.com/url/14825 and http://status.hackerposse.com/url/14826 @Gargron I never understood underscore filtering either (but that's not the issue in this threa…
@thefaico Subscribing shouldn't be an issue. Mentioning should probably cause collision confusion though. If this is an actual problem I wouldn't mind making sure it works. Haven't heard anything about this from the real world use though.
@mcscx You should, but it'd be without the underscore. The locally stored (normalized/sanitised) nickname is the one you would mention. That's why confusion may occur with a__b and a___b because both would be @ab (but you wouldn't be able to do it without being subscribed I think, i.e. @a__b@someplace.com)
^- @realramnit Apparently I could use the nickname but not the full ID, probably not even @choller (though that depends on in which order the normalisation goes, which I don't remember off-hand)
@realramnit Ok, I could use the proper @a__b@example.com but not the shorter @ab@example.com
So this is more of a user confusion scenario than a technical difficulty. The most confusion part was that my autocomplete suggested to use an invalid identifier.
@espectalll @realramnit I haven't tried using the "Remote follow" link on a #Mastodon instance yet, no. But that's just a redirect to /main/ostatussub which works great. I just subscribed to @permalink
@espectalll Yes, remote subscription form. What I saw that was the error in some screenshot you had was that the 'acct:' part was included, which makes the lookup fail. Without it, it works even with underscores. If it for some reason still doesn't work for you, maybe it's because you're on #quitter.se and because @hannes2peer unfortunately has to work to gather capit…