Let’s encrypt doesn’t have to be accessible from the web, it accesses the web itself. It’s a subtly difference i guess, but you don’t need port forwarding or anything. Of course if your jellyfin/immich service is completely blocked from going out on the internet then it still won’t work.

as far as I know, there is no way to put a valid certificate like let’s encrypt for a service that is not accessible from the net

I don’t think that’s true. But Let’s encrypt does need to verify the domain name. If it’s just a domain you made up in your LAN that is an issue yes. But I have no experience with that though.

You could use self-signed certificates, they are free. but you would need to add custom trusted CA to all the user devices manually. I’ve never done this myself so no clue how troublesome this really is.

What I do is have a reverse proxy that requests a wildcard certificate (e.g ‘*.example.com’) with Let’s encrypt. And then route all my services through the reverse proxy with subdomains. You can get free domains with duckdns.org or others.

Buys closed eco system phone. Shocked it’s a closed eco system. Cue shocked Pikachu face?

I love it for using klipper. But when I started doing it the klipper pkgs did give me some troubles. You can work around them, but know you might find some issues on the way. Maybe it’s better now, I haven’t really updated that part of my config much recently.

Do know that not all arm devices are equally supported. rpi 3 and 4 are, the rest is community based (see: https://nixos.wiki/wiki/NixOS_on_ARM). Personally I run klipper on a x86_64 thin client for this reason and because raspberry pi’s were scarce and expensive back then.

I have to be honest and say it was a journey. Nix in itself isn’t really difficult I find. But everything together and finding the right documentation and figure out how NixOS comes together can be a bit daunting.

But a simple straight forward config is pretty doable. My advice is to start small and build up. You can reuse your old dotfiles and include them in the configuration directly, so you don’t have to convert everything to nix (right away). Also don’t scare away from using flakes, they are the way to go in my opinion.

You can define multiple hosts/systems in one configuration with each their own nixosSystem call. So you can define hardware/fs/network etc per system.

Also I like to add that the vimjoyer video’s on nix helped me with understanding some of the concepts, They are usually short and straight to the point.

I’ve converted everything to NixOS (Desktop, laptop, nas and 3d printer, rpi with home assistant) only my router is still pfSense (and thus BSD). It just makes configuration and updating so much easier from one central configuration. And I don’t have to remember what and how I installed something. It’s just there in my flake.

If string return nan, else % 2

So now you return a number type if it’s a string and a boolean if it’s an integer. How does that make sense?

The is-even lib exists to sanitize input by throwing an exception which imho is better.

Edit: having looked at the code better. Apparently it still allows string coercion (boo). It only checks for non integer numbers.

To be fair in a dynamic typed language with dumb string to int coercions, I kinda get why such a library would exists. So it’s more a symptom of terrible language design than modern dependency hell.

In c style languages, Java, c++, rust, etc.

I think it’s a fair strategy. If they know what happens if you do it wrong people suddenly complain less about rust’s borrow checker. Whereas people who are only used to garbage collected language don’t usually have the slightest clue why it works the way it does.

I disagree. I love it for a desktop system . The fact that you can just try a package/app out with nix shell -p pkg and it doesn’t mess with your global environment and don’t have to bother to uninstall/clean up is very nice. Also combined with direnv/shell.nix it’s really nice for setting up different dev environments, no need to globally install your dev tools (of course you can also do this without nixos too). Or the fact I can run a test variant of my setup without being afraid of corruption with nixos-rebuild test and it will never be able to fuck my existing setup…

Of course, configuring everything in a single structure is a bit of work at the beginning. But it’s really not that bad (though the documentation could really use some work) . You can just reuse your existing dot files by just including them without converting them to the nix language. And the fact I can now update and configure all my systems from one place and one structure is amazing, without having to ssh in every machine and remember how it’s configured.

Now does that mean it’s the final distro? Probably not. But would I go back to a non-declaritive setup? Most definitely never. Maybe I’ll try out guix sometime, but I personally never liked lisp variants as a language. But who knows what else comes along. But imho declarative is the way to go for any setup, desktop or server.

This so true, every one complaining that the borrow checker is annoying isn’t apparently aware what they used to do was inherently flawed. Sure there a some, though rare, false positives. But they are easily mitigated. These people are exactly that what they themselves are complaining about, elitist.

Exactly, if garbage collection meant memory safety then why do we get null pointer exceptions about every 5 minutes in Java. Garbage collection is about memory leaks, not safety. Imho the borrow checker is a better solution than garbage collection and faster to boot.

It’s been about 20 years since I’ve touched PHP. So i don’t remember all the problems i had with it.

But some language from those times were at least consistent with itself and clearly more thought-out. Even though they might miss some of the nicety we’ve come to like nowadays. Of course for web development there weren’t many better choices back then.

But I’m heavily skewed towards non-oo, static typed, explicit languages so PHP was probably never for me.

I somewhat know the history of PHP and how it came to be. And that it was just a personal project that suddenly got big. So I don’t blame the creator. But that still doesn’t make it a good language.

Let’s be honest though. The early PHP versions were absolute dog shit. And the definition of how not to design a programming language. That said, that never stopped anyone in web development from using it apparently. No clue what modern PHP looks like, apparently it’s better now.

So Google maps should be shut down too? Or you could use it to find a route to someone who has been doxxed for free! This logic is really flawed…

I always see people advocate for Stremio. But my experience was always very mixed. Half the time it would just buffer all the time. I guess it’s s my own fault for having little interest in the latest Marvel/Hollywood movies, but alas. I way more prefer my jellyfin/jellyseer/arr stack. Once it’s available I’m (99%) sure it works from everywhere in the world.

I understand it will be a cat and mouse game. But surely its possible to make a curated list of big offenders akin to advertisement block lists?

Not necessarily about stack overflow. But i just got myself in a situation where the first search result I found for a problem was clearly AI generated. And the solution it provided was not at all technically possible. The AI decline is really terrible…

That said, does anyone know of an extension or block list for those terrible AI slob websites? Or a way to filter it from duckduckgo?