• 0 Posts
  • 11 Comments
Joined 18 days ago
cake
Cake day: August 31st, 2025

help-circle



  • he will become hostile and defend his position until you either leave or he bans you from any community he has control over. I’ve been down that road a couple times.

    Just proceed with caution.

    So you hold a grudge because they banned you for something, and now you’re passive-aggressively spreading FUD, even as you recognize its superior security. What do you even mean by proceeding with caution? Be careful you don’t get banned from a chat server, or something more vague and nefarious? This kind of petty mud slinging is the bane of open source software’s existence everywhere.

    Best secure Android experience. Certainly not the best from a usability standpoint, but I digress

    Unrelated to the above, but what do you mean by this? Graphene is by far the most usable custom ROM I have ever used. Everything just works out of the box, including Google Play and banking apps (at least the ones I use) without compromising on privacy or security. The only times I’ve encountered a broken app, I could always fix them by disabling the hardened allocator for that app in the app info dialog, which does technically compromise security a little, but is a low risk trade off in most cases.





  • Nah, nobody gave a shit about privacy back then, just like they don’t give a shit about it today. The problem was just that most people “understood” what spy glasses were because they’d seen them in movies, and the media just stoked the flames of controversy because it led to easy clicks.

    Walking into a public bathroom with glasses like that on your face seems creepier than walking in with a phone in your hand, even though it’s much easier to discretely record with the phone (and in much higher quality).

    Although Meta’s case is different. If I see someone with those glasses on, I may give the individual the benefit of the doubt and trust that they’re not recording me, but I sure as shit am not giving Meta the benefit of the doubt and trusting that they’re not going to record without the user’s knowledge/consent. They wouldn’t let a chance to capture free data pass them by.




  • This non-sarcastically. The operating system is better at cleaning up memory than you, and it’s completely pointless to free all your allocations if you’re about to exit the program. For certain workloads, it can lead to cleaner, less buggy code to not free anything.

    It’s important to know the difference between a “memory leak” and unfreed memory. A leak refers to memory that cannot be freed because you lost track of the address to it. Leaks are only really a problem if the amount of leaked memory is unbounded or huge. Every scenario is different.

    Of course, that’s not an excuse to be sloppy with memory management. You should only ever fail to free memory intentionally.