We need some sort of historical torrent indexer for lost/dead torrents, a wayback machine for magnet links that gathers/scrapes them automagically from the internet
I didn’t see anyone mention Warzone2100 yet. An excellent RTS, with a neat research system and unit customisation, and fun campaign. They’ve recently added a couple of new campaigns I haven’t played yet, and have enough ongoing dev work on skirmish/multiplayer that some AIs are listed as “X% win rate in AI matches”.
we are a tech company. we had several floors in two near but separate buildings. we had as many toilets for woman as we had for men. basically each floor had one for woman and one for men which had a pissoir too. as we had > 90% men, mens toilets always had a waiting line after lunch time (not for the pissoir, however). on one floor the only woman was a trainee who (normal here) often had to go to school for 3weeks in a row, that was when men just used womens toilet as there was no woman to use it on the floor and the other woman on the other floor of that building literally had her very own toilet to share with no one. (rest of all the woman happened to work in the other building)
then the company started to build its own building to leave the rental situation and at the same time to better longterm meet some necessarities that come along with the market niche that the company serves. (there are some laws regulating some physical aspects of the building for our services.)
one if the promises was, that the “toilet situation” would be improved with the new building.
the new building then had larger toilets on each floor. the space was then used to still have one toilet for men, but now there were two pissoirs! and two large sinks just for washing hands. yay! womens bathroom now have 3 toilets on each floor each and also the large sinks too. same amount of toilets for 90% of empleyee, the 10% have now triple number toilets they had before and double the space for washing, using mirror etc.
The woman basically gets her own.
exactly, and when men don’t have enough toilets, women actually gets build more of them to “statistically” solve the problem !! 🤣
yes, that is the transgender agenda, we switch genders each time we open lemmy and use blahaj plushies to stabilize, don’t blow our cover like that in public though jesus christ
It seems like the big problem with Yotta right now is that it is caught up in the Synapse fallout. These small financial firms advertised that their customers funds were insured, but didn’t hold them directly, they held them through intermediaries like Synapse who did have the US FDIC insurance. When Synapse collapsed, all the funds held by Synapse’s customers like Yotta got stuck in limbo.
I mainly developed it for myself, and sharing it if others want to do what ever they want to do with it, took many hours to just put together all the readmes and examples and cleaning up the code, I understand everyone wants me to release it on some git platform, but I didn’t develop it using any cvs at all and don’t plan to do that either
I’m not familiar with that side of Linux as I’m primarily a user. But that’s how our devops pipelines work to ship apps/websites. We’re shopping the entire working package with every update, and rolling back with issues. It’s a fantastic system since as a developer, I can isolate problems.
I never thought about that on a OS level. And I support it!
Changes to a declarative operating system, such as NixOS, are atomic. This allows for easy experimentation and rolling back to older configurations.
For example say you install gimp for editing photos. Normally you’d just install it using command line or a clickidity gui program. But say you don’t like it. Maybe it causes an issue. Then you have to uninstall it again. You are applying yet another action to the same system. That system is mutable, or modifiable, and that introduces some extra complexity.
With NixOS you can simply roll back to the previous state you had before installing it. It also doesn’t have to support stuff like uninstalling. The downside is that it likely uses a bit more resources when changing configurations.
This also applies to stuff like user management, services, e.g. a webserver.
Any experts correct me if I am wrong, I haven’t tried any of these systems yet.
We’ve known since the 1950s that our configurations should be declarative, to make them resilient to necessary changes to our software stack.
Instead of coding exactly what change needs made, we ought to write a config that declares the intended outcome, and then do extra work to write code that correctly interprets that config. This way when all the commands we used stop working (and they do!), we still know the original intent of the configuration.
But making config management declarative is a lot of work. So fuck that noise. I’ll do it in bash, instead, again.
Nix actually IS Bash under the hood. It uses Perl and Bash to create an atomic installation. I tend to do a LOT less maintenance than I’d need to do if I rolled everything from scratch in Bash.
Maybe homelab stuff that you mess with a lot and need to revert or stand up a multitude? I tried it for self-hosted apps and frankly a docker host is way easier. JB guys were pushing it for Nextcloud and it was a nightmare compared to the Docker AIO. I guess you could stand it up as a docker host OS, but I just use Debian, it’s pretty much bulletproof and again, less hassle.
I recently switched to nixos, because my ACME image was failing all of a sudden and I didn’t know enough what was going on under the hood to fix it.
It was a steep learning curve, but the infrastructure as code approach just works too well for me, since I just forget too much what I did three years ago, when doing things imperatively.
for a user that isn’t trying to maintain a dev environment, it’s a bloody lot of hassle
I agree but I prefer it to things like ansible for sure. I’m also happy to never have to run 400 apt install commands in a specific order lest I have to start again from scratch on a new system.
Another place I swear by it is in the declaration of drives. I used to have to use a bash script on boot that would update fstab every time I booted (I mount an NFS volume in my LAN as if it were native to my machine) then unmount it on shutdown. With nix, I haven’t had to invent solutions for that weird quirk (and any other quirks) since day one because I simply declared it like so:
IMO, where they really shine is in the context of declarative dev environments where the dependencies can be locked in place FOREVER if needed. I even use Nix to build OCI/Docker containers with their definitions declared right inside of my dev flake for situations where I have to work with people who hate the Nix way.
No end of interesting shit you can do in Nix, at one point I had zfs and ipfs entries in one of my configs. I got away from it all before flakes started to get popular.
I tried it as a docker host; the declarative formatting drove me around the bend. I get a fair bit of disaster proofing on my docker host with git and webhooks, besides using Proxmox/ZFS to host it all and back it up.
nd of interesting shit you can do in Nix, at one point I had zfs and ipfs entries in one of my configs. I got away from it all before flakes started to get popular.
I tried it as a docker host; the declarative formatting drove me around the bend. I get a fair bit of disaster proofing on my docker host with git and webhooks, besides us
I suspect that the whole Docker thing will improve exponentially now that Nix is on the Docker’s radar. I found the OCI implementation to be superior to the actual Docker implementation in Nix…at least for now. I think the way that Docker isolates things to layers is the biggest barrier to them working together seamlessly at the moment…but I think they’ll start to converge technolgically over the coming 10 years to the point where they might work together as a standard someday.
Started a “community support” projects group with friends. We schedule a day to descend upon one of our houses and take care of whatever tasks need to be done - painting, yard work, home repairs, etc. It takes very little time with three or more people dividing the work, and we can chat and joke the whole time. We got a lot done, had fun together, and we’re done by early afternoon.
Next weekend everyone is coming here to help cut up a fallen tree, and the weekend after we are renovating another friend’s small dayroom.
kbin.life
Oldest