👋 Everyone: see what you think:

The Seven Deadly #Fediverse UX Sins Part 2: The Road To Redemption: https://www.timothychambers.net/2025/06/24/the-seven-deadly-fediverse-ux.html

Don't claim that these are final answers - but hope they help continue constructive motion to final answers!

cc: @renchap @dansup
@cheeaun @scottjenson @newsmast @andypiper @ricmac @evan @laurenshof @pfefferle @fediversenews #fedidev #mastodev @timbray

The Seven Deadly Fediverse UX Sins Part 2: The Road To Redemption - Tim Chambers

''

Tim Chambers

So, I am still reading through this but I see a–to me– quite obvious issue with having a roulette of "trusted servers"

…What if your software barely even has other instances, letalone ones that would be considered "trusted"?

App.wafrn.net is to this day basically the only Wafrn instance that we know will be hear in 1-3 years from now; Even if only because we develop directly here; We simply don't have other instances to point to if we wanted to

Do we just note this down as being a painpoint of newer, less widespread software? Is the solution to just wait?

Granted we have some issues as to how we do updates that make running an instance sort of annoying; We don't do versioning, just to name one example. But I really feel like that point – while we were explicitly mentioned – kinda left out cases like ours

@alexia Trusted and vetted by each major Fediverse flagship site:

So Warfn.net would be one portal and it would set public minimum standards and choose the other warfn servers that met those commitments and requirements. One might be pledges to not shut down for xx months and to give yy months warning if they do.

@Tim Chambers @Alexia ΘΔ Of course, what makes a server "trusted" would have to be different from server software to server software.

For example, the criteria might include minimum moderation standards as well as a guaranteed minimum timespan between a shutdown announcement and the ensuing shutdown. But what fits Mastodon will not necessarily fit our three "nomadic" server applications. They largely put moderation into the hands of the users, appropriate tools for moderating their own streams included. And e.g. three months of warning ahead before a server goes offline are overkill for software that a) allows you to move your whole channel to another server at the drop of a hat and b) might not even make moving necessary if you've already cloned your channel.

Granted, the part with the clones currently only matters on Hubzilla. (streams) has only got two public servers with open registration as far as I know, and I don't know of Forte has any at all. So you've only got so many places, if any, to clone your channel to.

Still, if a server application is rather obscure, it only has very few servers, and not a single one of them actually counts as a "flagship" or "lighthouse" server, the whole application would remain absent from this system. This easily applies to (streams), not to mention Forte.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte #NomadicIdentity #Moderation #SelfModeration
Tim Chambers (@[email protected])

69.8K Posts, 5.48K Following, 18.1K Followers · Technologist, writer, who is fascinated by how new politics impacts technology and vice versa. #fedi22 #indieweb #fediverse

Indieweb.Social