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

help-circle



  • arm still needs a custom kernel and conpletely different drivers to even boot, because every manifacturer can implement it completely differently.

    Dunno why you’re getting downvoted, this is correct. ARM makes comparatively very expensive to maintain an OS over a variety of CPU models. The specialization required by each Cortex revision (and beyond that, each manufacturer adaptation) is too intense for a world trying to conserve resources.

    x86 hardware is standardized in a way where you don’t need to port an os to them, it just runs with generic drivers.

    That being said, I’m honestly shocked your friend doesn’t run into issues. Several ISA extensions have been released for x86 since the Core 2 Duo days, and I have to imagine software incompatibilities appear semi-frequently. Running Windows 10 on that can’t be a good experience.


  • If there was an option that was presented to users once the device got below 80% battery health to slow down the system to make daily batter life longer

    This isn’t why they did it. Degraded Li-ion batteries cannot sustain their rated voltage at high currents due to increased internal resistance. Sufficiently undervolted CPUs/memory cells produce errors (specifically bit flips), which can rather quickly lead to memory corruption and a crash.

    Reducing the CPU frequency (thereby reducing the peak current draw) is practically necessary in the face of a degraded battery. Various laptops were infamous for not doing this, because it resulted in a ~20-30 minute battery life, as the voltage drop became too great once the battery charge drops below 80-90%. Within the context of a smartphone, neglecting to use the remaining 80-90% would make it basically useless.

    What Apple (and the rest of the smartphone industry, at this point) really needs to do is make their batteries replaceable.







  • 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?







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