this post was submitted on 17 Jun 2023
220 points (100.0% liked)

Technology

37747 readers
230 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

Like many, when the recent defederation went down, I decided to create a couple other logins and see what the wider fediverse has had to say about it.

I've been, honestly, a bit surprised by the response. A huge portion of people seem to be misidentifying communities as belonging to "lemmy" as opposed to the instances that host them. I think a big portion of this seems to be a fundamental misunderstanding of what this software is, and how it works.

For example, lemmy.world users are pissed at being de-federated because it excludes them from Beehaw communities. This outrage seems wholly placed in the concept that Beehaw's communities are "owned" by the wider fediverse. This is blatantly not how lemmy works. Each instance hosts a copy of federated instances' content for their users to peruse. The host (Beehaw in this example) remains being the source of truth for these communities. As the source of truth, Beehaw "owns" the affected communities, and it seems people have not realized that.

This also has wider implications for why one might want to de-federate with a wider array of instances. Lets say I have a server in a location that legally prohibits a certain type of pornography. If my users subscribe to other instances/communities that allow that illegal pornography, I (the server admin) may find myself in legal jeopardy because my instance now holds a copy of that content for my users.

Please keep this in mind as you enjoy your time using Lemmy. The decisions that you make affect the wider instance. As you travel the fediverse, please do so with the understanding that your interactions reflect this instance. More than anything, how can we spread this knowledge to a wider audience? How can we make the fediverse and how it works less confusing to people who aren't going to read technical documentation?

(page 2) 50 comments
sorted by: hot top controversial new old
[–] vtr@programming.dev 8 points 1 year ago (3 children)

I completely understand the reason for the current workflow. However, IMO that makes Lemmy almost unusable. I already have a programming and a gaming community that I can't use Jerboa on. That's pretty bad.

load more comments (3 replies)
[–] maynarkh@feddit.nl 7 points 1 year ago (3 children)

A huge portion of people seem to be misidentifying communities as belonging to “lemmy” as opposed to the instances that host them.

