Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)SA
SayCyberOnceMore @ Cyber @feddit.uk
Posts
18
Comments
567
Joined
2 yr. ago

  • Anything that's not an HP...

    I don't know what it is with them, but I always have problems with their hardware - generally. Printers, laptops, anything...

    But I definitely +1 all the Dell comments

  • Ah, ok, so I can export my OsmAnd paths, import into this and then remind myself of where I went on holiday / almost fell of a cliff / got lost driving / etc ?

    I have a bunch of tracks I've saved over the years... hmm... maybe this is what I should be using

  • Ahh. Thanks... I renamed the .config/vivaldi folder and launched it, barely a blip on the CPU...

    I've re-added .config/vivaldi/Default/Calendar from the backup (as that's what I wanted to use anyway) and it looks like everything's working with minimal CPU.

    So, I guess some old settings needed clearing out from somewhere.

    Thanks for the pointer

  • It's similar failure to what Flathub does on their site too

    My understanding is that Mint is just following Flathub's classification, so it would be identical...?

    And (would need to verify when this version is released) some of those apps are available without Flatpacks anyway... (ie VLC for example), so I'd expect those to still be available

    I don't see this as a big issue...

  • +1 for Logseq... I'm using it for work as well as personal stuff and it's strength is automatically creating new pages (and reverse links back) by just typing '' [[that new idea]] '' and you're done. Fantastic.

    And sync with syncthing

  • It's not like the AUR packages need recompiling after every update, so I'm using standard Arch repos + AUR and that's it.

    Everything will be using the same (bleeding edge) dependencies, so if something breaks, I can find what changed and fix it and / or roll-back and / or report it to the dev.

    I've been down this whole scenario with Windows back in the day... DLL hell, InstallShield packaging, compiled zips, weird %PATH% sets for execution, the lot... and at the end, it's always simpler to use common libraries and work with the devs to fix bugs - after all, they're usually developing on a "normally" packaged system anyway.

  • Came here to say this too... I contribute a few €/£/$ per month to various projects...

    I won't get all righteous here, but just because you don't have to pay, doesn't mean you to say you can't support the developer(s)...