• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle
  • Even if a social network loses 99,99% of the user base due to charging to use it, those left are the ones that see no problem paying to use it, so they are more likely to eat up some insane pricing, which would help recoup losses from a smaller user base. Basically whales.

    I think the only way to try to kill a social network is by going full scorched earth on it. Remove all your comments, or change them to be an annoying copy pasted comment about why you’re getting off the platform. And even then I don’t think it is helpful, I did that with Reddit but was forced to leave technical posts intact because I feared I might prevent someone from solving their issue.


  • Space usage under flatpak is highly overstated. It only takes a noticeable amount of storage if you only use a couple of flatpaks, cause all the dependencies are used for a single package, once you start using flatpaks as the main mean of installing “applications”, the space required start to decrease because the dependencies are shared between multiple apps







  • Alright, this is slightly related to the topic at hand:

    I think the charging up to 80% is kinda bullshit. I’ve been using my Redmi Note 10 for 2 years, and during that time I’ve used the 33W charger and almost always waited until the device was under 10% and charged it to 100%.

    I’ve used AccuBattery and it guessed the battery health was at 85%. This is still more battery left than what I would have if I kept the device between 20~80% charge. So I don’t get it


  • I just flash LineageOS even when the device is currently supported by the OEM. I buy the hardware from them, not the software.

    Edit: Like, the vast majority of actual custom ROMs users are either using Pixel Experience or LineageOS, there are a bunch of other ROMs, but those are mostly “purpose built” for enthusiasts of what they offer. Like, GrapheneOS is for security reasons, and things like that.

    There is a bit of headache installing custom ROMs, but once you install it, it is usually pretty stable. Also, I don’t get the locked vs unlocked bootloader thing in regards to security. The device is stolen and outside your hands, it is doubtful that a thief would go through the steps of flashing a ROM, but wouldn’t be smart enough on how to make the device unusable if it had a bootloader locked. Either way you are screwed.









  • it interferes with the ability to open drawers

    It’s funny, but I tried looking around the old Material Design guidelines and I haven’t come across any mention of swiping to open a drawer. I know it was on Android Developers, but it appears that from the point of view of the design team, it wasn’t really “officially” recommended?

    Regardless, Discord, IMO, offers a better implementation for side sheets, as the metaphor isn’t that you drag something from beyond the screen into view, you just drag the view itself to the side and that reveals the side sheet. And it works in the middle of the screen so it doesn’t interfere with the system gestures


  • As far as I know, Flatpaks have the best foundation currently, there are a number of issues, but they are fixable and not entirely by design. And with Fedora Silverblue/Kinoite and OpenSUSE MicroOS you can really see how native debs/rpms/whatever isn’t really that good of an idea for the average user and Flatpak is a solution to that.

    Appimages at a glance seems like a perfect solution for apps that for some reason or another needs to be kept outdated. But there is (was?) an issue of it not really bundling everything it needs, it looks and behaves as it is portable, but as far as I’m aware, it really isn’t.

    And then there’s Snap. Yeah, that one is just weird, it honestly just doesn’t feel like a proper solution to any of the problems it tries to fix.