Do not conflate the Zuck or other Silicon Valley suits with hackers. They lack both the technical skill and the ethics.

Early voters are reporting some hijinks when selecting their choice so be VERY CAREFUL about confirming who you are voting for.

Like so?

Weidel is just cosplaying nationalism. As with many other European far right movements, the AfD is supported by Russian money and Russian information warfare operations. Russia wants to see the EU weakened, if not broken apart. And so their sockpuppets act upon their orders from Moscow.

But there’s people out there! (shudders)

I’m not an LLM and I don’t use any for writing my postings, if that’s what you’re getting at. ;)

A Booklore fork! Yes, that does make sense, since Grimmory’s commits oddly start with v 2.x.x

It does not, however, change my outlook much. Booklore, too, was a very young project (initial commit: March 2025) and heavily vibecoded by a handful of people.

Grimmory sounds like a new kid on the block, and indeed, it is. I’ve looked into it, and here’s what I’ve come up with:

• initial commit: March 2026 --> very young project, blazed through 24 releases already
• 165 contributors, but upon closer inspection, it relies on only two frequent contributors --> if they lose interest, the project might fall dormant or die entirely
• as per its AI policy, the project embraces AI as a tool, but expects contributors to understand what they’re committing, and reserves the right to throw out blatantly vibecoded contributions. --> Whether two people can actually enforce this policy when getting firehosed with AI contributions remains to be seen.

With all that in mind, I think I’ll give this project a pass for now. Like you said, it’s some work that goes into curating a library and making sure the metadata is correct, and if that locks me into a project that may or may not exist several months or years from now, I’ll probably stick to one of the more established projects with a higher likelihood of long-term maintenance.

Feel free to elaborate. ;) I don’t mind ditching folders. The question is: how do I get at said metadata with the least amount of manual effort, how do I make sure that it’s accurate (sifting through thousands of files is not fun), and how is the metadata stored - particularly so that does not lock me into one application that can only understand its own metadata scheme, and once it dies or I want to switch to a different one, I lose all the work I’ve put into curating my collection. That’s why I was considering folders as an option: they are a software-agnostic way of organising my library.

Hi there,

thanks for not staying true to your username. ;)

[let the LLM] apply metadata to the file

How does this work in practice? I’ve got a bunch of .pdf, .epub, .txt, even some .doc files lying around in a folder. What would an LLM do to them? Write a bunch of .xml files with the same file name of the corresponding book, or what?

That’s fair.

Now let’s see which of these waste materials I can recycle, and which of them I could, theoretically, leave untouched in their current state for 250-500 years without investing a single Dollar. (The illegal Sweetwater dump was cleaned up, btw. Picture 1 is supposed to be the clean-up.)

it can be stored on site for half a century without issue.

Oh yeah. These issues are so mild that after your “half a century”, we need to dig everything back up, reseal it and find a new place. Playing a thousand years’ worth of musical chairs with radioactive waste may sound fun to you - until one day, the music stops and you can’t find a chair.

To answer your question, could you first

a) calculate the total energy generated by the waste materials in pictures 1 and 2, just so we can be sure this is an apples-to-apples comparison and we can be sure that we’re looking at roughly the same amount in both pictures and
b) fast-forward these images about 250-500 years and then reasses which one depicts the greater environmental problem and cost factor?

Praising nuclear and deploring the cost of wind? That’s funny, considering the still-unsolved problem of securely storing nuclear waste for thousands of years. It’s almost like we have left the factor with the largest potential cost out of our calculation…

I’ve got your exact setup:

• running immich (and other services with valuable data) at home (on OMV!)
• backup server at family member’s house
• regular backups from here to there through Wireguard tunnel with Borgbakup

AMA!

I don’t want a compromised device on the family member’s network to compromise mine

If with “mine” you mean the pi Zero, I wouldn’t worry too much about that. Just configure the pi’s firewall to drop all traffic from the LAN (they have no business with this device anyway), except any incoming traffic from the router on the Wireguard port.

Immich is entirely free and open-source software and got a grant from the FUTO Foundation, which is fiercely pro privacy. As such, it does not engage in any data sharing. Development is financed through the grant and purchases of the server licence (I got one; it’s ridiculously good software).

Ah! I use virt-manager + qemu on desktop Linux, mainly to try things and and contain dodgy software (Windows). I didn’t know it was commonly used on headless servers. Thanks for pointing that out!

I’m self-hosting psiTTSa, an offline text-to-speech engine.

(Prob not the answer you were looking for, but a reminder that “AI” is more than just LLMs.)

and one day apps that destroy these things!

Call me old-school, but I prefer doing this manually. Literally.

equilibrium with Christian Bale which is basically just fahrenheit 451

That’s an odd way of spelling “poorly-crafted ripoff with pointless gun-fu action scenes crammed into it”, but OK.

Thanks for your detailed reply and expertise! I really appreciate it!

First question you have to ask yourself is so what?

You’re right to call out my lack of threat modeling. I am aware that the “cost” of what I’m planning here likely outweighs the actual risks. That’s a deliberate choice though: one of my objectives in homelabbing is to “learn how the big guys do it”, i.e. learning and implementing, bit by bit, networking and security best practices.

That said,

• all of my drives are (LUKS) encrypted (although this will only help against evil maid attacks physically stealing my disks, since data is only encrypted at rest, not while the server is in operation)
• I do have some CPU monitoring in place
• I have applied the principle of least privilege (as far as I can see at least)
• I have set up an off-site backup server running (although I need to improve automation and deduplication; I’ll probably go with Borg here)

Thank you also for pointing me towards OWASP Docker cheat sheet! I didn’t know this resource yet, although I seem to have found others that said the same thing. I already have in place:

• no docker socket exposed to services
• user set for every service that didn’t give me a headache doing that (some assume root and won’t accept setting a user)
• username remapping is active
• all containers have their caps dropped and selectively only put those back in which they need
• I expose almost no container ports, and only those necessary; instead, communication with the containers is handled on my reverse proxy’s network (i.e. via the internal docker network)
• privilege escalation is disabled

I have played around with rootless docker (again, stubborn containers assuming root prevented me from going all-in) and considered Podman, although just putting containers in a VM looks like a more frictionless route to me.

All things considered, your advice seems to be:

1. to first consider whether I actually need all this security. I really don’t, yet I want to learn how to set it up anyway.
2. to first explore and all other hardening avenues. I have, to a certain degree, and beyond that run into brick walls.

If I might exhaust a little more of your time, I’d be curious how you judge the next step I’ve suggested: splitting duties between separate servers, thus segmenting public from private physically, or going the virtual route (again, by splitting into a public and a private VM and separate them through strict software firewalling).