You should maybe read about the use cases for deduplication before using it. Here’s one recent article:
https://despairlabs.com/blog/posts/2024-10-27-openzfs-dedup-is-good-dont-use-it/
If you mostly store legit Blu-ray rips, the answer is probably no, you should not use zfs deduplication.
Yeah… So I’m in Berlin, and in Germany the internet operators finally are building fiber everywhere. The provider who lays the fiber to our street is Deutsche Telekom, and they promise to pay everything: laying the fiber, bringing it to our house and bringing the fiber to every apartment for a two year monopoly on fiber internet after which it’s up for competition using their cables. What needs to happen next is our landlord (a Swiss company) and house management company to agree on these guys to come in, put little fiber dividers to every floor and drill a hole to the walls so we get the fiber cable to our apartment.
Of course this being Germany, they are very slow on agreeing on that, we might need to go to court and for sure we need to talk to our neighbors who own their apartments to push them a bit. I’d expect us to get the connection maybe before end of 2025. But eventually it will happen…
I am doing exactly the same as what the OP is doing. In addition to that, I will unify my beelink mini PC proxmox server and our old Intel atom NAS into one rack server with AMD EPYC, proxmox and truenas in a VM.
I sure hope our landlord and the Internet operator can agree on the operator finally bringing fiber cables to all apartments. Then I would have fast enough uplink to my homelab.
Graphene only works on Pixel phones. Graphene is more private and secure, but might be too many issues for people who do not care about such things that much. Lineage has better support for different phone models, and you can make it just like a normal Android OS, that just happens to provide updates for your phone years after the manufacturer stops sending them.
Neither of them is better than the other, it’s just about your priorities. Get Graphene if you have a Pixel and you value privacy and are willing to tinker with it a bit if some apps don’t work.
Linux kernel updated to 64 bit time quite recently. In 2038 I can guarantee somebody in a very serious business is still using an ancient RHEL and will have issues.
And not using 32-bit integers to calculate time. Which is still a thing in many many many codebases written in C or C++…
I can validate this. I work as the IT ops guy for every Fortune 500 company and we only use RAID-0 for backups.
Rust and Cargo enters the room.
We’ve been using Linear in my latest company and it is actually quite good. No bullshit fast UI, boards, issues linking with Git, a support that can take a feature request that is often implemented in a week or two after asking it.
I run invidious at home on my proxmox server. The server is available everywhere with tailscale, so I can use it even when travelling. If Google ever blocks this, nobody at home can watch youtube anymore…
It kind of fails with certain protocols. I once wrote an async MSSQL client for Rust, and some data doesn’t say its size in the headers. So this kind of forced the business logic to be async too.
Never had one, just partied in the uni and dropped out :D
So basically your typical network protocol is something that converts an async stream of bytes into things like Postgres Row objects. What you do then is you write a synchronous library that does the byte conversion, then you write an asynchronous library that talks with the database with async functions, but most of the business logic is sync for converting the data coming from the async pipe.
Now, this can also be done in a higher level application. You do a server that is by nature async in 2024. Write the server part in async, and implement a sync set of mapping functions which take a request coming in and returns a response. This can be sync. If you need a database, this sync set of functions maps a request to a database query, and your async code can then call the database with the query. Another set of sync functions maps the database result into http response. No need to color everything async.
The good part with this approach is that if you want to make a completely sync version of this library or application, you just rewrite the async IO parts and can reuse all the protocol business logic. And you can provide sync and async versions of your library too!
That’s why you write your protocol as a sync library, then implement the async IO separately and mapping the data over the protocol modules.
dbg!(1) all the time…
It is very different outside Berlin too. But one of the reasons is how most of the clubs here are very queer friendly, and it is easier for people from different backgrounds to go there if they know their presence there is not leaked to their families from some photos.
I also noticed that underground parties in countries like Finland started to follow this trend. In these cases it is more to filter out cameras on dance floors which obviously makes the parties more fun when people are just not using their phones all the time.
This is what I really like about clubs in Berlin. When you get in, they put stickers to your phone’s cameras. If you take them out and try to take photos, or they see you removed the stickers when you get out, you need to delete all the photos you took in the club and you’re never again welcome to their premises. Makes also dancing there super fun because people really dance, not focus on taking a video of the DJ.
It creates a set of symlinks so every program sees exactly the dependencies it needs.
https://nixos.org/guides/nix-pills/09-automatic-runtime-dependencies#automatic-runtime-dependencies
You can also create a container:
https://nixos.wiki/wiki/NixOS_Containers
Or you can create reproducible docker containers with nix:
https://dev.to/anurag_vishwakarma/a-better-way-to-build-reproducible-docker-images-with-nix-2k59
The secret sauce with nix is reproducibility. If it builds once, it will continue building exactly like that forever. Bit by bit.
Nix can build you a bit-to-bit exact environment for your app. It is a superior environment, but is hard to use in the beginning and users can feel snobby sometimes. It is awesome, but YMMV.
I really try to move to Jellyfin, but there’s always some papercuts that block me. Tried it last weekend again, and:
I also tried Navidrome for music. Weirdly it had hiccups playing some files, and DSF was again a problem.
I really want to get out from Plex, but I use Plexamp so much and it handles my huge music library really well it’s hard to switch :(