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/)V
Posts
8
Comments
193
Joined
1 yr. ago

  • Some will let you pay for up to 10 years at the 1 year price, so if you get a deal on a particular tld (as long as it's not an abused one like .xyz) you can pay upfront and save a decent amount of money.

    From memory you should try and avoid 10 year renewals since you can't transfer to a new registrar for the first year of the new renewal.

    You'll probably want WHOIS privacy support, so make sure the tld supports it.

  • I didn't follow a guide, but this guide is probably the closest to how I'd do things.

    I'd say if you don't care that much about the data then either snapraid or RAID-5 is okay; I use snapraid because even if the data is replaceable, I'd prefer to lose only 1 or 2 drives instead of all of them. You should of course have proper 3-2-1 backups for essential/irreplaceable data in any case.

  • Because modern arrays are often in the multi-TB size recovery can take a significant amount of time (days and weeks potentially) and since RAID-5 only allows one drive to fail, if a second drive fails during that time you're cooked.

    I like to use snapraid combined with mergerfs which technically has the same problem, but because it works on the file level, if a second drive became corrupted, you'd only lose the data on the drive that failed, not the entire array. I combine it with snapraid-btrfs which operates on read-only snapshots instead of raw data, avoiding write hole issues (data changing during sync) and also btrfs itself on each drive gives an additional layer of integrity checking, and rollback support from the snapshots themselves.

  • Paperless may work for this, although it's more focused on document scanning.

    Vaultwarden is probably a better fit for password management, combined with Bitwarden app and browser extensions.

  • Beets for cleaning up the tags and self-hosted navidrome appears to support multiple artist tags. The web interface of navidrome definitely supports filtering by both albumartist and artist (the latter will include albums and tracks with multiple artists). I assume this is what you are trying to achieve by using a visual artist tag? If you just want to rename an artist but keep the underlying artist tag, that can probably also be achieved with beets.

    This link shows the details of how navidrome handles tagging: https://www.navidrome.org/docs/usage/library/tagging/ The issue if you don't want to use the navidrome web interface is that not all clients support browsing by artist I suspect (and often use albumartist, which I personally prefer). I use supersonic which I doesn't appear to support it, but there's also Feishin and a bunch of mobile clients you could use (or open a feature request on supersonic github).

    Replaygain will be supported by most clients (not sure about the navidrome web interface).

  • Garmin smartwatch but used offline only and connected with the FOSS gadgetbridge software. I've also started doing some manual tracking in a diary just to get my thoughts down with it.

  • I'll throw in Australia's ATAGI. There's also an Australian CDC but it was only just legislated last year.

  • I would expect that the security issues are with the stock OS, but can't argue with the gl.inet recommendation.

  • Also unrelated, but if you’re running a x86 system with gigabytes of RAM, why not run Opnsense at that point?

    I believe it's gotten better but historically *BSD had poor SQM support (bufferbloat mitigation), which is particularly useful on slower, asymmetric connections and where low, consistent latency is paramount.

    It was also a bit of a laggard on Wireguard support, although that's long since been fixed. So mainly you might prefer OpenWRT if you want the Linux kernel which tends to get features more quickly. Also because it's so low on resource usage (including disk space), you can put it in a VM and very rapidly recover in the case of issues.

    You could of course also use a full Linux based router OS, but I don't believe there are many with a web interface, which most users would prefer.

  • Another approach would be setting up your own recursive revolver with e.g. Unbound. It's debatable whether it's more or less private than using DoH etc but it would bypass the DNS tampering by your ISP at the least.

  • I still complain about the lack of the headphone jack (and SD slot). It's just become almost impossible to buy one that supports it without it being lacking in some other way. But I held out for ten years at least.

    I get you're making a broader point about how most people act and I agree.

  • You could also get a wildcard cert using dns challenge, and not even expose the subdomains publically.

  • It does require some Google service related functionality though I believe so may not work without gapps (may work with microg and graphenos has its own handling as you said).

  • I have a few very minor commits to some fairly major Linux projects.

  • It would take more than financial incentives I suspect. It's the time cost that is so demanding and it would likely require a restructuring of society that either results in people working much less hours, or a more community-based child rearing approach.

  • Try zram or zswap since you're on Linux.

  • Or use zram/zswap on Linux with ZSTD compression, which dedicates part of physical RAM to compressed swap.

  • I think the Libreoffice UI isn't great, but neither are its competitors. Probably partly the nature of conventional word processors that try to do everything through a GUI.