masterspace

Oh wow congrats, like half the world writes software, I also write software for a living, but I don’t confuse the admins running my software and using my admin portals with the primary users of my software who will determine whether or not it will be popular or a success.

Back up and examine the context of the conversation and then stop with this pointless semantic distinction. In the context of whether or not your social network software will be successful, an admin setting that allows one instance to connect to other is not a user facing feature.

People do not open Reddit to examine how the Reddit admins configured their kubernetes clusters, so stop with this dumb bullshit pretending like users care about federation. They want somewhere to come have a discussion with everyone else interested in the same thing. That’s it.

No, they’re not. They’re admins.

If that were true, then the software wouldn’t have the ability to defederate built directly into it in the admin panel.

A setting in an admin panel is not a user facing feature.

IMO the point of any open source software is the noone really has ownership over what “the point” of it is. Anyone can take that software and use it how they see fit.

In broad strokes yes, but in more specific and relevant strokes, the point of social networking software is for users to use it to engage with each other, not concern themselves with how it’s servers are administrated.

People like good software that behaves intuitively, news at 11.

I’m sorry, but no. The point of the fediverse is not to spin up niche communities, since we already have forums. You want to be part of a niche small forum, go spin up your own bb instance and run a niche small forum.

The point of the fediverse is to recreate the global social networks that are twitter / Reddit / etc, but to do so using open source servers that are decentralized and anyone can host.

Again, federation is not a user facing feature, it’s an architecture / implementation detail. Fediverse enthusiasts are like train enthusiasts who love every detail of how they’re built and their history and how much philosophically better they are than cars, but none of that matters and train networks will fail if they don’t provide quick and convenient transportation to their users.

Software exist to solve a user’s problem. All software’s primary motivator should be user experience.

It’s quite frankly asinine to spend your time building a social network that user’s don’t want to use (see: Reddit’s official app / new site).

Ignoring psychology, network effects, and how social networks work while instead trying to build one based on naiive dogma is doomed to failure.

I’m already starting to get pretty tired of people in the fediverse saying shit like this:

What this means to you is when a user within one instance (e.g. Beehaw) that’s chosen to defederate with another (e.g. lemmy.world), they can no longer interact with content on another instance, and vice versa. Other instances can still see the content of both servers as though nothing has happened.

A user is not limited to how many instances they can join (technically at least - some instance have more stringent requirements for joining than others do)

A user can interact with Lemmy content without being a user of any Lemmy instance - e.g. Mastodon (UI for doing so is limited, but it is still possible.)

Considering the above, it is important to understand just how much autonomy we, as users have. For example, as the larger instances are flooded with users and their respective admins and mods try to keep up, many, smaller instances not only thrive, but emerge, regularly (and even single user instances - I have one for just myself!) The act of defederation does not serve to lock individual users out of anything as there are multiple avenues to constantly maintain access to, if you want it, the entirety of the unfiltered fediverse.

Having “multiple avenues to maintain access to the unfiltered fediverse, if you want it” is the most nightmare user experience sentence I can possibly imagine.

A user does not want multiple avenues to maintain access to the unfiltered fediverse with it being unclear when their comments will be shadow banned and not. They want to be able to see a post and go in and comment on it.

Federation is not a feature, it’s an implementation detail.

It’s working for me, but quoted below:

Regarding Beehaw defederating from lemmy.world and sh.itjust.works, this post goes into detail on the why and the philosophy behind that decision. Additionally, there is an update specific to sh.itjust.works here.

For now, let’s talk about what federation is and what defederation means for members of Beehaw or the above two communities interacting with each other, as well as the broader fediverse.

Federation is not something new on the internet. Most users use federated services every day (for instance, the url used to access instances uses a federated service known as DNS, and email is another system that functions through federation.) Just like those services, you elect to use a service provider that allows you to communicate with the rest of the world. That service provider is your window to work with others.

When you federate, you mutually agree to share your content. This means that posting something to a site can be seen by another and all comments are shared. Even users from other sites can post to your site.

Now when you defederate, this results in content to be no longer shared. It didn’t reverse any previous sharing or posts, it just stops the information from flowing with the selected instance. This only impacts the site’s that are called out.

What this means to you is when a user within one instance (e.g. Beehaw) that’s chosen to defederate with another (e.g. lemmy.world), they can no longer interact with content on another instance, and vice versa. Other instances can still see the content of both servers as though nothing has happened.

