this post was submitted on 17 Dec 2023
261 points (96.8% liked)

Fediverse

28395 readers
136 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
 

TL;DR: The current Mastodon-signup is only removing the confusion of users on first glance, because it either hides the server-choice altogether, or leaves them with a choice that is impossible to make at this point of their Mastodon-journey. Instead, it should introduce them to decentrality on a lower scale, with a handful of handpicked servers to choose from, such that the decision makes sense to them and shows them the merits and fun of the concept instead of scaring them away. Ideal would be to give them a sense of agency. Then, chances are higher that they consider migrating again in the future and eventually internalize it as a permanent option of the digital world.

all 49 comments
sorted by: hot top controversial new old
[–] MudMan@kbin.social 75 points 11 months ago (2 children)

I've been saying this from the go: users don't need to know decentralization even exists until AFTER they are signed up.

What Mastodon needs is a proper migration flow that moves old posts and remote follows so users can decide if they want a new instance after they spend some time in the system and start to understand how it works. Any mention of decentralization on signup is a churn point, because decentralization doesn't add any features to posting and reading posts. From a UX perspective, decentralization isn't a feature.

Things are about to get messier once the big decision coming in becomes "do you want to see Threads or nah?", which then actively requires thinking about a competing social media platform on the way into this one.

[–] Scrollone@feddit.it 30 points 11 months ago (3 children)

Not only decentralization is not a feature -- it's a burden. "Normal" users (read: non nerds like 99% of us here) couldn't care less about which server they should sign up to.

[–] ArcaneSlime@lemmy.dbzer0.com 11 points 11 months ago* (last edited 11 months ago) (1 children)

Tbh then just tell em to sign up for mastodon.social, or a specific instance you know they'd like since you know them fairly well, problem solved. They can migrate later if they want anyway, fuck it, they'll be fine. It's a masto acct not a limb amputation, like hair so to speak "it'll grow back."

[–] explodicle@local106.com 9 points 11 months ago* (last edited 11 months ago) (2 children)

Mastodon has account migration? Are we going to get that?

Edit: Yes. https://github.com/LemmyNet/lemmy/pull/3976

[–] ArcaneSlime@lemmy.dbzer0.com 6 points 11 months ago

Iirc I heard that is part of this update along with blocking instances but I haven't yet figured out how to do either, and my instance just logged me out with the update so I finally made the move to eternity and am learning that UI now too instead of jerboa, so it may be a minute before I do figure it out lol.

[–] panicnow@lemmy.world 1 points 11 months ago (1 children)

If you migrate your own account to a new server, do other people follows of you automatically migrate too? Or do all your followers need to then update to follow you at the new location?

[–] russjr08@bitforged.space 6 points 11 months ago (1 children)

I just did this the other week, all of your followers (who are on servers that are still online of course) will follow your new account and unfollow the old account.

