Primary account is now @[email protected].

  • 1 Post
  • 26 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle

  • Just the standard “you can sue if you think this is unfair and have your day in court.”

    What it looks like is if China or Russia has a competitor to a US product (say, Yandex or Baidu), a US company (say, Google) could lobby the President to mark them as a threat and ban them from the US. The product doesn’t need to actually have the capacity to cause harm, it just needs to be from one of the adversary countries (currently China, Russia, N. Korea, and Iran).

    This is true, but it’s also pretty unlikely. Even TikTok is just a vine ripoff, but a vine that was successfully monetized.

    There really hasn’t been much to come out of our “foreign adversaries” that I think most people would care about. If that’s the price we have to pay … I’m not the least bit worried about it really.

    Furthermore, China is happy to use public money to back companies (as a sort of “state run venture capital”); that is a threat to competition in the same way venture capital is a threat to competition.





  • I haven’t given Discord a dime from the start because I knew this was going to happen.

    The entire premise of Discord’s free service was to gobble up the market from TeamSpeak, Ventrillo, and Mumble and capture the ecosystem using a ton of venture capital. In any sane world it would be an illegal mode of operation to provide “free service” based on venture capital like that.

    TeamSpeak did manage to react but their reaction has been slow (I think they’re a much smaller team and still a private company). Their new client is fairly feature complete but still not out of beta (AFAIK).

    Mumble is an open source project and is still ticking as a result as well (though obviously it’s received much less love since Discord stole the spotlight).


  • I had a buddy who was a Linux ARM laptop fanatic back in like 2014. Microsoft had been trying to make Windows on ARM a thing for years before that.

    Apple was the first to popularize it but it’s been a work in progress if you’ve been paying attention for a LOT longer. What helped Apple is all the work they did on their own ARM chips for iOS. They managed to get pretty close to x86 performance in an ARM chip. They also had an app store of apps that could run on them and an emulator for things that wouldn’t.

    Every time Microsoft tried nobody would release ARM builds… People just bought the x86 laptops. It’s the same chicken and egg problem desktop Linux has had for years.





  • Battery life always goes to crap almost exactly 2 years after purchase

    Disposable battery technology is disposable. We don’t have truly rechargable batteries yet … and the EV batteries only last longer (AFAIK) because they’ve got better cooling systems and are higher grade – read more expensive – components.

    Appliances use plastic parts and come with a plethora of unnecessary features all on one circuit board so when one feature breaks the appliance is dead

    That’s not the entire story there … it’s just cheaper to make it one board. You can eliminate some points of failure by using one board as well.

    It’s definitely ridiculous appliance companies aren’t providing parts. I’d also like to point out … I was specifically responding to the widespread e-waste from the mobile devices sector. Not “all things that could possible become e-waste in 2024.” GUARANTEED planned obselence is what has been happening there for years with “2 years of device security updates” and that nonsense is ending.

    There’s even a story going around about a business-class HP printer

    Yeah, don’t buy HP.

    It’s gone long past planned obsolescence at this point. Whether it’s software or hardware, companies want you subscribed for life. Anything less and they break the devices that were able to dupe you into thinking you owned.

    Subscriptions aren’t necessarily the enemy when it comes to e-waste. They’re bad for ownership, but they’re not bad for planned obsolescence and e-waste. If your subscribers need your device to keep working to keep paying you, you’ve got a much stronger incentive to keep the device working vs just abandoning it.

    This already happened with software, there really isn’t “buy once then buy again and again and again” software anymore, the vast majority of software has gone subscription. This is also true of online games like CSGO, Hunt Showdown, Fortnite, etc.

    It’s just a matter of making things into subscriptions that are mutually beneficial. Your printer being an InkJet printer with a vendor locked in subscription that doesn’t offer any real service is absurd and should be illegal. Your smart home camera having a subscription to store cloud video, provide new features and security updates … that’s a reasonable service that a lot of “normal” people don’t want to do themselves (and incentivizes manufactures to keep their devices working so you keep paying).

    A big part of the problem with e-waste is that companies setup fancy features to sell a product but didn’t plan for how to support that product’s software for the life of the product (because they’re not making any more after the point of sale) … so we end up with a very insecure piece of unserviceable e-waste.

    Don’t get me wrong we’ve still got a long way to go before we find a solution that handles the problem for all the various devices being manufactured these days. However, credit where it’s due the mobile devices sector / “big tech” is doing better than they have for the last 15 years, and that’s all I’m trying to contest. There IS change happening.


  • This is speculation by Ars Technica. Essentially, a recent firmware upgrade seems to have drastically lowered the battery life of some models. In addition, they are removing all third-party apps in the EU in response to the DMA.

    Sounds like it’s more speculation from users published by Ars … which is fair but also needs to be taken to some degree with a grain of salt. This is not expert commentary, this is personal anecdote. It’s a grievance I have with a lot of media, e.g., interviewing random people on the street for “their take” … they don’t necessarily know what they’re talking about.

    I’d flag this as concerning but, it’s also not uncommon for updates to devices to require more resources, with requires more power and can definitely be done accidentally. There’s the doomer argument that it’s all malicious planned obsolesced under the guise of plausible deniability … but I wouldn’t be so sure. They’re selling subscriptions for fitbit, for a subscription model to work, the fitbit needs to work; it’s against their own interest in continued revenue to brick the devices.

    Google does need better support in general; it’s not uncommon for bugs to go unfixed for way longer than should be acceptable.

    Most recently Roku.

    That’s not a bricking from a firmware upgrade; it is scummy though.

    Google’s history of bricking its smart home products goes back to at least 2016

    They’ve discontinued products they haven’t launched but purchased, that’s not quite the same thing. Even some very old nest cams are still working just fine (again it’s against their best interest to sell subscriptions and have devices that they’re selling subscriptions for dropped from support/virus ridden/etc). That’s a bit scummy but it does make sense from a “we want some of their technology but don’t want to maintain their code/redevelop the product on our software.” Every piece of hardware they’ve done this on has seemed incredibly niche to me as well (i.e., not something you’re going to find in your local department store).

    The exception to that was their nest home security system, which IIRC they allowed users to pivot into an ADT system (and I vaguely recall offering some level of refunds).

    Their Stadia controllers they provided a free tool to convert into generic Bluetooth controllers after shutdown… Literally nothing to gain from that except perhaps some PR.

    There’s plenty of evidence to the contrary for Google bricking perfectly good devices “just because.”

    Wink threaten to brick your devices unless you suddenly start paying a monthly fee on top of your purchase price “for life”

    Yeah, this is the typical “startup made a bad business decision and is now trying to squeeze users.” I hate it as much as you do (but it’s not Google, Samsung, or generally speaking the mobile sector/big tech/mainstream tech).

    The following is pure speculation on my part: I think we’re at the beginning of a huge wave of planned obsolescence. Everyone and their mother are now training AI’s, and they want their customers to replace older products, which don’t support AI integration, with new ones. They’ll soon stop supporting the older devices or outright bricking them, to force people to buy the new ones.

    Big “press X to doubt” from me, primarily because of the desire to sell subscriptions. I think more likely Google (as an example) will keep everything they can working and then sell Gemini subscriptions on e.g., the nest hub + make new nest hubs with attractive features.

    Speculation on my part but I think Google invested in Fuschia (and ported tons of legacy devices in the Nest ecosystem) specifically because they wanted to reduce the security risk and maintenance burden of keeping old devices going (to maximize subscription revenue).


  • Yeah, all the Logitechs and Razors I’ve ever had are glued (or some other non-obvious method of entry). Gaming mice tend to be the worst about this.

    I have gone with Logitech over Razor as I have found them to last significantly longer. My last Logitech lasted ~5 years compared ~2.5 I was getting out of my razor mice.

    It’s incredibly common for Logitech and Razor to put a rechargeable battery in all their wireless mice instead of a user serviceable battery as well. This is in part because the general population seems to prefer this strategy (and it’s better than non-rechargable AA or AAA batteries … but that doesn’t mean it’s good).


  • If anything they’re supporting hardware with driver/OS updates less now than before.

    That is literally false information. Prior to the last year there has been no version of Android that has more than 4 years of operating system security updates, before that it was common to be 3 and before that 2. They bumped it to 7.

    I have a good working Android tablet that I’ve replaced the batteries on twice that I now can no longer use because the OS won’t get updated any more (security risk, etc.). Perfectly working, has to go in the trash.

    Literally what I just explained they’ve been working to change, and have changed for their latest devices.





  • Google is introducing planned obsolesence in Fitbit

    Have they? In what way?

    They’ve done good work for Android and Pixel, promising 7 years of updates for the latest Pixels. Samsung has also gotten much better about this with their recent phones. That’s going to put a huge dent in the e-waste as Android phones have surely been heavy contributors (certainly much higher than fitbit).

    TVs get bricked with firmware upgrades.

    What TVs? Vizio, Hisense, the Chinese junk budget brands?

    Very sympathetic to your e-waste concerns; I think the source of the problem is actually getting better not worse though. In general, the mobile tech sector is “growing up” and supporting products longer.


  • Not sure what you’re using to generate that list/formatting is a bit difficult.

    I don’t have a cluster since it’s effectively single user + @[email protected] (in theory a few other people have access, but they’re not active), single machine, it’s just more or less the out of the box docker stuff on a bare metal machine in my basement + a digital ocean droplet.

    The droplet is what I’m using to have a static IP to prevent dynamic DNS nonsense + it provides some level of protection against a naive DDoS attack on random fediverse servers (since I can in the worst case, get on my phone and severe the ZeroTier connection that’s using to connect the droplet to my basement server).

    I’m pretty confident whatever is going on is payload related at this point.

        PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
      50622 70        20   0  330264 240200 201512 S   0.0   0.7   0:25.21 postgres
      50636 70        20   0  327804 239520 201296 S   0.0   0.7   0:26.55 postgres
      50627 70        20   0  327204 239152 201592 S   0.0   0.7   0:24.75 postgres
      50454 70        20   0  328932 238720 200872 S   0.0   0.7   0:26.61 postgres
      50639 70        20   0  313528 217800 193792 S   0.0   0.7   0:03.13 postgres
      50641 70        20   0  313284 217336 194204 S   0.0   0.7   0:03.15 postgres
      50626 70        20   0  313592 216604 193636 S   0.0   0.7   0:05.07 postgres
      50632 70        20   0  313236 216460 193968 S   0.0   0.7   0:04.52 postgres
      50638 70        20   0  310368 216084 193856 S   0.0   0.7   0:04.20 postgres
      50614 70        20   0  310520 216072 193840 S   0.0   0.7   0:02.88 postgres
      50642 70        20   0  312200 215920 194068 S   0.0   0.7   0:04.46 postgres
      50640 70        20   0  312584 215724 193676 S   0.0   0.7   0:03.32 postgres
      50635 70        20   0  309744 215404 193764 S   0.0   0.7   0:02.72 postgres
      50630 70        20   0  312168 215224 193488 S   0.0   0.7   0:02.67 postgres
      50621 70        20   0  309560 215096 193772 S   0.0   0.7   0:02.97 postgres
      50646 70        20   0  309492 215008 193560 S   0.0   0.7   0:04.66 postgres
      50625 70        20   0  309760 215004 193368 S   0.0   0.7   0:03.08 postgres
      50637 70        20   0  309296 214992 193848 S   0.0   0.7   0:02.87 postgres
      50616 70        20   0  310596 214984 192700 S   0.0   0.7   0:04.17 postgres
      50643 70        20   0  310392 214940 194008 S   0.0   0.7   0:04.14 postgres
      50624 70        20   0  310128 214880 192928 S   0.0   0.7   0:04.15 postgres
      50631 70        20   0  310220 214596 192576 S   0.0   0.7   0:02.71 postgres
      50613 70        20   0  309364 213880 192520 S   0.0   0.7   0:04.06 postgres
      50628 70        20   0  309852 213236 191504 S   0.0   0.7   0:03.04 postgres
      50634 70        20   0  187772 163388 149428 S   0.0   0.5   0:02.87 postgres
      50644 70        20   0  189684 162892 148508 S   0.0   0.5   0:04.11 postgres
      50633 70        20   0  186096 162544 149324 S   0.0   0.5   0:03.20 postgres
      50629 70        20   0  185644 162112 149296 S   0.0   0.5   0:04.62 postgres
      50618 70        20   0  186264 160576 147928 S   0.0   0.5   0:04.10 postgres
      50582 70        20   0  185708 160236 147592 S   0.0   0.5   0:04.10 postgres
       3108 70        20   0  172072 144092 142256 S   0.0   0.4   0:04.46 postgres
       3109 70        20   0  172024 142404 140632 S   0.0   0.4   0:02.24 postgres
       2408 70        20   0  171856  23660  22020 S   0.0   0.1   0:00.76 postgres
       3113 70        20   0  173536   9472   7436 S   0.0   0.0   0:00.15 postgres
       3112 70        20   0  171936   8732   7020 S   0.0   0.0   0:01.54 postgres
       3114 70        20   0  173472   5624   3684 S   0.0   0.0   0:00.00 postgres
    

    I’ve got quite a bit of experience with postgres; I don’t see any indication it’s the problem.


  • So, I think this is a (helpful) general comment but wrong in this/my specific case.

    The server is so small it’s not really going to register on a 10-minute frequency for outgoing content – I’m not that much of a lemmy addict! haha.

    You can see in a comment here my most recent comment to lemmy.world did sync: https://lemmy.world/comment/8728858

    I’m not having any issues with outgoing content, beehaw, the KDE instance, and several others. It’s just lemmy.world that’s acting up (which is unfortunately because it’s my favorite – I mod/run several communities and donate to here/them – haha).