• 0 Posts
  • 18 Comments
Joined 2 years ago
cake
Cake day: September 27th, 2023

help-circle
  • Yeah, I think “forumverse” isn’t bad. Though I have always felt like a Reddit-like interface and a forum interface are fundamentally different, in some way I can’t really put my finger on. I’ve been involved in bulletin board forums (fora?) in one aspect or another since the late 90s, so maybe it’s just nostalgia vs. recency bias; though it could also be the feeling that a “forum” seems like it should be hyper-specific, with different subforums on an already-niche bulletin board scoping down to even more niche and specific areas.

    (Side note: Actually, now that I think about it, maybe the forum -> topic -> thread connection is why people like the name “threadiverse.” The word “thread” definitely seems like it arose from there.)

    Anyway, I am fully ready to admit that I’m yelling at clouds here. Get off my lawn, dang kids and all that.



  • I don’t think likes serve the same function as votes. The downvote, the ranking as a function of score and recency, and the surfacing and consensus-building that comes as a result are the main point of this sort of platform.

    By contrast, the microblog “like” (at least on a platform without an algorithm, like Mastodon) doesn’t do anything other than express appreciation.

    Threads are common in pretty much every form of social media now, from friend-aggregation sites like Facebook and Friendica to messaging services like Discord and Revolt. They’re hardly exclusive to a Reddit/Lemmy-type service. Mastodon even organizes posts into threads (though I think that it does so in a much more clumsy way).

    (Edit: by “don’t they have votes?” do you mean polls? Because that’s a completely different function altogether than the Lemmy/Reddit vote.)





  • I’m not saying it’s a matter of desire. It’s a matter of time. A full-time developer has to feed their family, so they have to put most of their time into the stuff that makes them money. That means that their passion project is just naturally going to get less time as a function of the number of hours left in the day and the amount of energy for coding that the developer in question has.

    Further, ux design is a less “atomic” process; small amounts of time working on ux is going to have less impact than small amounts of time in coding. A programmer could conceivably fix a bug or make a minor improvement or feature request in ten minutes, and a Wikipedia editor could spend ten minutes improving the grammar and punctuation of an entire article; but the ux process requires mockups, iteration, asset creation, and coding for every change—and even if that can be done in ten minutes, the rest of the ui will look completely different, meaning that the overall ux will be worse than before, despite that one thing looking better.

    What can we do to change it? Companies that rely on FOSS should donate to projects so that the people who work on them can afford to do so at least part-time, or empower their own employees to contribute to FOSS on company time. Those are really the only two options, barring some sort of UBI or public grant for open source software.






  • Yes, although the protocol is already open, which I think mitigates the risk slightly. Bluesky is also organized as a public benefit corp, which mitigates the risk almost not at all but is interesting. If Bluesky begins to go the way of Twitter, other corporations or entities can make interoperable replacements easily. That was not so for Twitter.

    But in general, yes. This is the same song but a different verse. People have been so blinded by the brokenness of the internet as it is now that an interoperable protocol doesn’t make any sense to them.