moved from us instance

  • 1 Post
  • 130 Comments
Joined 5 months ago
cake
Cake day: June 3rd, 2026

help-circle
  • I’ve talked about this before, but the draft says that a “registered number with the IANA” would be recorded. So the ASN, likely to the hosting provider? Or the IP, with a birthday problem so it’s unlikely to be implemented de facto? Why the fuck does a video player need a registered organization and an ASN? It’s capped to income, there’s little to none.

    Facebook and Insta and other social networks are not targeted because they are free

    The video player is also free of charge? And Facebook also has income? Hello?

    IDK, I use MPV so y’all will have to correct me if I’m wrong. I don’t think software should be wrapped around petite bourgies anyway.








  • Someone I know has one of these.

    KD1:/ $ pm list packages | grep cpe
    package:x.cpe
    KD1:/ $ settings get global package_verifier_user_consent
    1
    

    Hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm, so Play Protect is enabled and doing nothing about it. Also, “nexus” wasn’t installed, not here at least. Not “system.ntp”, “oemservice” or “sso” either. com.droidlogic.* is just generic AmLogic crap, if there’s a backdoor in there it’s probably a different company. The Google article mentions libexploit.so, which doesn’t exist with a quick find. Neither does libjaguar.so. libbase.so is just a generic file present everywhere, nothing interesting in strings for it. My guess is that it’s geographically locked.

    So I am not sure what I am supposed to do with that. I just ran pm disable-user on it, hopefully that’s enough.












  • I agree with most of what you are saying and am also looking for an excuse to switch to a BSD. BUT:


    Re: Wayland

    It doesn’t sound “hard to refuse” at all, unless you are also sticking with the big two DEs and no forks. For context I have done both X11 and Wayland installations based purely on whichever runs better on any given machine with some tweaking. Wayland runs amazing on new 3D-only GPUs, which is what it was designed around. Although I don’t have any bar at all, I just use sway with the bar removed because that’s what I’m used to. And because all bars I could find either aren’t maintained anymore, suck at efficiency or suck at running without a bunch of config file editing. Which is kind of a fault of the time frame when Wayland was popularized and the leadership for adjacent standards rather than the original protocol design. And it’s also not a fault of the base protocol that virtually all implementations ended up using lots of “Linuxisms” like libinput which require all sorts of weird hacks to run on other systems. Maybe in the near future this will be better considering the whole Linux “left opposition” situation replaying in the age of LLMs.

    Re: Linux phones

    They suck because it’s an extremely niche category of people who can port, consider Android too bad and yet don’t consider most of the devices themselves bad. They are amazing from recycling and pocket computing standpoints, but there are even less people thinking this rationally about it, unfortunately.

    Also, “available in OS but not Flathub” that’s a good thing, no? You are also in an extremely niche category of people who are anti-systemd, anti-Wayland yet pro-Flatpak.

    Re: RedoxOS

    Was it the Rust one? If so, “not written by an RNG machine” makes little sense given that Rust tooling itself is tainted.