Didn’t the refactored netscape eventually evolve into Firefox though? Not disputing the poster child status or the fact that it’s a terrible business decision, but the project did not really go stale I think?

What’s IVF in this context?

Never knew it, very neat!

How do I use this feature? I’m a Firefox user since quantum and had no idea this was a thing.

Just write some content without no soul and not a shred of humanity present. I.e. use the platform as intended.

They already have something kinda like this. All public wifis require that you sign in with phone number and SMS-verification. It might not be as air-tight as whatever the article is about (like a chad I only read headlines), but in practice it seems pretty darn tight IMO.

Is immich in a usable state yet? I was looking for a self-hosted image service a while back, but eventually I just went with pigallery2 mostly due to the extremely simple file storage (just point to a folder and you’re good to go), but I do miss being able to manage images/albums from the website and having a more mobile friendly version. I kind of avoided immich due to the repo saying it’s under very active development (#scary).

Isn’t it a local filesystem though, so I can’t expand the filesystem with other drives on my network?

That’s very helpful because glusterfs and ceph are probably my top two candidates. Will probably try it out.

the biggest selling point for me is that I’ll have a mounted folder or two, a shell script for creating the container, and then if I want to move the service to a new computer I just move these files/folders and run the script. it’s awesome. the initial setup is also a lot easier because all dependencies and stuff are bundled with the app.

in short, it’s basically the exe-file of the server world

runs everything as root (not many well built images with proper useranagement it seems)

that’s true I guess, but for the most part shit’s stuck inside the container anyway so how much does it really matter?

you cannot really know which stuff is in the images: you must trust who built it

you kinda can, reading a Dockerfile is pretty much like reading a very basic shell script for the most part. regardless, I do trust most creators of images I use. most of the images I have running are either created by the people who made the app, or official docker images. if I trust them enough to run their apps, why wouldn’t I trust their images?

lots of mess in the system (mounts, fake networks, rules…)

that’s sort of the point, isn’t it? stuff is isolated

You won’t be able to catch one on camera.

Yeah I guess you’re right. Probably just seen the Source Code Pro one so many times that I stopped being annoyed with it.

Should try exposing myself to the Jetbrains Mono font until I get used to that instead, then I won’t have to fiddle with that part of the IDE settings.

I use SauceCode Pro (variant of SourceCode Pro with nerdfonts stuff). I’ve given up on changing it because everytime I do I find stuff that’s “non-standard” in the fonts I test and it bugs the hell out of me. @ signs are the absolute worst offenders, which is weird because they have a very uniform look everywhere that’s not a specialized “programming” monospace font.

Yes, but at the end there should be a single all lowercase “i love gradle”

Gradle is fantastic, but there is this mantra you have to chant while tinkering with it:

I hate Gradle, I hate Gradle, I hate Gradle, I hate Gradle, I hate Gradle

But once you get it to do whatever you want it’s way more powerful than Maven, since it’s actual code. Also you will never get me to voluntarily define my project structure in XML.