What are the biggest difficulties when making ActivityPub software compatible/federated with each other? And why?
There are some Fediverse services which are incompatible or don't work that perfectly with each other (e.g. Lemmy on Mastodon). So I was curious on why that could be a problem with ActivityPub compatible software in general. I mean, apparently just implementing ActivityPub may not be enough.
And if there are some Lemmy devs reading, what are some technical difficulties for Lemmy on that regard? Thank you for making this awesome piece of software btw!
Wait, what? I tried to follow a couple of Lemmy groups from my Akkoma (fork of Pleroma) account. It shows as ”requested follow” in Akkoma. A day later I still haven’t actually followed the groups in question. You say there is a switch somewhere I can flick? In Lemmy, or in my other service(s)?
Admins have a setting in most modern microfedi platforms that allows them to enable something called authorised fetch. It's a security feature that makes it harder for blocked instances to access your content despite the block. But, a side effect of it, is that it creates issues for fediverse platforms that don't support authorised fetch, and lemmy is in that group.
So, your instance admin can disable authorised fetch and that will generally fix the problem, but I'm not sure if there are any akkoma specific compatibility issues above and beyond that.
Pretty sure it is a group. I can search for it, and see its "profile" page, which is the same profile as over here in Lemmy. Only shows "Request Sent!" since yesterday when I tried to add it.