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/)LE
Posts
15
Comments
2,750
Joined
2 yr. ago

  • Should I not be able to use the software if I'm donating?

    I see these comments going "oh it's still alpha, we need to encourage them". Well it should have exited alpha a long time ago, and secondly I'm not going to pay for the mere possibility of it being useful at some undetermined point in the future. Show my something useful now.

    If anything, Immich has demonstrated it has no intention of ever becoming a useful project. A perpetual alpha that breaks super often and plans to remain in that state on purpose indefinitely should not be asking for any support.

    Even in FOSS you have to show some modicum of practical sense. FOSS was founded on "scratch an itch" not on "break forever".

  • Wow, basically everything you wrote about Manjaro was wrong:

    • It doesn't need constant maintenance, and it doesn't break. The whole point of it is to be a stable variation of Arch.
    • It doesn't have a highly irregular update schedule, it's quite regular — every two weeks. There are also updates for outstanding security issues which can come faster (as needed). Occasionally very large updates can take longer in order to weed out all the issues, such as the recent example with Plasma 6 — those are announced in advance.
    • AUR doesn't "expect" anything, it's a dumping ground where anybody can put anything. I successfully run about 100 AUR packages on Manjaro without any issues, but nobody can guarantee anything when it comes to AUR. It's officially unsupported on Arch and every Arch-based distro. If you want to call it dangerous that's fine (if a bit hyperbolic) but don't blame that on Manjaro, it just shows that you don't understand how AUR works.
  • That's barely enough time to talk about best editor. Then there's best DE, best distro, best shell, Wayland vs X, systemd, whether sudo needs to be replaced, Nvidia vs AMD etc.

  • I get that they're trying to figure out how to monetize it while staying kosher FOSS, and their first wording suggests they'd like to offer per-seat licensing.

    What I don't get is what would compel me to get a license. I still can't rely on it for anything serious. I'm basically using it as an UI for the face recognition models and that's shoddy too. They've made it impossible to lean on it for anything else.

    I don't want to sound like a hater because they're obviously working hard on it but, God, you can tell they're not professional developers and it's so frustrating. Focus on doing something well, and stop breaking compatibility every other week.

  • Even for unit tests it needs to be taken with a grain of salt because they should describe what should be there and at best Copilot can describe what is there.

    The overlap may or may not be there but either way it's a dicey proposition to allow Copilot to second guess the intent behind the code and make that guess the reference.

  • Separate root fs makes it easier for timeshift. Snapshots are a different beast from backups.

    Also makes it easy to install another distro and pick up where you left off with the old home.

    If you alocate 50-60 GB for system it should be ok. Things like Flatpak or Steam can put their files in home.

  • Depends on what you mean by "programming".

    If you mean it like the neighboring comment, who is probably a mathematician or physicist who just needs to feed it a science paper and run some models to verify the premise, but doesn't care about the code itself, it's a good tool. They aren't programmers and learning programming or using a programmer would only delay them.

    If you're a professional programmer however your whole point is to create the most efficient specifications for the computer to do things. You cannot convey 100% of the spec to something like GPT so inevitably some is lost, so the end result is not the most efficient (or doesn't even cover everything you needed).

    You can of course use it to get a head start but there are also boilerplate and templating tools and frameworks that cover the same purpose.

    Unlike the physicist, the code you make is the whole point, and it's based in your knowledge of the subject matter, and you can't replace it with GPT. Also, using GPT in this manner stunts your professional growth and damages you long term.

    It would be somewhat worth it if at least it accelerated some part of your work, and it can find its way into the tooling, but straight out replacing your brain with it ain't it.

    For writing actual code and designing software it's more trouble than it's worth, it produces half-assed code that needs fixing.

    TLDR figure out ASAP if you really mean to be a programmer or some other type of specialist that only deals with programming incidentally.

  • I guess? I'm surprised that the original model was on equal footing to the user prompts to begin with. Why was the removal of the origina training a feature in the first place? It doesn't make much sense to me to use a specialized model just to discard it.

    It sounds like a very dumb oversight in GPT and it was probably long overdue for fixing.

  • Search for "chris titus windows tool". It's a debloat tool that removes such annoyances. It also includes a button that runs the Shutup tool, that disables another bunch.

    I'm a Linux user but I use these tools (and massgravel) on Windows VMs to make them behave.

  • Not OP but:

    Separate the system and home partition, first of all. The strategies are usually different.

    Many distros integrate Timeshift out of the box to create system partition snapshots before every update, and to be able to restore them from the boot menu. Using BTRFS for the system partition makes this even better.

    This is usually all that people need in regards to the system, but you can also take regular backups (see below) of things like /etc, the list of installed packages and things like that.

    For personal files I prefer Borg Backup because it is incremental, does compression, deduplication, encryption, checksums & recovery.

    Borg works with repositories, which can be on local disk, on a removable disk, or remote. If remote, they are tunneled over SSH. It can also export/import tarballs for more exotic scenarios like moving snapshots between different repositories or backing up data to optical discs.

    You can use Borg from the CLI and there are also UI apps that make it easier. Pika Backup is a simpler one, Vorta is a more advanced one. I've set up family members with Pika and after preparing it for them all they have to do is plug in the backup HDD, open Pika, and hit the big "backup now" button.

    There are also online services that support Borg repositories specifically, and for anything that doesn't you can export tarballs and back them up as regular files, completely transparently from the service.

    rclone is a cli tool that supports a large number of online storage services. You can use it with borg snapshots or you can use it to back up your files directly — it resembles rsync somewhat and can also do encryption iirc.