I think the most hurtful thing with seeing #NixOS in flames and people leaving for other immutable distros is...
NixOS was strong for its module system, not so much its immutable nature.
The rapid development you could do, and test that locally, sewing together an entire fleet in a matter of hours, without much of a thought to the minor details was amazing.
Lets remember to take the NixOS module system with us.
@soupglasses I have worked with professional, smart developers, born in the 90's, at FAANG-level corps, who, with a straight face and very earnestly, have told me that "no license means everyone can use it". They have literally never lived in a world where that was true...
With the talk of #Redis becoming proprietary in licencing. I want to highlight Apache KVRocks! A true open source Redis compatible NoSQL database, ready for use! :blobfoxaww:
@AngryAnt You can do that, but nowadays it is much more common to use it to overclock your monitor.
Basically where you pull your EDID, use software like "AW EDID Editor" to change its timings. Then use the linux kernel to override the display port's EDID for any connected monitor.
I use this strategy to overclock my 100Hz monitor to 115Hz, for example.
@soupglasses So in these instances, the self-reported data is correct, but the actual hardware supports more than what is reported in it and specifying those numbers then unlock the full hardware potential?
Im slowly starting to run out of energy for running #NixOS thanks to its constant issues.
23.11 has broken so much, i cant even save images without crashing the webbrowser now. And that doesn't help UnityHub also being broken now too...
Honestly this all just kind of makes me depressed, as I don't want to leave Nix behind either. But from how broken both my server is (open issue for the broken package), and now my desktop... I don't really know where to go.
@soupglasses but I am also not the kind of user that usually opens issues for problems but straight out PRs with fixes. Maybe I am just the kind of crackhead that so deep into things, that I usually know how to help myself.
What's the issues? Maybe we can do some wizardy and fix them. 🪄
I really want to like #GNOME, it's such a nice and uniform experience. The best DE around by far. But its straight up user-hostile feature lockdown feels more like proprietary software than open-source.
Why is the wayland screenshot API private to GNOME devs only? Why can't I set my own folder formatting? Why do you not trust me?
Even as a developer, wanting to create a solution, I am unable to. "Open-source" GNOME feels worse than what I'd expect MacOS gives me with APIs. Gah!
@soupglasses The screenshot file format could be added as a setting, but allowing creating sub-folders is a bigger step; what happens if you set "../../../some/random/file" or whatever else? Remember that the shell is a privileged component, and everything that has access to your session can write to your settings.
@sandro I'm not sure. I'm just trying to package a CMake project but it doesn't export/install correctly and it's ending up being one of the hardest undertakings I have done in months.
I just want to make it export the files to the right location. :blobfoxcry2:
@soupglasses because upstream used the wrong variant of the plentiful variables available which make no difference in debian but a very big one in Nixos?
So, #BlueSky 's main selling point over #ActivityPub is its data portability guarantee in case of a server shutdown. But according to the docs, this is based on a recovery key that only works within a 72-hour window, generated by the server and backed up to your devices.
Wouldn't this mean a BlueSky account would often have less than a 3 day notice to move to a new instance when a server shutdown occurs, or else loose the account? :blobfoxshocked: