271
Why is Mastodon struggling to survive?
(www.reddit.com)
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!
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
Because Threads and BlueSky form effective competition with Twitter.
Also, short form content with just a few sentences per post sucks. It's become obvious. That Twitter was mostly algorithm hype and FOMO.
Mastodon tries to be healthier but I'm not convinced that microblogs in general are that useful, especially to a techie audience who knows RSS and other publishing formats.
I 100% agree with this sentiment.
Jaron Lanier has a great book called You Are Not A Gadget, where he talks about the way we design and interact with systems, and he has some thoughts I think reflect this sentiment very well:
He talks about how when a system becomes popular enough, it can "lock in" a design, when others build upon it as standard. Such as how the very concept of a "file" is one we created, and nearly every system now uses it. Non-file based computing is a highly unexplored design space.
And the key part, which I think is relevant to Mastodon, the fediverse, and social media more broadly, is this quote:
Fragments, of course, meaning the limited, microblogging style of communication the platform allows for. I've seen some Mastodon instances that help with this, by not imposing character limits anywhere near where most instances would, opting for tens of thousands of characters long. But of course, there is still a limit. Another design feature by Twitter that is now locked in.
But of course, people are used to that style of social media. It's what feels normal, inevitable even. Changing it would mean having to reconceptualize social media as a concept, and might be something people aren't interested in, since they're too used to the original design. We can't exactly tell.
As Lanier puts it,
No it isn't; that's what databases are.
@grue @ArchRecord An example of a database that doesn't keep it's data in files?
I'm not a big expert on database technology, but I am aware of there being at least a few database systems ("In-Memory") that use the RAM of the computer for transient storage, and since RAM doesn't use files as a concept in the same way, the data stored there isn't exactly inside a "file," so to speak.
That said, they are absolutely dwarfed by the majority of databases, which use some kind of file as a means to store the database, or the contents within it.
Obviously, that's not to say using files is bad in any way, but the possibilities for how database software could have developed, had we not used files as a core computing concept during their inception, are now closed off. We simply don't know what databases could have looked like, because of "lock-in."
Memory is still structured like a file and referenced over addresses, we just call it something else.