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!
deleted by creator
I believe that the future roadmap for Lemmy is to allow for users to be followed
Indeed. I just now came back here to Lemmy to see if that had changed, seeing as I could find my Lemmy user (this account) from my Akkoma instance, and I could press “follow” over on Akkoma. That apparently sends back to Akkoma that my Akkoma user has “requested” to follow my Lemmy user, but I can see no trace of that over here at Lemmy, and here is no way to “approve” followers.
It would be great if I could follow my Lemmy user from my other Fediverse accounts and then re-post (boost) my entries from Lemmy to the further Fediverse without having to make a separate post about it. Much like Pixelfed works.
You need to wait for Lemmy 0.17.0 for this to work.
that means its coming soon! Excited for whenever the new update is released
You can follow the groups you post to, and then boost the posts you make that way
I can’t even follow communities apparently, I can click the follow button but then when I come back to the community it’s unchecked again.
If your instance has authorised fetch turned on, that breaks the follow requests with lemmy. It took a long debug session before @supakaity@lemmy.blahaj.zone discovered that!
Oh thank you that did the trick
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.
Thanks. I shall have a look. It is an Akkoma instance-of-one with only me on it, so I am the admin.
Yeah, but even though that is cool I’m not sure how well that will scale when Lemmy picks up lots of users.
From a Lemmy users perspective: You have a cool link that you wish others get to see. To post it you need to pick a group where it fits in. It might not be the groups you normally hang in. Or it is, and the group might have 100’s (in the future maybe 1000’s) of contributors and the group stream is moving rather fast.
From another Fediverse service: That Lemmy group you started following is flooding your home stream as it is really active. Sadly you also published a Lemmy post in a group you don’t normally hang in, but you now have to follow to be able to boost your own post in it to the further Fediverse.
I can imagine how that quickly creates both noise and scalability issues.
I imagine that’s why following users is planned eventually.