It was a bit funny, because I had already signed into the mobile I used and was flooded with notifications as each account followed me (some might be slightly delayed, but all in all it didn't take more than an hour for the ~50 followers I had).

You will however want to export the list of people you follow from the old account though, because that isn't automatic. Once you plug the export file into the new account though it'll do the rest for you.

[–] panicnow@lemmy.world 3 points 11 months ago

That sounds very slick. I never really used twitter so had no reason to use mastodon instead, but I am glad it exists!

[–] Serinus@lemmy.world 2 points 8 months ago

And if it such a central feature

It's not. It's an important feature. It's not a central feature.

That's like saying two factor authentication is a central feature of Twitter. It's important, yes, but it's not central.

[–] Foxfire@pawb.social 4 points 11 months ago

Though if decentralization were to be hidden, it'd be a good idea to cycle through lots of well established general instances for user signups under the hood. The vast majority of people are just going to choose the default options, and if it's all going to funnel into mastodon.social, that's a lot of centralization of users. Ideally no single server lords over all the others in terms of user count, because that gives them lots of power other instances may feel compelled to abide by. Having power spread out across many different people helps keep things in check, at the very least making large or drastic decisions more of a round table affair.

[–] Nougat@kbin.social 22 points 11 months ago (2 children)

Here’s another way: stop referring to everything “Twitter-like” as Mastodon. Stop referring to everything “Reddit-like” as Lemmy. Those are both client platforms through which one can access ActivityPub content.

Conflating the platform with the provider with the protocol with the content is what’s confusing people.

[–] CoggyMcFee@lemmy.world 33 points 11 months ago (1 children)

Are you saying to start calling all of it ActivityPub? In which case, I would think that’d be extra confusing since lemmy and mastodon don’t cross-interface very well and you really need one client for each type.

[–] Nougat@kbin.social -2 points 11 months ago (2 children)
[–] CoggyMcFee@lemmy.world 10 points 11 months ago (2 children)

Great, can you explain what you mean? I did not follow.

[–] Nougat@kbin.social 1 points 11 months ago* (last edited 11 months ago) (1 children)

The article refers to ActivityPub-based "microblogging" by assuming that Mastodon is the only client application available for that purpose. It is not. Mastodon is certainly the most popular client application for that purpose, but it doesn't have to be. Other client applications exist, and a better or more popular client application could be created.

When the point of the article is to get people to comprehend that federated social media is not a "walled garden" --

People are using open, free Mastodon, but in their minds, they are still in a walled garden.

maintaining the notion that a single client application is the only way to read or create a certain kind of content is a big part of the very problem the article describes.

And the author seems to be aware of this:

Often, I hear about people trying to explain the idea behind Mastodon to someone, who is not on the Fediverse, they often explain it with e-mail. However, nowadays, people don’t even experience this “choice of service” even with e-mail anymore. They get their e-mail when signing up with google and that’s it.

GMail is not the only way to send and receive SMTP email. It's certainly a very popular way to do so, but you wouldn't describe a concern over people being blind to their choices of email providers (or, indeed, their ability to host their own email server) as

The current [GMail]-signup is only removing the confusion of users on first glance, because it either hides the server-choice altogether, or leaves them with a choice that is impossible to make at this point of their [GMail]-journey.

If the author, or anyone else, wants people to have a better understanding of the nature of federated social media, describing it wrong is not a path to that goal.

[–] CoggyMcFee@lemmy.world 5 points 11 months ago (1 children)

What would you prefer people use to refer to “Reddit-like” ActivityPub clients, and what would you prefer for “Twitter-like” ones?

[–] Nougat@kbin.social 1 points 11 months ago

I used "microblogging" earlier as a stand-in for "Twitter-like," and I shamelessly pulled that terminology from the kbin interface. It's accurate, but I don't know that the term is sufficient to gain popular traction - and I certainly do not pretend to be the person to dictate what the terminology ought to be.

Now that I think about it, the core of social media of all types is "someone posts a thing" (whether that thing is a link to something else or original text content), and other people comment on it. YouTube, Xitter, Reddit, slashdot, fark, etc etc. The display format, post and comment organization, tagging options - those are all ancillary.

Federation via ActivityPub introduces a wholly new aspect to social media by separating the client application from the content accessed therethrough. I, from kbin.social, can see and interact with content posted by someone originating from mastodon.social. Content is one thing, and client application another.

People do have familiarity with that kind of separation in at least one other internet functionality: email. People generally already understand that their web interface to their email provider allows them to send and receive email both within and without that provider, and that their mobile app is just a different way to access that same content. But SMTP email is old. Since then, the aim of content providers on the internet has been to capture and contain users, using existing protocols, which causes people to consider the provider and the content to be the same thing - because in so many cases, it is.

ActivityPub is a new(ish) protocol. Functionally, it is much more like email than it is like an internet forum of any kind. Extending this comparison, SMTP email is one-to-one (yes, there can be multiple recipients, but they are all themselves "ones"); ActivityPub is one-to-many. Yes, this is similar to traditional walled-garden forums, which are also one-to-many, but those walled-gardens restrict the "many" to "those who have accounts inside our garden." Perhaps ActivityPub is more accurately described as one-to-very many or one-to-all.

It probably seems that I am avoiding your clear and plain question. Maybe I am, but I also think it's important to consider the details of these as-yet-unnamed things in order to arrive at an appropriate and effective way to market them. Federated social media is a public forum in a way that previous internet forums have not been since Usenet. "Forumnet" seems like it could be workable. It's definitely more descriptive than "fediverse" (a name I have never been very pleased by).

While it gets closer, that continues to avoid your specific question. I will need to put a good deal more thought to this, and must now direct my attention elsewhere. Watch this space.

[–] wolfshadowheart@slrpnk.net 1 points 11 months ago* (last edited 11 months ago)

I'm not them but -

Forum style posts =\= reddit.

Short text style posts =\= twitter.

Just because lemmy is a forum style alternative to Reddit does not mean we should call it a reddit-like.

Just because mastodon is a short text style post alternative to Twitter does not mean we should call it a twitter-like.

It would be like saying reddit is a gameFAQs-like, but for more than just games. Is it inaccurate? Not exactly, but they are their own things. Related/inspired from each other, but so is basically everything that exists from art to practicality.

I think in this case, yes Lemmy was made as an alternative to the forum-image style posting that Reddit is now known for. However, lemmy and mastodon are far beyond that now too due to how it interfaces with ActivityPub (each instance being able to have its own community of the same name). It's created enough separation that it almost seems inaccurate now to entirely call these a "-like" alternative.

[–] Carighan@lemmy.world 19 points 11 months ago

I like this, though I will say I acutally prefer the playful choice idea. Not Hogwarts for me particular, but in general.

[–] Serinus@lemmy.world 13 points 11 months ago
  1. 2 is good.

Decentralization doesn't matter until it does. Recruiting people to your specific Mastodon instance is ideal and simple. All they need out of the decentralization concept is to know they can't be screwed if Elon takes over their instance.

[–] otter@lemmy.ca 9 points 11 months ago (2 children)

I'm curious about the state of account migrations right now. Ideally it should be super easy and it should strengthen the Fediverse if people can hope platforms with ease when an admin isn't behaving as they should.

One technical challenge might be deletion

  • Admins need to be able to delete or quarantine harmful / illegal content
  • You can't move instances if an admin suddenly comes along and deletes everything

Could on-device backups be a thing? The collective userbase takes up a lot of storage, but each individual person probably doesn't upload more than their phone can store. It might also incentivize them to not spam large files

[–] starman@programming.dev 8 points 11 months ago* (last edited 11 months ago)

Account migration and backup are features of lemmy v0.19

https://github.com/LemmyNet/lemmy/pull/3976

[–] CleoTheWizard@lemmy.world 6 points 11 months ago

I think account migration will have to come in two waves. It would be far easier to migrate accounts that are federated. That should be as simple as name swapping comments and posts and assigning them to the opposite servers while handing over user data.

The hard part is with servers who do not federate. Two solutions exist. One would have a data hop. It’s very likely that defederated servers would contain some link somewhere between federated servers. So the original server would pass data through one or two other servers to get to your new destination server that otherwise wouldn’t receive that data.

The other solution involves allowing a user to download their content with a key from the server and then present that to the new server. That data may need to be encrypted or have verification somehow to prevent tampering before reuploading it.

Any of these solutions will probably require manually approving and sorting through of data. The good news is that you can make requirements to say that users should have so many upvotes or whatever to receive a transfer to your platform. So their backup of data can sit still until you’re deemed worthy of transfer.

I’d say that data backups on your phone should definitely be an option regardless.

[–] stevecrox@kbin.social 7 points 11 months ago (4 children)

If you signup to social media it will pester you for your email contacts, location and hobbies/interests.

Building a signup wizard to use that information to select a instance would seemto be the best approach.

The contacts would let you know what instance most of your friends are located (e.g. look up email addresses).

Topic specific instance, can provide a hobby/interests selection section.

Lastly the location would let you choose a country specific general instance.

It would help push decentralisation but instead of providing choice your asking questions the user is used to being asked.

[–] Plopp@lemmy.world 8 points 11 months ago

Giving social media platforms access to my contacts? Ew. Never. However for those that want it it might be a good idea, except what if I don't want whoever has put me in their contacts to find me that way?

[–] astronaut_sloth@mander.xyz 5 points 11 months ago

Building a signup wizard to use that information to select a instance would seem to be the best approach.

That's actually not a bad idea. I'm not on board with mining contacts, but I think there's a simple, transparent way to do this that can actually be fun: a personality quiz. Sure, if someone knows what instance to join already, they can override this. But if they don't, they get like five questions, and then they are matched to an instance.

[–] shrugal@lemm.ee 3 points 11 months ago

The contacts would let you know what instance most of your friends are located (e.g. look up email addresses).

I don't think that's possible without creating a privacy nightmare, at least not with an identifier like the email address.

[–] russjr08@bitforged.space 3 points 11 months ago

To be honest, as an instance owner I would not want to even have that data touch my instance - that would be a nightmare waiting to happen whether some instance operator does so with or without malice intent (such as a server compromise).

[–] nycki@lemmy.world 6 points 11 months ago

I think the "migration" process needs more work. If you want to hop homeservers, you're going to lose your whole post history and all your followers. That's what keeps people stuck, more than the sign-up process itself.

[–] RobotToaster@mander.xyz 5 points 11 months ago

There's still nothing like awesome lemmy instances that shows a server's blocking and blocked by count?

That's the biggest hurdle for me, there's no guarantee who you want to follow won't be blocked by your or their BOFH.

[–] Illecors@lemmy.cafe 5 points 11 months ago

So... Am I missing something or are you suggesting an oligopoly, elected by a monopoly?

[–] Kecessa@sh.itjust.works 3 points 11 months ago* (last edited 11 months ago)

I think it should be like joining a mining pool, if you create a server you don't have admin privileges like they exist here at the moment, you're added to the pool of machines that stores info and users don't choose a server at all, the servers communicate between themselves to make sure all info is backed up on at least three machines.

From the front end it looks like any equivalent private social media, one website for everything. On the back end side the servers are all over the place instead of in a couple data centers.

Server owners could decide to ban certain communities from storing info on their server, but that wouldn't delete the community, it would just rely on being hosted elsewhere (hence the triple backup at all times) and users would be responsible for curating their own feed.

It would solve the issue of having to switch server if you disagree with the admin's decision and would make the experience much more user friendly. Each new server would improve the stability of the whole network by taking part of the load and making sure that if one server is down, others have the same content available so no user can tell that there's something wrong happening behind the scene.