I don't like the clickbait title at all -- Mastodon's clearly going to survive, at least for the forseeable future, and it wouldn't surprise me if it outlives Xitter.

Still, Mastodon is struggling; most of the people who checkd it out in the November 2022 surge (or the smaller June 2023 surge) didn't stick around, and numbers have been steadily declining for the last year. The author makes some good points, and some of the comments are excellent.

you are viewing a single comment's thread
view the rest of the comments

[–] ArchRecord@lemm.ee 23 points 21 hours ago (1 children)

short form content with just a few sentences per post sucks.

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:

"When [people] design an internet service that is edited by a vast anonymous crowd, they are suggesting that a random crowd of humans is an organism with a legitimate point of view." (This is in reference to Wikis like Wikipedia)

"Different media designs stimulate different potentials in human nature."

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:

"A design that share's Twitter's feature of providing ambient continuous contact between people could perhaps drop Twitter's adoration of fragments."

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,

"We don't really know, because it is an unexplored design space."

[–] grue@lemmy.world 5 points 19 hours ago (2 children)

Non-file based computing is a highly unexplored design space.

No it isn't; that's what databases are.

[–] ArchRecord@lemm.ee 3 points 18 hours ago* (last edited 18 hours ago) (1 children)

That's what some databases are. Most databases you'll see today still inevitably store the whole contents of the DB within a file with its own format, metadata, file extension, etc, or store the contents of the database within a file tree.

The notion of "lock in" being used here doesn't necessarily mean that alternatives don't or can't exist, but that comparatively, investment into development, and usage, of those systems, is drastically lower.

Think of how many modern computing systems involve filesystems as a core component of their operation, from databases, to video games, to the structure of URLs, which are essentially usually just ways to access a file tree. Now think of how many systems are in use that don't utilize files as a concept.

The very notion of files as an idea is so locked-in, that we can rarely fathom, let alone construct a system that doesn't utilize them as a part of its function.

Regardless, the files example specifically wasn't exactly meant to be a direct commentary on the state of microblogging platforms, or of all technology, but more an example for analogy purposes than anything else.

What social media platforms don't have some kind of character limit?

What platforms don't use a feed?

What platforms don't use a like button?

What platforms don't have some kind of hashtags?

All of these things are locked-in, not necessarily technologically, but socially.

Would more people from Reddit have switched to Lemmy if it didn't have upvotes and downvotes? Are there any benefits or tradeoffs to including or not including the Save button on Lemmy, and other social media sites? We don't really know, because it's substantially less explored as a concept.

The very notion of federated communities on Lemmy being instance-specific, instead of, say, instances all collectively downloading and redistributing any posts to a specific keyword acting as a sort of global community not specific to any one instance, is another instance of lock-in, adapted from the fediverse's general design around instance-specific hosting and connection.

In the world of social media, alternative platforms, such as Minus exist, that explore unique design decisions not available on other platforms, like limited total post counts, vague timestamps, and a lack of likes, but compared to all the other sites in the social media landscape, it's a drop in the bucket.

The broader point I was trying to make was just that the very way microblogging developed as a core part of social media's design means that any shift away from it likely won't actually gain traction with a mainstream audience, because of the social side of the lock-in.

[–] Drunemeton@lemmy.world 3 points 17 hours ago

Wow!

“Minus is a finite social network where you get 100 posts—for life.”

[–] nanook@friendica.eskimo.com 2 points 19 hours ago (1 children)

@grue @ArchRecord An example of a database that doesn't keep it's data in files?

[–] ArchRecord@lemm.ee 5 points 18 hours ago

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."