Egregoros

Signal feed

Timeline

Post

Remote status

One of the most annoying aspects of the ongoing corporate capture of our network is that protocol-related discussions increasingly happen on Github instead of Fediverse (or friendly platforms like SocialHub and Codeberg).

Today's example: https://github.com/swicg/groups

Why use Github to talk about federated groups when we have federated groups right here in Fediverse? That makes no sense. But some self-appointed "leads" decided to create a repo anyway.

Similar Github repos ("task forces") also exist for other protocol features. I don't see any reason to legitimize this by participating and hope that other developers will do the same.

Replies

8
@a @silverpill
>my issue is between akkoma-akkoma and akkoma-gts mostly, where akkoma seemingly drops some follow requests instantly (maybe they are "already seen") and also some profiles just will not load at all...

Do you observe the same with Pleroma? If not, then if signed fetches are involved, I'm somewhat certain what the issue is. I've seen this happen before with Pleroma and @mkljczk fixed it recently I think. Akkoma would need to backport those fixes in that case.
@mkljczk @a @silverpill It is almost non-existent in Pleroma, but very popular in Akkoma, maybe even the default (too lazy to check). If a remote instance needs to fetch an actor to figure out who you want to follow, ie. from a new instance you want to follow somebody whose handle you know but they haven't interacted with you yet, that would break as I understand it.