Nix user arrives to the room.

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.

Nice! And they will probably differentiate from the competition by allowing GPL applications and sideloading, and having a total control for your privacy and no tracking, right?

Right?

No, it means if you run Lemmy as a service and make modifications to it, you have to release your modifications back with the same license. Otherwise you couldn't use a browser that's not AGPL and read pages running on top of an AGPL server.

What AGPL is really good at is how nobody can take Lemmy, run a proprietary service and add incompatible features without giving them back to the community. So nobody can fork Lemmy, create a new VC-backed Reddit clone and start making incompatible changes to the source without the main project getting the source code.

It comes with the Office subscription. People who choose it are not the ones using it daily.

A great UI to stream your movie files from your TV. A bit like Plex, but open source.

The mandatory comment to any printer discussion. Buy a brother laser. Nothing else. Preferably used.

Helix. A perfect programmer's editor you can use with almost no config.

It was great to watch all these runs on twitch. Now if Nintendo would just release an open source version of the server and all the content people have created...

Is that Luanne?

Hetzner crowd says hi!

Sauce

https://tech.lgbt/@endali/111450318096238934

Opens up a web page with a tracking cookie so they can analyze what interests you.

Lenovo Thinkpad T14s AMD. Runs Linux perfectly, is fast, has a great keyboard, has a great trackpoint, and has good battery life.

If it doesn't run Linux, I don't buy the laptop.

What I did is I bought a cheap small PC with an Intel chip (i5), some RAM and an SSD. You can find these with more than one NIC pretty easily from Amazon, and they are just normal computers: only small and quiet. Then go with a virtualization platform such as Proxmox, and to that, install opnSense as the router distribution and use the rest of the processing power to run everything else in your house in virtual machines: Home Assistant, media server, you name it... Just search Amazon with something like "router pc" and you get a long list of machines below and over 200 euros that are more than enough for your home. Computers like this one.

The great thing about opnSense is how it gets regular updates. And when you use a normal PC as your router, you run the latest FreeBSD kernel and get updates basically as long as opnSense is developed.

You probably also want a Wi-Fi. These boxes usually miss it, and even when they have a Wi-Fi card, opnSense is not really great for setting wireless networks. I just bought a few APs from Ubiquiti. They are a bit on the expensive side, but I just don't need to touch these things after setting them up and the network never fails on me. There are also much cheaper APs in the market, just get anything that fits to your budget and plug it to the router.

Some people don't care about organizing their music and all that. They just want their playlists and an algorithm to tell what to listen...

Me? I enjoy my properly tagged Plex library.

thab's been trying to beat "The Last Dance" for a few days already, it's really fascinating to watch. And even barb finished one level, then said "fuck this garbage" and spent the next days finishing Paper Mario and complaining how boring it is...

It's been a few good weeks on Twitch...

I would love to participate. I've been doing Rust professionally for seven years now and I understand the language very well. Too bad there is just so much work already and adding a new project feels a bit too much. I'd love to read the source one day though, maybe I find some time.

ZFS is still the de-facto standard of a reliable filesystem. It's super stable, and annoyingly strict on what you can do with it. Their Raid5 and Raid6 support are the only available software raids in those levels that are guaranteed to not eat your data. I've run a TrueNAS server with Raid6 for years now, with absolutely no issues and tens of terabytes of data.

But, these copy on write filesystems such as ZFS or btrfs are not great for all purposes. For example running a Postgres server on any CoW filesystem will require a lot of tweaking to get reasonable speeds with the database. It's doable, but it's a lot of settings to change.

About the code quality of Linux filesystems, Kent Overstreet, the author of the next new CoW filesystem bcachefs, has a good write-up of the ups and downs:

• ext4, which works - mostly - but is showing its age. The codebase terrifies most filesystem developers who have had to work on it, and heavy users still run into terrifying performance and data corruption bugs with frightening regularity. The general opinion of filesystem developers is that it's a miracle it works as well as it does, and ext4's best feature is its fsck (which does indeed work miracles).
• xfs, which is reliable and robust but still fundamentally a classical design - it's designed around update in place, not copy on write (COW). As someone who's both read and written quite a bit of filesystem code, the xfs developers (and Dave Chinner in particular) routinely impress me with just how rigorous their code is - the quality of the xfs code is genuinely head and shoulders above any other upstream filesystem. Unfortunately, there is a long list of very desirable features that are not really possible in a non COW filesystem, and it is generally recognized that xfs will not be the vehicle for those features.
• btrfs, which was supposed to be Linux's next generation COW filesystem - Linux's answer to zfs. Unfortunately, too much code was written too quickly without focusing on getting the core design correct first, and now it has too many design mistakes baked into the on disk format and an enormous, messy codebase - bigger that xfs. It's taken far too long to stabilize as well - poisoning the well for future filesystems because too many people were burned on btrfs, repeatedly (e.g. Fedora's tried to switch to btrfs multiple times and had to switch at the last minute, and server vendors who years ago hoped to one day roll out btrfs are now quietly migrating to xfs instead).
• zfs, to which we all owe a debt for showing us what could be done in a COW filesystem, but is never going to be a first class citizen on Linux. Also, they made certain design compromises that I can't fault them for - but it's possible to better. (Primarily, zfs is block based, not extent based, whereas all other modern filesystems have been extent based for years: the reason they did this is that extents plus snapshots are really hard).

