Another traveler of the wireways.
I think it may also be worthwhile to toss in Bonfire, if looking for some pieces designed to hack together into a fediverse app. As I was looking up software the other day, I also saw some developing their software with Fedify, so there may be some resources to pull from there.
Tossing a mention to ya OP so you may catch this as well: @sentient_loom@sh.itjust.works
For people finding you, it means having to interact more in ways that encourage them to follow/subscribe to you, similar to how it goes now. For you finding stuff, it’s also similar in that you’d want to follow/subscribe to those that introduce you to others to follow/subscribe to. It’s really more for those that don’t mind putting forth effort to have their own online social space, much like the setup involved in having any online space.
It shines when you want to host multiple users with multiple different domains and identities.
Emphasis added. It’s that last part that drew me to include it. A single individual can prefer to portray themselves in multiple ways, particularly for different fediverse software (or even just different projects), so that’s why I included it.
Going to guess it’s one of the UrbanDictionary definitions, or in that vein…
Here I was thinking Ktistec was the most unfortunate, mainly as it’s awkward to remember & write.
When preserving culture is criminal, or punishable, ya might want to reevaluate your laws
In the meantime, people are gonna do it anyway 'cause why ask permission to back up and preserve your own stuff? And when the law finally catches up, some will be grateful to those that did so despite the earlier wrongful laws that tried to discourage them.
I think a better title & question would be, “Why is Mastodon struggling to thrive?”
It’s surviving no problem, but it’s not thriving for a multitude of reasons. Some are pretty well covered across comments here & in the linked discussion, and are more or less reiterations of prior discussions on the matter.
Ultimately I think as much as many of those reasons are correct, the biggest reason is the same as ever: network effects. All the jank and technical details could be endured and adjusted to if there was sufficient value to be had in doing so, i.e. following accounts of interest/entertainment, connecting with friends, etc. That’s proven to varying degrees by those that have stuck with Mastodon. In turn, however, it’s also clear by how many bounce off that for many there’s still insufficient value to be found across Mastodon instances to justify dealing with all the rough edges.
If Mastodon had enough broadly appealing/interesting people/accounts across its instances, people might deal with the various technical and cultural rough spots the same way they deal with similar on other social networks they may complain about yet won’t leave. There still aren’t enough of those sorts on there for many though, so Mastodon simply survives but doesn’t thrive.
Yes but no. Due to architectural differences, federation under AuthTransfer protocol is simply different compared to ActivityPub. In its own terms it is federated as individuals’ data is stored in personal data servers (PDSs) connected to a relay, which currently is only the Bluesky relay, that roughly speaking connects them to other personal data servers.
You can technically operate your own personal data server apart from those operated by Bluesky, but I think it’s fair to say the vast majority on there don’t. It’s not clear yet, apart from fully holding your own data, how useful it is to operate your own given you only have one relay to use anyway at the moment.
So even in its own terms Bluesky really isn’t federated in much of a meaningful sense yet. The problems are twofold: a major part of their pitch is making federation Just Work™, keeping the underlying tech out of mind to mitigate confusion, but you can’t have your cake and eat it too here. Eventually, if you’re really committed to meaningful federation, you have to teach people about the value of operating their own personal data servers, at minimum, otherwise what was the point in separating it out in the architecture?
Problem is, that goes against their pitch to their audience and spoils the appeal. It’s telling a good joke only to kill it by explaining to the one person that went, “I don’t get it.”
Secondly, they’ve already upfront said that relays may be cost prohibitive for many people to operate, resulting in only a few ever being spun up. If that remains the case and is true, then even if a few were spun up, that’s not any more federated or distributed than the rather consolidated web we see now. How much of a difference would it make if the social web was running on AuthTransfer and the major relays were owned and run by Meta/Facebook, Twitter/X, and Google?
Congrats you have your own data in a personal data server…But are you really the one running it, or did you just opt into the PDS entryway offered by Facebook/Twitter/Google/etc. because sorry, what’s that about a server?
Always happy to see more RSS-related tools emerge!
This is buried toward the bottom of the release notes so I’m bringing it up here:
Added instance-level default sort type
Any admins out there considering changing their instance sort settings or asking people on their instance if they’d like this changed, given that we can individually set sorting anyway? Taking into account the inclination of people to never adjust default settings (I remain deeply curious about this tendency, as an aside), I think it might be worth at least bringing up to one’s instance community.
If they decide they want it to remain the same, all good, and even better, it raises some people’s awareness that they can change it themselves.
To add to this, I think as long as decentralization involves having to know how to and have the money to operate a server, it’s not going to reach the point some may hope for. The monetary costs may be lower than ever, but that doesn’t address the knowledge requirements (not to mention time for setup and upkeep).
Even one of the more user friendly attempts at this so far (AT Protocol) doesn’t address this in a meaningful way, as one still has to get into the weeds of server config, domain leasing, etc.