• 0 Posts
  • 70 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle

  • But, I’m starting to realize that no amount of evidence is sufficient for folks who want to federate with Meta

    This is an incorrect assumption, because

    And somewhere in this very discussion some other person has given a very plausible overview of their potential EEE approach. I’ll add a link to that comment later when I have time to find it again.

    I would be very interested to read this! There are definitely limits to my optimism here. I think Meta is a horrible company and I don’t expect them to act in the best interests of the Fediverse; I’m just not yet convinced that them giving up what is essentially free and ad-free API access to one of their platforms cannot be used to our advantage. Threads federation could absolutely be catastrophic, but it’s also possible that it’s a good opportunity; that’s all I’m saying.


  • They will corrupt and exploit any environment they are a part of via any means they can.

    Right, unless they can’t, though. Ideally the Fediverse should be resistant to this kind of influence without resorting to defederation. I’m also concerned that defederating from Threads will make more Threads users than Mastodon users.

    We don’t need to be able to predict every last detail of how they will do so to know it is true.

    I mean, some idea of what they might do would be nice.

    They have a track record of being awful, anti-consumer corporate citizens. WHY would we want to try to invite them in and try to contain them?

    I couldn’t care less about Meta itself. My interest begins and ends with Threads users. There are a ton of people that would never give the Fediverse a try for one silly reason or another—predominantly, I would argue, the fear of the unknown—and this seems like it could be an opportunity to overcome that obstacle if leveraged correctly. The prospect of everyone and our parents using social media that is not completely beholden to Meta is exciting to me.

    Again, maybe I’m wrong, but this whole thing is basically an experiment, isn’t it? I’d like to see what happens before reaching any conclusions.


  • Maybe I’m just being naive, but this seems like an argument in favor of federating with Threads. One of the reasons Facebook and Instagram are so effective at driving engagement is that users have basically no ability to curate, sort, or filter the content that they see, especially since third-party clients are banned. You can’t even view most things without logging in.

    The implementation of ActivityPub in Threads is a strange departure in this context - (federated) Mastodon users can view all of the content Threads has to offer without subjecting themselves to Meta’s arguably predatory curation algorithms. It almost seems like an escape for people who want to use a Meta-sized platform without Meta getting its grubby little fingers all over your mental wellbeing.

    If people are worried that Threads will affect likes and comments (and therefore like/comment-based sorting algorithms) on other instances, it should always be possible to exclude Threads’s contribution to those metrics, no?







  • There’s a conflict between the linguistic and practical implications here.

    “kilo-“ means 1,000 everywhere. 1,000 is literally the definition of “kilo-“. In theory, it’s a good thing we created “kibi-“ to mean 2^10 (1024).

    Why does everyone expect a kilobyte to be 1024 bytes, then? Because “kibi-“ didn’t exist yet, and some dumb fucking IBM(?) engineers decided that 1,000 was close enough to 1,024 and called it a day. That legacy carries over to today, where most people expect “kilo-“ to mean 1024 within the context of computing.

    Since product terminology should generally match what the end-user expects it to mean, perhaps we should redefine “kilobyte” to mean 1024 bytes. That runs into another problem, though: if we change it now, when you look at a 512GB SSD, you’ll have to ask, “512 old gigabytes or 512 new gigabytes?”, arguably creating even more of a mess than we already have. That problem is why “kibi-“ was invented in the first place.





  • I have a Class 3 (28mph), it’s actually not too bad. That assumes the brakes are well-maintained, though, and as we know there are no inspections for e-bikes. I’ve seen some terrifyingly bad brakes on normal bicycles, so I can’t imagine what some people’s e-bikes look like.

    It should be mandatory for Class 2 and Class 3 e-bikes to have hydraulic disc brakes imo. I have mechanical disc brakes, and I have to tighten them at least once a month. It seems unwise to trust that the average person would also do that. Rim brakes are right out; they have nowhere near enough braking power for the speed and weight of most e-bikes.