A few days ago, Beehaw posted an announcement in their Chat community about the challenges of content moderation and the possibility of leaving Lemmy. That post was eventually locked.
Then, about two days ago, Beehaw posted an announcement in their support community that they aren’t confident about the long-term use of Lemmy, due to so-called concerns about Lemmy.
If you currently use Beehaw and want to stay on the federated Lemmy network, consider migrating your account to another instance like lemm.ee.
Honestly, reading the second post I feel for them. Seems like the main issues are all technical.
The issue about a mod removing an image from the posting server and it not being removed on other servers is very concerning. That means that any instance needs to moderate the same content again on top of the moderation that was already done by the host instance.
That type of duplication of effort is strange and it also means that illegal images could be propagated throughout the instances when they could have been stopped at the front door.
I always felt the fediverse is designed in a very awkward way… the way all the content needs to be mirrored, not only does it make it hard to update / modify / delete content, but also it makes it so other instances have to host content from all the other instances they want their users to access…
Not only is that redundant and requiring a lot more resources from the instances, but it also means that if an instance you federate with is hosting content you don’t want (let’s say… ch*ld pr0n) then your instance might end up HOSTING (ie.activelly propagating) that content… if I hosted my own instance I wouldn’t want to federate at all out of fear of legal implications and I’d be constantly paranoid about possibly facilitating illegal stuff like that without even noticing…
Imho, a decentralized system in which content providers are separate from the user account providers would make more sense in my mind. Then the content providers can have full control over what they are hosting and also control over what user accounts (or whole account providers) are banned from posting / allowed to post. And it still gives users the freedom to navigate across different content providers seamlessly with the same account and interact with multiple content providers, sort of like with the fediverse, without having to login to each content provider.
Yeah. The Reddit migration, small at it was, brought an order of magnitude more people to the platform, and it has shown Lemmy is not ready for prime time. It is also showing that the devs may not be the best at leading this kind of development effort due to inexperience.
Relooking at the idea of the fedeverse may be needed, and the group at Beehaw seem knowledgeable enough on how a Reddit like system should work that they could probably do a better job designing one.
Removed by mod
You won’t see the posts to the small communities on the new instance unless one of your users manually finds them and subscribes to them.
I get why a decentralized model was created; we’ve seen issues pop up with Reddit due to a centralization of power. However, this current implementation of a decentralized system is showing major problems at a fraction of the scale Reddit showed and the devs seem incapable of enacting meaningful change to fix this.
deleted by creator
It is decentralized in that there isn’t one group of admins, but a set of them across the platform who can run their instances as they see fit.
And you can effectively kick off an instance from Lemmy by mass defederation.
I don’t see that as a federation issue, it’s a moderation one. It’s on the admins to bring something new / niche to the table.
deleted by creator
For other systems where its Activity Pub - think FourSquare check ins ( joinmobilizon.org/en/ ) or “a new video has been posted” or “a new blog entry has been posted” ( wordpress.org/plugins/activitypub/ ) - it works fine.
That’s interesting. Does Mobilizon actually not do any mirroring between instances? How does it work when a Mobilizon user accesses a group/community that isn’t in their home instance and posts some content there?
About the Wordpress plugin: my impression is that it only works as a broadcasting activitypub feed, but the blog authors registered in that Wordpress instance do not have any way to use that account to subscribe to any other ActivityPub feed, correct? if so, that piece of the puzzle would still be missing, and it’s there where we typically find mirroring.
As far as I understand it (and I could be wrong), there is no way in the ActivityPub protocol for a user from another instance to actually publish content (eg. a reply or a comment) directly into a different instance (that is, without hosting it in their own instance first), so at the moment the way it works in services like mastodon/lemmy is that the user posts content on their own instance referencing the content from the second instance that they are replying to, and then the second instance mirrors it and displays it as a reply of the original post.
This, as far as I understand it, is the origin for the need of mirroring, and not really any thirst for “censorship resistance” or “faster rendering time”. I feel the problem is still originating from limits in ActivityPub. Or am I wrong? Is there a way to do this in the current protocol without mirroring?
Layering a microblogging system on top of it where you want faster rendering time (and lower network traffic - unless you’re hosting a popular site) is awkward.
I don’t think the need for faster latency justifies the mirroring. You could still get a fast time by sending the requests directly to the original host, without proxying/mirroring them at all from the service offering the frontend. Just allow for cross-domain requests to call directly the API from the client, without needing server-to-server requests for that. Of course if the host is slow then the request will be slow, but if it’s fast the request will be fast. The responsibility for performance when providing content should fall on the content host. The instance where the user has an account could provide some token for identification as proof of the user belonging to it, and have third party content providers validate that proof and decide on their end whether the user is allowed to access/post content there directly (being subjected to the moderation of the content provider, who is the one hosting the content).
The more troublesome part of this approach would be having to rely on client-side aggregation of the content coming from different providers in order to build a feed. But I think this could still be viable. Or it could be handled by another different type of instance that acts as indexer but doesn’t really mirror the content, just references it. This also would only be necessary if the user really wants an aggregated feed, which might not always be the case, sometimes you just want to directly browse the feed of a particular community or your subscriptions from a particular instance.
I mean, I get that for some use cases mirroring would be a good thing, but that could be entirely a separate layer without requiring it as part of the communication. Making it mandatory places a huge responsibility in the instance host without it being necessarily something that every user needs or even wants. I don’t want to be dependant on what other instances my particular instance decides to mirror so I can access them. What’s the point of the fediverse if in order to access content from two instances I have to create separate accounts just because they don’t like each other’s content policy?
deleted by creator
I agree wholeheartedly. This is actually the exact reason I haven’t tried to stand up an instance. I don’t want to mirror the content.
deleted by creator
Since the beginning, I expected Beehaw to move to an unfederated software. They wanted a system where they could vouch for every user and comment, and even with a list of allowed instances, there was (and is) not enough control they can do to keep it to their standards.
Yeah. I mean it’s a topic that will affect a lot of people, but the changes are likely months away. Beehaw doesn’t have a platform to switch to overnight anyway, it would need some work.
That said it’s good to get this conversation out in the open early as to hopefully spur Lemmy development to address issues we’re running into and help improve the Fediverse model overall.
What I don’t get is that they’d probably need to create their own platform. Their main issue is about mod tools, so they’d need to create their own mod tools. Why not just add those to Lemmy? It’s open source. If they’re capable of creating their own platform, they’re capable of adding what they need to Lemmy.
deleted by creator
You pose a good question. Here are a couple reasons:
- Rust is hard language for people to develop with.
- There are problems extending beyond moderation that need addressing, such as database management, as admin alyaza put it:
The problems with databases are almost too numerous to talk about and even Lemmy’s most ardent supporters recognize this as the biggest issue with the software currently.
What I don’t get is that they’d probably need to create their own platform. Their main issue is about mod tools, so they’d need to create their own mod tools.
Not quite. When you are on a non federated community, with accounts that require approval, the ability to ban trouble makers solves most things, and doesn’t leave them with an easy way back in.
Moderation requirements on lemmy are very different though, because federation introduces communities and users from instances that have different rules.
No need to create their own platform, they can use phpBB!
The technology ever!1! And a good old MySQL with apache!
I thought you can turn off federation.
Good Riddance. They wanted a safe space, they now have their safe space. Everyone’s happy.
What do you mean by this? I havent explored that instance
They seem to feel aggrieved by beehaw, which existed long before they discovered lemmy, and its sanitized moderation style. It’s just a safe space instance full of affable people. There’s really nothing else to it. I honestly have no clue why they’re upset about internet hippies.
If this happens, we will lose a good chunk of the lemmy fediverse
They have some valid complaints but bothowdy do they sound like they are whining quite a bit.
That’s what happens when you criticize something.
Did you read it? If you did, what tone did you feel it conveyed?
If you didn’t, why are you being such an ass when I’m trying to squarely state how I felt they conveyed their problems?
I read it and it sounded like general frustration while trying to be civilized. They laid out the reasons why the platform was failing them while noting things that were within and outside their control. For things outside their control, they listed the thought processes in how to overcome them. I thought they did a good job in communicating their issues.
But my response was to your reaction. You can’t write a critical piece like they wrote without coming off as whiny to a part of the user base.
That’s fair, and I appreciate you engaging with me.
The technical explanation of issues was definitely well done and presented the issues rather plainly. I don’t want to diminish the importance of the moderation issues. It just strikes me as a bit weird the replication compliants.
That’s kinda the entire point of federation, it could be better but until the lemmy devs figure out how to make all of the lemmy instances a kind of CDN on top of everything else files being put everywhere is the next best step.
Should moderation of those images be replicated just like the images themselves? Yes.
The commentary on forking lemmy felt unnecessary. Yes, once you fork it you own it. That’s how code works. But I’m also biased since I’m in IT.
So maybe it’s my profession or just me scrolling while at work dealing with developers who try to avoid doing work, planning work properly and don’t think through what they are asking but it came across as valid issues with a tinge of whine.
I don’t think that Lemmy provides everything that Beehaw wants in a platform, but I also don’t think Lemmy devs have planned out what a federated platform should look like.
But then I don’t see the Beehaw team trying to get around work. They have effectively been told by the dev team to build the resources they want to see on Lemmy, and so they are evaluating whether to put those dev hours into the existing platform or a new one.
That’s a kind of odd situation then.
Per beehaw, they are willing to pay a bounty to get things they want fixed/deved. I read that from one of the admin posts, can’t remember if it’s the first one linked in the post or second.
If lemmy has effectively said “go dev it” why hasn’t beehaw paid developers to handle the requests?
Maybe my radar is off but something seems a little weird between those two statements
If lemmy has effectively said “go dev it” why hasn’t beehaw paid developers to handle the requests?
Because Beehaw is evaluating whether doing so is a good idea or not, and a lot of that goes into whether Beehaw believes that Lemmy is a platform that can continue to fit its needs. So Beehaw is evaluating several options:
- Fund development within the Lemmy ecosystem.
- Fork Lemmy to get full control over development and fund the fork.
- Design and build a new platform from scratch.
- Do nothing.
Based on what was written, Beehaw admins seem to be leaning towards option 3 given the current quality of the existing code and lack of confidence in Lemmy devs.
And this kind of high level concept development is typical of organizations when choosing to spend money. It isn’t just a choice between spending money to fund development or not.
it came across as valid issues with a tinge of whine.
Maybe it’s because I’m not a native speaker, but I always understood “whine” as to mean: “complaining in an annoying way about something unimportant”. So I’m replying on that basis.
I get that the “replication compliants” touch on a fundamental design choice in the way how the federation is typically working through ActivityPub. But that doesn’t make their problem “unimportant”. The conclusion I’d take from that is that either there’s a need (for them, though perhaps for others too) to redesign Lemmy so it can fit that purpose or they made a wrong choice by using lemmy to build their platform.
I think at the moment they are debating which one it is.As for whether the way in which they complain is annoying… well, given that it’s a written text that can’t transmit non-verbal cues, I’d suggest not making too many assumptions or reading too much into it. Any complaint would sound annoying if you make the assumption that it comes from a position of entitlement, try to second guess or recontextualize it in a way that makes it no favors.
Just to establish common ground, we’re using different definitions.
“Speaking of complaining in a mildly annoying way” is a common definition we can agree on. I’ve never attached a level of importance to the definition and that may be due to me being a native English speaker.
They always seem to be whining about something.
Does Lemmy support account migrating? I know Mastodon can do it, but wouldn’t know if Lemmy does.
Lemmy Migrate works great for at least syncing subscriptions, but I think I read somewhere that it doesn’t work if the instances don’t federate together. Lemmy unfortunately doesn’t support actual migration of history and whatnot.
I wonder if you can make multiple hops. Hop from beehaw to A, then A to B?
You just do it in 2 hops?
