Lemmy feature request: Show my negative “karma” in my profile page. You can make it opt-in if you must.

  • 0 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2025

help-circle
  • I’m not even saying ditch the phone just minimize usage of it

    This is the correct take.

    I never used the Graphene meme and the shit American Baidu hardware it runs on (security and phone were always an oxymoron regardless). But I was on custom ROMs from around CyanogenMod 3 until Lineage 21. I also owned phones with the highest-end Snapdragon SoC’s.

    Over the years, I went from everything unlocked in the open, to “hiding root” to disabling root (I realized I didn’t even need it anymore). And now I deliberately downgraded to a lower-end phone running stock ROM. And even with that, there is an APP from a utility company that refuses to run because the phone has an unlocked bootloader, which was needed to properly recover the phone. So my next phone will be completely stock. Never again.


    Most people here tend to be on the younger side. So while their hearts are in the right place, and tend to agree with a lot of genuinely good stuff. They are also very susceptible to falling for memes and becoming a part of circle jerks (they are still r*dditors at heart after all). They also just lack maturity and experience to be able to value situations with less emotion and wishful thinking, and more nuance.

    And I didn’t even mention the fact that 📲 is actually their primary online device 🥲.


  • I2P is a fully connected network where everyone is a relay, a UDP transport exists iirc, and there are many other significant technical differences.

    And if you’re dreaming of significant masses moving to the shadows, you might as well dream of them using distributed solutions. Otherwise, the monsters will simply find and shutdown the hosts/servers of whatever the good kids are consuming.

    There is a connection between August and freedom. Do you know what is it?


  • Enthusiasts will care because it could save them storage space for equivalent quality

    That’s the thing, even if you ignore that such scenarios involve lossy-to-lossy re-encodes (bad), and even when you ignore the general lack of psychovisual tuning in new encoders, the advertised so called objective “20%-30% improvement” is not universal, and only applies to bit-starved resolution-maxed encodes.

    Your file is 1080p or 720p? you won’t get that improvement, even in not-fit-for-purpose “objective” measures.

    You want to encode at a higher bitrate than YouTube to actually get good quality? you won’t get that improvement either.

    So if you embark on such a futile journey, you could be wasting a lot of computing power for no, or even negative, gain.


  • now

    Full-length encodes will take days to finish, and we are not talking single digits.

    An almost, but not really, practical encoder will probably take at least a year of development before it’s ready.

    And anyway, do end-users still care about codecs (beyond decoding complexity/hardware support)?



  • What’s wrong with it

    • It’s a random crate no one uses.
    • You’re not even really “using” it. You are just importing a re-export of reqwest, which is what I expected you to immediately notice after I brought it into attention. You can obviously just remove it and use reqwest directly.
    • Still, trusting a re-export is not a trivial matter. The random author of the no-name crate could replace the original reqwest with something malicious, or bad in some other way, in a v0.1.1 release. That (theoretical) release will be picked up after a cargo update call, or when Cargo.lock is not checked, which is the case by default with libraries.