So I’ve been watching the news regarding some of the Bike lane drama in the US, but as an active bike user I have also noticed something weird happening around the city (Hamilton)

A number of the bike racks appear to have been removed from outside some of the larger stores

Now this may seem something small, but there is apparently some part of the planning form overseas to be pushing for vehicles that are able to be tracked via GPS etc

And it has me wondering if it may be part of making something harder to use by making these areas unfriendly for use to push for things that people pair their phones with that are harder to steal because they are digitally lockable, and are also track-able because of the pairing, like e-scooters and e-bikes

What’s the term? **Planned obsolescence **of items that don’t require a digital connection

Has anyone else noticed this happening in their area?

  • Venator@lemmy.nz
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    8 days ago

    Graphene os seem to be shooting themselves in the foot with a bit of a toxic max security type attitude ☹️

    When asked if this new communicator device would ever support GrapheneOS, the team was blunt: it is “never going to be supported.” Clicks-Communicator-GrapheneOS-support

    The rejection comes down to two specific deal-breakers that GrapheneOS cites as incompatible with their mission:

    Software commitment: The Communicator runs Android 16 with a promise of 2 years of Android updates and 5 years of security updates. GrapheneOS views this as insufficient for a secure, long-term device. The chipset: The device utilizes a 4nm, 5G IoT SoC platform from MediaTek. Historically, GrapheneOS has avoided MediaTek chips due to a lack of proper support for custom-verified boot and other hardware security features found in Tensor or Snapdragon chips.

    https://piunikaweb.com/2026/01/05/grapheneos-delays-non-pixel-flagship-to-2027-rules-out-clicks-communicator-support/

    LineageOS seems like it might be a good alternative for non-pixel devices, but it also has very limited device support ☹️

    • Dave@lemmy.nzM
      link
      fedilink
      arrow-up
      2
      ·
      8 days ago

      I kinda understand that it’s what GrapheneOS are going for. They are specifically trying to be a very secure OS. When Cellebrite has their device list leaked and it shows they are unable to break into the Pixel phones before they have been unlocked after reboot, this is the kind of phone they want to use. Supporting more devices would hurt this aim, but we also can’t forget that there are a huge range of devices and they don’t have the time to support them all. I support them in their choice to keep a narrow focus, and then I buy pixel devices second hand so I can use it.

      But of course the conversation started around how existing phones are going to get locked down by Google, so there isn’t really an easy option unless you have a phone supported by one of the de-googled Android forks like LineageOS, /e/, etc.

      Ultimately all Android forks will have limited device support because they don’t have the manufacturer creating the drivers and things needed to make it work, and everyone has limited time.

          • Joe :tinoflag:@mastodon.nz
            link
            fedilink
            arrow-up
            2
            ·
            8 days ago

            @Venator , might just be how you use it.
            I find Mac and Windows OS a terrible user experience, even most Linux Desk tops so I run a window manager in Linux and keep the skeleton OS to a minimum for what I use it for.
            I’m aware of the limitations and might have to settle with a Pixel and Graphene (mainly for the Pixel’s camera) until hopefully there will be more open phones and FOSS developers come up with a more ideal OS.

          • Dave@lemmy.nzM
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            8 days ago

            Honestly, if I could have that experience she had I’d be pretty happy with it as a second phone. Ultimately I haven’t been able to source a supported phone and the three spares I have are not supported by any linux phone I’ve had (and they aren’t that unusual. One is a Pixel 7 pro, ones a Samsung S10+, and one is some sort of OnePlus, a 4 maybe?) They are all flagship phones but I haven’t found any linux phone OS that is supported.

            I’ll have to investigate @Antigrav@mastodon.nz’s suggestion of a full Linux OS, though that’s not going to be the same experience it might be fun to play with.