The thing that I think didn't sit right with a lot of people is that Beehaw's admins apparently said (I haven't seen it first hand) that they see a future in refederating with Beehaw's communities being kept private, only accessible to Beehaw users, while Beehaw users would get access to the wider Fediverse.

To be honest, I feel that it's Beehaw's prerogative to grant or revoke access to anyone on other instances, but also I wouldn't be surprised that in turn other instances would not federate with an instance that would not give access to other instances' users for its communities.

[–] freeman@lemmy.pub 4 points 1 year ago* (last edited 1 year ago) (7 children)

That’s sounds…not possible. At least at the current iteration of the software. It also seems like kinda the opposite of what the fediverse was meant to be.

I just looked at one of my communities and the only main setting is whether mods can post. You can’t set perms at the community level to exclude certain users or make them private

On the latter part of your reply. I agree. It is their prerogative but I do see obvious benefits of not going say…allowlist only federation

load more comments (7 replies)
load more comments (2 replies)
[–] foxuin@lemmy.sdf.org 6 points 1 year ago (1 children)

It will take more time to establish norms. Other instances will certainly defederate and folks will become more accustomed to what that defederation means.

Instances are very vulnerable right now. There's not much ability to trust or predict how the owners of your instance will behave, because there isn't a long history of past behavior to look back on, so understandably some users will be frustrated by the lack of stability.

I do see one huge issue with how people are being instructed to join lemmy, which is that most resources tell people it doesn't matter which instance they join. That becomes fundamentally untrue with defederation.

load more comments (1 replies)
[–] unknowing8343@discuss.tchncs.de 6 points 1 year ago (5 children)

Instances hold copies of other instances' communities? I thought it was simply an API call to the other server. Not an expert, tho.

[–] Cipher@beehaw.org 8 points 1 year ago* (last edited 1 year ago)

That is correct, and this is why a new instance only shows the most recent 20 posts for a community until someone from the viewing instance subscribes to it. From that moment forward (barring de-federation), the host instance sends updates to the viewing instance. The viewing instance provides content to its users from the local copy that it stores.

load more comments (4 replies)
[–] jeena@jemmy.jeena.net 5 points 1 year ago

I think if every instance was a one person instance then the mods would not have the hammer sollution to defederate thousends of people at once. Back in the days they would ban a IP range, it's simmilar.

But to not need to do that, there need to be better tools available for them, we're waiting for those now.

[–] Hudsonius@lemmy.ml 5 points 1 year ago

This is so cool, these discussions remind me of events in the Bobiverse books where the spirit of these topics are similar. Also the start trek instance is totally getting this right from my perspective of things (startrek.website). Of course there are many ways to approach this as « right » is one’s opinion.

[–] maegul@lemmy.ml 5 points 1 year ago (1 children)

So for newcomers to the fediverse (also, hi!), mastodon has gone through debates and events too. People my differ on this, but I think the whole phenomenon is just a part of the fediverse and that it's fundamentally a good thing.

Where it causes drama or friction, I think it is essentially a different kind of friction compared to what happens on big-social platforms. And while it can have its problems or be mishandled, the problems, IMO, reflect real-life social dynamics more, and are therefore healthier than being subject to and at the whims of big-corporate overlords with many more interests other than true cultural and human engagement and interaction. Sometimes, people and whole groups of people just don't want to know each other. Free-speech and political discourse ideals aren't the catch all analysis here. This isn't the news papers or an academic journal, it's social media.

Bubbles are problematic but so are firehoses and incessantly unpleasant social interactions ... grouping and excluding is what we do ... it helps to match our finite minds and lives to the magnitudes of reality.

Beyond this, I think many are just not accustomed to real-life human dynamics playing a more structural role in their major social media life. There's an adjustment that needs to happen. And this goes both ways, for those against and those in defence of defederation actions, where attacks on defederation may miss the point and defenders may not see that there are sometimes better ways to manage problems.

Many of the attacks of defederation are along the lines of "this will stifle growth". I get it, and I've said the same myself elsewhere. But, one, not long ago no one thought any of this would "grow" and yet here we are, so maybe save the prognostications and try more substantial and constructive critiques. And, two, much of the above about transitioning to different modes of online socialising necessitates friction, where the fediverse is not simply your substitute for big-social waiting for the special moment you decide big corporations have crossed your line, rather, it's a different system, problems and all. Now, by all means, critique the fediverse (I sure do), but, I would recommend doing so with some of the above as part of your frame of reference.



For my money, the biggest problem right now is account mobility. Your account is stuck and limited to an instance. Mastodon has migrations but it's really just importing your settings and followers to a new account on a new instance rather than truly moving your account to a new host. This is baked into the current structure of the fediverse. Instances are first-class citizens, users are second-class. It is truly accurate, though somewhat pejorative, to use "feudal-verse" instead, because that is actually what it really is.

In terms of defederation, the problem this causes is that you can find yourself at odds with the federation policies of your instance and want to leave, which is obviously a PITA. More deeply, it's hard to know the federation policies of an instance before you join, or how they'll respond to some situations, so events like beehaw can be a little "shocking", and sometimes hurtful, because you find yourself labelled by your instance when you in reality have little alignment it, at least on the matter at hand.

Thing is, belonging to an instance or a community of some sort, finding a "home" of sorts with a group of other people, is probably a good thing, in line with my comments about healthier and more "in real life" dynamics. The issue is that instances and us being forced to join them is somewhat arbitrary, and once you end up having multiple accounts, just a PITA and ultimately bad UX.

What the fediverse really needs, IMO, is both grouping/community mechanisms and for our accounts and their hosting to be decoupled from these groups/communities.

Lemmy/kbin and the threadiverse as a whole do well in this regard by having sub-reddit/forum like structures. Mastodon and the microblogs struggle as they are quite bad at communities (as the BIPOC communities found out it seems). But, as it stands, the threadiverse still couples community hosting with account hosting, and so we have the beehaw defederation issue (which I should say is interesting to see as communities or reddit-like structures haven't been popular on the fediverse until now-ish).

Technologically, my suspicion is that this whole fediverse thing goes to another level once a coherent protocol provides for optional independence between account hosting and community hosting and, arguably, independence between the prior two and platform format. We have "self-hosting", but at the moment it's a bit of a hack, still binds you to platforms and hardly provided as a convenient service (check out Spacehost, an upcoming service for this: https://spacehost.one/).

I wonder about self-hosting scales and suspect it's awfully inefficient, and so, technologically, I suspect some hybridisation of the architecture is required, where the whole web2.0 idea of user->server->platform just melts away.

In reality, the only real innovation of the fediverse is to parallelise the "server" part user->server->platform so that a single user on a single platform can be achieved with horizontal scale and a distributed work load.

user->server->platform
    \-server-/
    \-server-/

This has the effect of FOSS social media being a thing (here we are and it's awesome TBH), but isn't really revolutionary from a user perspective. Once multiple platforms communicate over the same protocol, it starts to get revolutionary, but that's only started as anyone who's tried to mix mastodon and lemmy can attest to.

load more comments (1 replies)
load more comments
view more: ‹ prev next ›