AmbitiousProcess (they/them)

  • 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2025

help-circle
  • Using password login renders this vulnerability useless.

    This isn’t the case, though I can see how the article could lead you to believe that.

    It’s directly based on password rather than key input. The entire vulnerability is that typing a password longer than 256 characters automatically defaults to crypt() outputting the * character instead of a normal password hash, which is coincidentally the same default character used as the “hash” (not actually a value you could get from a normal hash, intended to be impossible to get from any normal password for that reason) for the built-in daemon account.

    When the Ars Technica article says “Second, the target system account must be configured to be passwordless”, what they mean is the default daemon account, which has a hash set to * by default, and thus wouldn’t normally be accessible via any hashed password… unless you happen to find out that the system chooses to not make a hash, and just send * if you type more than 256 characters.

    Look at https://sshhole.com/ if you want the details.


  • As if the ONLY thing your memory could be used for is running AI models.

    Hey buddy, we need this shit to use our BROWSERS or to play GAMES. I have a GPU in my computer that can run most new AI models when quantized at a speed that would be perfectly reasonable for any home user that doesn’t want it to literally replace every ounce of their thinking, and I bought that shit before ChatGPT was even a thing, because I wanted to play fucking video games.

    I have a NAS with 16 gigs of RAM and a consumer-grade CPU that’s a few generations old, and it can still run models with zero GPU or AI accelerator if you give it a little time.

    Is it going to be perfectly tuned, and run at the highest possible speed if you design a datacenter just for AI models? Of course it is. But do most people on this planet need that or give a fuck about it? Absolutely not.




  • Maybe try Ente then?

    Haven’t used it before myself, but I’ve heard good things, and it does have a memories feature, and it seems at least based on the examples on their website that it might generate something more than just “today x years ago”.

    Unsure to what degree it works though, and unfortunately Ente is also a paid service (though it is privacy focused, and I believe it has a FOSS app too)

    Seems like “Smart Memories” are on the roadmap for Immich though, so you might just have to wait a bit and can then switch once they’re there:

    image

    There aren’t really any other mature options out there for self hosted, or even just private Google Photos alternatives in my experience, so you’re kinda just stuck with Immich for the most feature-complete replacement, and Ente for a more “just works” private but not self-hosted one. Everything else is basically just a glorified file browser, but maybe with some smart searching or better media codec support.





  • 100% Immich. Really good UI, and the kinds of quality of life features you don’t normally find in smaller open source apps (auto face tagging, map based on coordinates of photos, built-in non-destructive editor, memories, etc)

    The memories feature is mostly just “here’s photos/videos you took on this date”, but it doesn’t compile any sort of custom album based on a theme or place or anything like that. Not hard to do so yourself by just going to the map view and zooming into any location though.

    As for image searching it does have that, and I’ve found it to be shockingly reliable even when I run it on just a Raspberry Pi. (though it can take a while to give you the result of your search if you’re on lower-end hardware like that)


  • I would say if all you care about is having a nice looking, fully-featured, easy to use client, Proton is good, but if you really just need… an inbox with an email attached, then Tuta will be a little cheaper and just as private, just with less bells and whistles.

    If you care about removing yourself from other services like calendars, cloud storage, password managers, etc, Proton is way better since it has the full suite.

    For example, Proton supports auto-categorizing mail (e.g. newsletters, promotions, updates, transactions, etc), unlimited email aliases, a more modern UI, good integrations with Proton Drive and Proton Calendar if you decide to use those as well instead of Google Drive and Google Calendar, etc.

    Tuta is more just an inbox that you can bother to sort as needed, comes with some aliases if you feel like it but probably not enough for every single online service you have, has a basic calendar, but doesn’t have any kind of integrated Drive access (is still in closed beta rn), and has a more… basic UI.




  • Kinda depends.

    If your job is heavily based on results or hitting quotas, quitting might not be the best choice in most cases, since if you weren’t meeting the requirements set, you’d be fired anyways. (e.g. if their metric is "10 protesters jailed a week, you can’t really be “gumming up the works” by only jailing 10 protesters instead of the 20 your coworker is doing. If they needed 10 more from you, they’d up the requirements or hire/transfer another person)

    But if your job is more abstract, something specialized that’s hard to find replacements for, etc, then it can be worth it. (e.g. you’re the only person who knows how this legacy system with no documentation functions, if you quit and they need tech support, they’re fucked. Or another example, if your job relies on your team making new guidelines for how to best identify protesters, but you effectively sabotage every regular meeting with long speeches, bringing up old issues and re-opening them for discussion, asking how effective new decisions really are to draw them out, etc)

    In this case, federal prosecutors are:

    • Harder to replace (you need a lot of experience and education)
    • Damaging existing efforts when they leave (one of those resigning was working on major fraud cases someone else will now have to pick up)
    • Slow to get replacements working for (since old cases being handed off to new people need to be entirely re-examined and learned about all over again)

    So resigning was probably a good choice compared to just going “it’s taking a while, sorry” and then them looking at the work and seeing it’s just way slower than before on purpose in tangible ways, then having them come after you for “sabotage” or whatever they try to brand it as.