The #stravaheatmap incident shows that many of the #strava users are completely ignorant about the impact of its use. And no, there is no technical solution for stupid.
Am I far off assuming that #ActivityPub is sort of a next generation implementation of #PubSubHubbub and other technologies that made weblogs (remember those?) talk to each other? In other words, is it time to dust off my #foaf yet?
@Gargron@grote This is in line with my experience: if follow initiated from within Mastodon it'll be ok in most cases, if remote follow it will fail in almost all cases. The TLS error might be isolated to the grobox instance.
@elieuw_@grote I double checked another gnu social profile from gnusocial.de, it seems to work but not via remote follow or profile URLs, only username@domain
@Gargron@grote Ok thanks for the effort so far. It's not the most urgent issue I'm sure but it would be nice if all of gnusocial could be included. In other words, take your time
@Gargron I usually go to a user's profile and click the "Remote Follow" button. If it errors (and it usually does) I open Twidere and search the user there, if it's been found, all is well.
@maloki pointed the search out to me, tried this also with the @user@instance syntax, this works if the user is cached on mastodon.social (I'm guessing here).
Could you test with @grote ?, I get a "503 Remote data could not be fetched" (sorry Torsten for mentioning you here for testing purposes)
@maloki Btw, first suggestion "you're doing it wrong" is not a very friendly and respectful suggestion.
@Gargron: I tried users on several instances, gnusocial.de, quitter.se, status.fsf.org,....seems OStatus connect is failing. Not saying the error is on your side, just noticing Mastodon website has issues with this.
Did disable all browser add-ons, cleared cache etc etc. And tested with Firefox and Chrome. Don't make me use IE or Edge, please.