I started evaluating bcachefs in my main workstation when it arrived to the stable kernels. It can do pretty good raid-1 with encryption and compression. This combination is not really available integrated to the filesystem in anywhere else but zfs. And zfs doesn't work with all the kernels, which prevents updating to the latest and greatest. It is already a pretty usable system, and in a few years will probably take the crown as the default filesystem in mainstream distros.

So... They've been A/B testing this the whole time and will continue to do so. Do you think OP is lying or could it be that you're having the B variant until it flips for you too?

Magit

It was a great commentary on 80's working class life. Kind of like a middle finger to all the traditional family shows, really anarchist if you see it in the context of late 80's television.

I've been running NixOS for the past four years in all my computers. It's really, really the end game of Linux distributions for me. But it's not for everybody. The Nix language can be a tough thing to learn, if you're not a programmer and haven't done anything with lazy functional languages before. It's a dynamic language, with not super great documentation for practical things and missing a good language server that would let you to jump to definitions when learning how nixpkgs work and how to build things.

Also, what I think is a serious problem, is how flakes are not yet enabled in the default installation. So first you learn with the basic template, and some helpful person comes talking about how great flakes are, and in a few weeks you might have written your own system flake finally and got it working. Flakes are really important to understand as soon as possible, because with them you get the lock file that gives you real reproducibility between computers and full control on which version of packages you get.

But, when you learn all that, and get your company to go full-on with nix, having flakes in all projects, it's the best programmer's operating system out there. Here's my config to steal stuff.

I use foot together with foot-server. The client opens in less than a millisecond, and I usually have tens of terminal windows open at the same time. Tabbing comes from the window manager.

Traces of the Rust work gets merged in every version. They come in small pieces, and now the next version has even more abstractions that are needed for the M1 GPU driver to eventually get there.

Yep. I switched from xorg/i3 years ago, and it was already super snappy back then compared to the previous setup. Today everything works with Wayland, and I don't really need to think about it anymore.

But, ymmv. I avoid Nvidia's products, which helps a lot for the stability.

Pickup trucks everywhere. No public transportation usually. General Tso's chicken is a typical Chinese food you get. Weed products are available almost everywhere legally. Light beer. No proper lager beer even in small breweries. How people drive. No sidewalks most of the time. The whole health industry. Electric sockets. So many churches. The general war against trans people. The general war against women.

"Are we going to call you a dad or a father?"

Somehow I stopped watching movies a few years ago, which kind of annoys me but we can't find time that much for a long movie. Of course binge watching TV series is another thing...

For me, the three rewatchables were:

• Stanley Kubrick: Barry Lyndon - If you're into cinematography and ultra techy perfection, this is the movie. And the main character is such an asshole.
• Celine Sciamma: Portrait of a Lady on Fire - This beautiful piece hits hard. Celine has an eye for women, and the story how the ladies take care of their own business since the beginning of time is really captivating.
• Pedro Almodóvar: All About My Mother - A queer classic. I really like the old Almodóvar telenovelas on acid, but this mid-career masterpiece has everything: the cinematography, the crazy characters and the melodrama.

Exactly this. And it shows a good example for other underrepresented genders that there are others too in the field and they are absolutely amazing; seriously in the top 1% of the devs.

I'm coming from the old ages of internet where we didn't have them. I'm fine with them, but I'm too old to use them comfortably.

It's fine. Use them if you like, but I don't really see the value in systems such as Discord where you pay money to have special emojis and so on...

Not until somebody challenges it in court and wins...

I'm running it in my homelab for projects I do not (yet) push anywhere public, and projects containing private items such as ssh keys. It is snappy and has a ton of features. I can imagine when the federation support works, one can set up their own git forge and contribute more easily to other forges no matter what software they run.

And, to be honest, that is already how git works if you use the email workflow. Here we just get a web based flow with federated issues and pull requests. But if email is enough for you, you can have a full federation with email and git.

You just have to be very careful to not have your developers to get even close to the AGPL source code, because if it's similar, there's a possibility the judge says you copied the AGPL code and now your license is AGPL too. There's a reason companies are really scared about everything related to the license...

But yes, this happens and you have to have resources to fight it. Which is not easy.

People like self-promotion and the chance of getting millions of views for your latest post. The Fediverse is like a nerdy book club in comparison (which is why I'm here).

I guess the only right thing to do is to buy used Brother laser printers until they all break... Such warhorses.

Psst. https://listenbrainz.org/

A good project to support would be the Ladybird.

https://github.com/SerenityOS/serenity/tree/master/Ladybird

If you ever visit Hamburg, this place will blow your mind:

https://www.miniatur-wunderland.com/

I don't even have words to tell you how cool that place is. We went to an art exhibition in Hamburg, and kind of accidentally went to see that place too. Like, they have day/night cycle there. They have trains with little cameras on top of them so you can travel in them. They have model planes landing and they have cruise ships going in real water.

So damn cool.