• 7 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle




  • Zardoz@lemmy.worldtoAndroid@lemmy.worldFairphone 5 Launch
    link
    fedilink
    English
    arrow-up
    74
    arrow-down
    1
    ·
    edit-2
    10 months ago

    Can’t speak for everyone but here are the reasons I prefer an actual jack:

    • 3.5mm headphones are extremely universal and can be used for any audio device. USB-C and Bluetooth headphones cannot

    • Bluetooth is extremely inconsistent when paired with multiple devices and often gets disconnected because of competing devices

    • I can’t charge my phone and listen to USB c headphones at the same time

    • Manufacturers claim the removal of the jack was to improve the water resistance. I have never dropped my phone in water and would be willing to risk it.

    • I already have too many wireless things to charge

    • I have a small stockpile of broken wireless headphones. Meanwhile my 10 year old wired headphones are collecting dust

    • I have never lost something more often than that tiny ass USB to 3.5mm dongle adapter

    • I distrust large corporations with incentive to get consumers to buy more stuff from them











  • Not a proxmox pro by any means, but it can do both VMs and containers. I have a few VMs for various Linux distros to play around with. I also have one dedicated VM for all my security related tools.

    Stuff like PI hole, jellyfin, logstash, etc. dont really have any need for a full OS, so a container works perfectly. Plus having a full OS with several things running on it makes it more difficult if you just need to restart one service

    I started doing everything in VMs but over time realized some things were better to maintain as containers




  • Reverse engineering is more about understanding how a piece of software does something so you can better work with it, or make your own version of it. Typically requires a lot of time studying it, and usually goes hand in hand with decompiling. But decompiled source isnt the cleanest and doesn’t give you the exact same code the devs have. It only gives you the low level order of operations.

    Most of the time, knowing why requires understanding all the code from an architecture perspective, which typically requires being part of the internal decision making. You won’t get that unless you have the actual source code with good comments and documentation. All of which would be stripped out during compilation.

    Whenever I reverse engineer something at work is because it is usually a super old 3rd party software that’s out of support, and I need to see how it’s performing some task. I’m never able to get the context of why they do it a certain way but I do get the how of it