Downvote are limited to members of this community
Can you imagine, years ago how the internet was before? We know Facebook, Twitter, Tiktok, Youtube. We knew blogger, Tumblr, Skyrock... and long before, it was the forum era as phpBB..and mail-lists.
And now with ActivityPub, we are reshaping the web, and achieving much with lots of freedom. So thank you all, and welcome π€π
If you want to donate, double check on the official website and report any problem to mod team
Threadiverse
Blog
Microblog
Event
Audio
Streaming/live
Book
Culture review
Picture
Short-video
Video
Image Credits :
Avatar : Wikipedia Eukombos
Banner : David Revoy licence : CC-BY-4.0
Moderation process
We all make mistakes,
If your comment is reported, and brings up a complex issue, we will reach out to you and ask you to rephrase it.
Our goal, is to create a serene space for discussion. Nothing more.
If the post isn't edited to remove hurtful language element, we will have to remove it. It would be a shame because your comment was interesting and you took some time to write it.
In case of xenophobia, racism, transphobia, homophobia or harassment, it will be a permanent ban.
They're legitimate friction points.
In regards to instance selection paralysis, I think the solution is to invite people to instances specifically rather than an overarching community, software or protocol.
As for the Mastodon timeline, it should be a filter button that defaults to federated, one click to local, two to home.
like fediverse isn't an open source project that someone could actually contribute work to fix instead of write an article for internet points
everyone wants to be captain; no one wants to swab the poop deck
I think starting a discussion about these kinds of issues is important.
It's an area where all of OSS has issues. It comes with projects being developed by individuals their own requirements.
The challenge comes when "we" (the tech community) want to see such projects expand... Into the non-tech community. If that's to happen with any project, the requirements of that community need to be considered.
And they're a fickle bunch that are unwilling to learn how stuff works.
Just found it on this post: https://mitra.social/post/01978f30-5295-cb5b-38cc-a151f08fd9f1
Haven't had the time to do an in-depth review yet, probably later.
One of the reason, why /kbin has achieved the success (so large, that eventually took it down...) has been it solving much of these UX sins:
This was only by chance, but as /kbin was ~not already~ never ready for third-party hosting, there was only one non-Polish speaking instance of /kbin (flagship kbin.social). This is another reason, why registration numbers made briefly kbin.social's MAU greater, than that of entire Lemmy software!
But what about decentralisation? As I probably have argued when /kbin yet existed, the Threadiverse could as well consist only of lemmy.ml, piefed.social and a Mbin instance (or the Feediverse might by only mastodon.social, misskey.io, flipboard.com, and Pleroma/Akkoma instance) and still be decentralised. Several carbon-copy instances are the simplest way to make an interoperating network - but not the only one!
/kbin of course is a Threadiverse app and evades this sin by definition. A Lemmy user never has to browse an empty "timeline"
This is a cursed solution for this sin, but with so great scale of flagship instance (and no alternatives) much of the federation work has already been done by more determined people. And if not? Then...
... we can just say:
and call it a day. :D
Five. This has been solved partially by Lemmy and its community Announces, and partially by scale.
Six. Of course everything on Lemmy and compatible platforms has to be posted to a community. However /kbin's magazines did more than that. They also aggregated (already federated) microblog content based on included hashtags. The magazine mod could specify, what hashtags would be aggregated under the mag.
The sidebar on /kbin's posts also includes sections like Related Magazines, Related Threads and Related Posts (for toots etc.).
Seven. ... and Active People. And "People" is one of the entries on instance's navbar. Yes, different one for every magazine, so you could follow anyone active in the topic.
All of these has been inherited by Mbin, its fork (well, maybe not its size xd)
Do you have any idea why Mbin never got as active as Kbin was?
IMHO for the same reason why Myspace has over hundreds of millions of MAU and Spacehey has got only over million of users overall.
IMHO solving UX sins does not bring new users. It rather helps not to deter them.
The Great Migration from Reddit did not repeat with the same scale, as with Great Twitter Migrations. Even then, most people IMHO return rather to their already existing accounts on already existing instances. Fedia.io has over 5 thousands total users, less than dozen Lemmy servers.
With the lemm.ee going down, we will witness a MAU drop. A non-zero number of people care no more about federation and will not make a switch.
There might not be enough stock of users to repeat /kbin's growth right now. Even recent developments at PieFed make its MAU number only slightly larger than Mbin
The best way to do a migration is to do it with joy and awe. Mbin has no kbin.social's big numbers, no ernest's individual vision, no marketing, no promise of awesome development, and a rump of spontaneously forming culture of the flagship instance.
Many of these "redemptions" still depend on scale - both of the local instance... and the external Fediverse. /kbin and Mbin benefit from Mastodon, but its MAU is shrinking too...
People don't generally flock for a software. Maybe for wobbly windows, but we are not doing e.g. Misskey-Flavoured Markdown here (yet?)
Tbh it reads more like a concerned tech person thinks that everyone except them is confused little kitten, not like a list of a real problems that someone experienced. Some of the problems are real some are completely made up 'problems'.
In fairness, I agreed with his first point to an extent about the difficulty normal people have even understanding the concept of instances. I did once to try to explain it to my mom and was completely unsuccessful. The best metaphor I came up with was that itβs like choosing your local AAA office. You know theyβre all AAA but this one might have a theme or perks that you prefer over others. Itβs not Location based itβs more theme-based, but same idea. Itβs not perfect, but she still didnβt really get it. But then when he refused to demonstrate his solution to the problem, and said weβll have to wait for his next post to find out, my mind started wandering and I stopped reading.
You use different phone providers can still call each other
This may be even better than the email analogy.
You haven't ever used email before? That's an obvious and easy explanation that most people understand.
Your tone is not nice
It wasn't my intention and re-reading it I can't find anything that will make it nicer or less nicer. π₯΄
I think conceptually to us that works, but it really doesn't work for the average person.
Partly because you get "if it's like email, why not just use email?". Most people don't understand how email even works, that it's a kind of federated system, that their account resides with a certain provider/host, etc.
People were starting to get it in the late 90's/early 2000's, but then Yahoo/Google happened, then smartphones.
And kids who grew up with smartphones often really don't get how things work, because their experience is with a capability-limited device where that stuff is even more obfuscated.
At best, average people think in terms of an app, and are utterly uninterested in any behind-the-scenes stuff. And to them, picking an instance is behind-the-scenes. "Why do I have to do any of this?" I mean getting people to create an account and track passwords is hard enough.
In my circle people understand emails, and they aren't easily stupified by smallest things and don't rage quit on encountering first unknown word. I have no idea how people think and don't really want to. Blog post insists on corporate metrics for conversions and whatever for registration flows, you on kids not getting simple concepts.
Fedi grows in organic ways and isn't an interesting place for everyone and that's fine.
I really don't see good encouraging even more people on a single instance. I can only see that creating more unbalance.
And what is the solution to the timelines, removing them for all users? I've used the local filter to pick instances when I needed it.
