#ActivityPub für #WordPress installiert, Blog-Profil @blog (nicht Autor!) aktiviert, in Mastodon gesucht, gefunden und gefolgt. Folgeanfrage taucht aber in WordPress nicht auf.
So, #Smithereen no longer requires a username when signing up. You instead get assigned one automatically, of the form "idXXX" where XXX is the ID for your user record. You can change it later in settings if you wish. Current Mastodon versions handle this change no problem.
The username is only visible in two places:
The URL of your profile
When someone mentions you
So it's not very important. Definitely not important enough to be a required field when you register.
My #ActivityPub server is receiving “GET /poco” requests from #Friendica servers (based on the user-agent). Can anybody point me to the documentation for this behavior? #AskFedi
Thinking about attempting to code an #ActivityPub service as a learning project, and to perhaps solve the social lock-in issue of gaming platform profiles that really pisses me off. 🤔
I really really don't like #DRM, however I'm way too attached to my almost 20 year old #Steam profile and like to do video game achievements. Having a unified, federated profile that pulls its data from all the different sources (Steam, PSN, Xbox, RetroAchievements.org and especially GOG) would be neat. #gaming
There are over 8K LoC for Pixelfed Groups atm, and that will likely double in the coming months (mobile apps, federation, etc...)
It's the most complex feature we've ever shipped, and we've pioneered several mod and safety tools to enable the best experience across Pixelfed instances
Rest assured, I will show the fediverse how it's done 💅
What I find strange in #ActivityPub and #Fediverse that there is no way to put a note to follow request. Like "I want more posts in language_name in my feed and I liked the cat videos you repost".
It gives cases when someone concerned that they did not understood why someone follows them.
Part of my frustration with #ActivityPub and one of the things I find baffling giving everything else in it: the lack of tools for backpressure.
Backpressure is fundamental in building reliable distributed systems (c.f., Notes on Distributed Systems for Young Bloods). From a C2S perspective I get why it wouldn't need to be specified, but from a S2S federated protocol perspective its absence is frustrating.
All that it says is to take care not to overwhelm others and a bit on rate limits