lele :Volt: 💜 on Nostr: #[0] I wouldn't say that anything that makes onboarding easier for new users is ...
npub188q3683vez7v4mnugjv4nf6ud3z9mkn2h7kgc76z6ph6advw5vdqdj3jlx (npub188q…3jlx)
I wouldn't say that anything that makes onboarding easier for new users is therefore a good decision over all.
While it is true that there still is the possibility to choose your own server, it is obviously not the intended option to choose.
Like npub1gyqyejxm3ev40kty89f46pu2f36k298a2nmu0m7cj0vmtehwvjzsn87ds5 (npub1gyq…7ds5) already mentioned, the wording is kind of confusing. It implies you have to host your own server, which in fact most users don't do. Additionally, the mastodon.social button is clearly designed more prominently with a filled, colored bottom in contrast to a gray outline one. Welcome to the wondrous world of dark patterns.
Even if it's not intended by the devs to centralize Mastodon, the current growth of mastodon.social in addition to the changes in the app onboarding will push exactly this development. So I don't see why we should support one specific instance. There are several issues which arise because of big instances, some of them explained by others in the replies (scalability, moderation, security etc.).
Account migration is only a partial solution, considering Posts don't migrate to new instances (yet).
Is there a way to fix this? Sure. One of the most popular suggestions I see is changing the button to show random general purpose instances with good reputation. This would simplify the sign-up process while not favoring one single instance. Another potential solution is a redesigned username picker which includes a server list.
Furthermore, the "use my own server" button could be phrased differently to avoid confusion.
On top of this, Mastodon doesn't really seem to care after they send Issue Updated Welcome-Screen (IOS-134) #1005 to the shadow realm by tagging it as off-topic. (In defense Issue #1023 is still open and gets currently some nice mockups)
I wouldn't say that anything that makes onboarding easier for new users is therefore a good decision over all.
While it is true that there still is the possibility to choose your own server, it is obviously not the intended option to choose.
Like npub1gyqyejxm3ev40kty89f46pu2f36k298a2nmu0m7cj0vmtehwvjzsn87ds5 (npub1gyq…7ds5) already mentioned, the wording is kind of confusing. It implies you have to host your own server, which in fact most users don't do. Additionally, the mastodon.social button is clearly designed more prominently with a filled, colored bottom in contrast to a gray outline one. Welcome to the wondrous world of dark patterns.
Even if it's not intended by the devs to centralize Mastodon, the current growth of mastodon.social in addition to the changes in the app onboarding will push exactly this development. So I don't see why we should support one specific instance. There are several issues which arise because of big instances, some of them explained by others in the replies (scalability, moderation, security etc.).
Account migration is only a partial solution, considering Posts don't migrate to new instances (yet).
Is there a way to fix this? Sure. One of the most popular suggestions I see is changing the button to show random general purpose instances with good reputation. This would simplify the sign-up process while not favoring one single instance. Another potential solution is a redesigned username picker which includes a server list.
Furthermore, the "use my own server" button could be phrased differently to avoid confusion.
On top of this, Mastodon doesn't really seem to care after they send Issue Updated Welcome-Screen (IOS-134) #1005 to the shadow realm by tagging it as off-topic. (In defense Issue #1023 is still open and gets currently some nice mockups)