A user is not limited to how many instances they can join (technically at least - some instance have more stringent requirements for joining than others do)
A user can interact with Lemmy content without being a user of any Lemmy instance - e.g. Mastodon (UI for doing so is limited, but it is still possible.)
Considering the above, it is important to understand just how much autonomy we, as users have. For example, as the larger instances are flooded with users and their respective admins and mods try to keep up, many, smaller instances not only thrive, but emerge, regularly (and even single user instances - I have one for just myself!) The act of defederation does not serve to lock individual users out of anything as there are multiple avenues to constantly maintain access to, if you want it, the entirety of the unfiltered fediverse.

On that last point, another consideration at the individual level is - what do you want out of Lemmy? Do you want to find and connect with like-minded people, share information, and connect at a social and community level? Do you want to casually browse content and not really interact with anyone? These questions and the questions that they lead to are critical. There is no direct benefit to being on the biggest instance. In fact, as we all deal with this mass influx, figure out what that means for our own instances and interactions with others, I would argue that a smaller instance is actually much better suited for those who just want to casually browse everything.

Lastly, and tangential, another concern I have seen related to this conversation is people feeling afraid of being locked out of the content and conversation from the “main” communities around big topics starting to form across the Lemmiverse (think memes, gaming, tech, politics, news, etc.) Over time, certain communities will certainly become a default for some people just given the community size (there will always be a biggest or most active - it’s just a numbers game.) This, again though, all comes down to personal preference and what each individual is looking to get from their Lemmy experience. While there may, eventually, be a “main” sub for <topic xyz> (again, by the numbers), there will also always be quite a few other options for targeted discussions on <topic xyz>, within different communities, on different instances, each with their own culture and vibe. This can certainly feel overwhelming and daunting (and at the moment, honestly it is.) Reddit and other non-federated platforms provided the illusion of choice, but this is what actual choice looks and feels like.

[edit: grammar and spelling]

As for the confusion / chaos around multiple/redundant/competing communities and so on…that will get better over time as people figure things out. Honestly it’s not that different than reddit with all of its splinter subs like “true-” whatever.

That’s true for just the duplication problem, but the defederation / shadow banning issue is not one that reddit has and is pretty confusing and poor user experience for new users coming in.

Signing an NDA to talk about an unreleased product is not predatory, it’s standard practice for virtually any business (especially the kind inviting random people off the internet to see them). Many jobs require you to sign NDAs just to go through the interview process.

There is nothing gained by not going to the meeting with Meta, if they want to launch their Twitter clone they are more than capable of doing that regardless of whether or not this guy takes a meeting to hear them out. All he’s done is learned less about what they plan on doing leaving him less capable of taking the best course of action, and if you trust him to make the right decision then that’s objectively a bad thing.

Such bravery coming from someone who sounds oh so employed.

That’s standard practice if you’re going to be talking about an unreleased product.

This is not a proper talk by meta that you could just “hear them out”. They explicitly said off the record and confidential, there’s no reason for that if it’s something innocuous.

They plan on showing demos of their product to them or talking about potential features it might have. Boom, they require an NDA.

I don’t think you understand how the professional world works or how common NDAs are. I’ve signed NDAs while going through interview processes at FAANG and other large companies just so that we can talk freely about projects I might work on. Especially for a company like Facebook where everything they do will get about a dozen news articles written, they’re going to make you sign an NDA for any conversation about an unreleased product.

Having a larger market = having a larger network = greater network effects for content

Having Meta join with Mastodon might actually sway people off twitter and into the fediverse where it will be easier to migrate over to a different instance.

It’s foolish not to hear them out, you accomplish nothing. This isn’t some silicon valley episode where he has some arkane secrets that meta engineers couldn’t figure out that he might leak. Meeting with them is zero risk and he would gain more information on what they’re planning.

Meta is more likely to pull people away from Twitter than Mastodon is, and having all of Twitter be run with ActivityPub / open to federation is a good thing.

The crappy scripts that I wrote while teaching myself to code at an electrical engineering / architecture firm are used more often than the professional software I’ve built for FAANG and Fortune 500 companies since.

That’s an upside, but it’s not necessarily a “good” thing to be fragmented if it means you don’t have the network effects to make a satisfying community.

End of the day a lot of Reddit’s value came from its popularity.