• 81 Posts
  • 1.87K Comments
Joined il y a 3 ans
cake
Cake day: 13 juin 2023

help-circle











  • I buy used/refurbished phones a generation or so out-of-date, and recently upgraded from a Pixel 7 to a Pixel 8. Amazon sells “unlocked” phones, but does not distinguish between carrier-unlocked and OEM (bootloader)-unlocked. Whatever phone you get, you’ll want to immediately do the “enabling OEM unlocking” step (enable Developer Options and make sure that “OEM unlocking” exists as an option and isn’t grayed out) before the return period expires.

    It took me two tries to get an actually-unlockable phone this time around, and I’ve still got the unsuitable one sitting here on my desk waiting to get packed and shipped back to Amazon.

    Also, I’ve been actually screwed by it a year or so ago, when I got a Pixel 7 for my dad, with the idea of preserving the option to install something like GrapheneOS or LineageOS at a later date. When that later date came (after the return window had closed), we discovered that his “unlocked” phone wasn’t actually OEM-unlockable and now he’s stuck on the stock ROM.






  • One of @FauxLiving@lemmy.world’s comments linked to a bug report about it. Turns out the real reason is that Krita uses a plugin architecture that allows additional file types to be supported, so it can’t actually know the complete list of MIME types to put in the .desktop file at application install time.

    Krita makes it possible for plugins to extend Krita with additional file format support. Those plugins come with a desktop file that tell the desktop that krita can load those file types. Of course Krita’s main desktop file cannot have the full list of supported file types, because that’s implemented by plugins. Most of those plugins are shipped with Krita, but that is not necessary. People can create extra import/export plugins that still need desktop files so your desktop can know that Krita can load this file format.

    I’m not completely convinced that’s a good reason (compared to, say, having each plugin installation modify a single krita.desktop file or something), but I think it manages to upgrade it from “indefensible.”