Hey look, the thing many of us have been complaining about when it comes to the MIT license has been shown to be true, imagine that

They did not even launder it /s

In the age of LLM code laundering, I'm not sure any license will protect a project, open source or not

never heard of ts

OT, it completely checks out that danemadsen's github history is filled with "AI" development.

I've been playing Linux for a while, and I'm pretty sure it's spelled "guthib".

OverTheWire bandit is really fun. I was able to get up to the level with the encryption stuff. The encryption stuff confused the hell out of me.

Be sure to use the manuals and the wiki entries about the relevant commands listed on the website. You need to use some comprehensive reading and crack your brain. It is quite literally a puzzle. Not much I can say to you to help you without spoiling the puzzle.

Sounds manageable but I will only know the next time I end up on GitHub. Thank you for the help though, it might just be enough to get me through.

I have not worked it out

The secret is you have to scroll all the way to the bottom and click the tiny link that says "releases". Or sometimes click the ellipses (...) at the top of the page and find it there. From there you scroll to the bottom of the latest release and expand the section that says "assets". Then you typically need to understand package formats and choose the correct one for your device.

I'm personally very happy with my proxmox based server(s). I'm using community scripts for many of the setups of actual services. Over all, it's low maintenance and if I'm having issues it isn't with the host system. Not once did a system update cause a failed boot after.

That being said, NASty sounds rather promising. I doubt I'll switch over, but it might at least make for a fun experiment. And being nix based is rather nice for reproducibility.

I have not worked it out, too many times a search ended at GitHub; it’s like the great filter for me, I cannot for the life of me get past it.

Similar/ related Linux instructions are often the same. Just do the gobbiligoo and write magicmumbojumbo in the wolooolooo. It is often just presumed that you know all terms, and that you automatically skip the first 5 steps which are soooo obvious.

Same with proxmox/openmediavault/docker. It just works, as long as I remember to clear old docker images before they fill up root

Funny calling a nerd stupid. Probably doesn't even know what guthub is.

Superglue is ca glue. Ca glue chemically bonds to itself and mechanically bonds to the surfaces it’s put between. I would like to know the kind of glue you are talking about. I never instructed the op to glue a nut to their ssd, however that would be a fine thing to do.

If it’s not clear by now: yes, I believe the problems will be resolved with a heatsink. They asked about how to stop losing ssds in an environment with passive cooling and the answer is a heatsink. Even if I didn’t have a wealth of theoretical knowledge that can simply be regurgitated while on the toilet to people who will not read it, I also have experience dealing with flash memory in sealed, passively cooled and high vibration environments which indicates that conclusion.

Here’s how a heatsink will resolve their problems: the heatsinks huge increase to their nand chips thermal mass will reduce the effect that periodic reads and writes have on its die temperature and the heatsinks much greater surface area and better transfer properties will dump that heat into the ambient air much faster than the surface of their nand chips package will.

Their pc has vents and is designed to rely on passive cooling. Perhaps it will last a long time, perhaps not. Pulling the ol “would that end racism? Would that end sexism?” Is akin in this instance to rushing into the operating theater to disrupt an in progress remediation of gunshot trauma to inform the staff that the persons heart disease is a big deal.

Why not truenas?

it is a website for code, built for code tools.

Tell that to the people who distribute their applications exclusively through GH. I can't count how many times I've been told "just DL it from GH" and I have to reverse engineer the site to find the download link. I have it figured out now but it certainly could be a lot easier. And while I don't agree with the way it was presented, I empathize with the thought process.

Installation instructions are often terse with a bunch of assumed knowledge left implicit.

It becomes a sidequest needing an investment of an unknown amount of time with no guarantee that you'll have a working program at the end of it.

Man pages can be just as bad, like the developer was ticking a box.

It's called WSL. You can install it straight throught the Microsoft Appstore, whatever it's called.

You can find linux.exe easily on limewire or gnutella, should be just a few megabytes in size, enjoy!

But unfortunately a fair amount of smaller projects do use it as a download site.

And I get it, not everyone has the time or budget to make a website for their own little passion projects, and it's probably not even worth it for a lot of them given their limited audience. I'm not gonna say that every little tool to make my computer do some goofy thing that only me and about 6 other people care about (and 3 of those people are the people actively developing it) needs to have its own website.

But I feel like a lot of projects could benefit from throwing a "If you're not here for the code and just want to download and run the program click here" message at the top of their page

Also, this is neither here nor there, but as something of a Linux noob, I'd kind of appreciate it Linux installation instructions included some brief explanations of what the commands they're having you type into the terminal do. Sure, sometimes it's as simple as "sudo apt-get install program" and you're off to the races, but other times it's a multi-step process of transcribing magic spells into the scary black & white hacker window.

And as someone who's decent with computers and trying to learn more I don't mind doing a little research to figure out what I'm actually doing. But for your average computer user who wants things to just work, I think that's a bigger stumbling block to people giving Linux a fair shake than a lot of programmer types think it is. A tiny bit of handholding can go a long way.

In that specific case it would the be exchanging of clanker with the n word that would be racist, not the clanker in itself part.

But yeah thats wack af

yeah, if there was a sign saying "sandwiches sold here, please come in" (or, without the analogy, a readme with an "installation" section) then it's different. point being, it's not the original intent.

Yeah! And let me buy it at the store on CD!

No experience with NASty, but:

Had a server die on me about a year ago and wanted more Infra as Code. Tried Fedora CoreOS first, but the cycle was constantly creating a new USB bootable, it was just a bad fit for me.

Switched to NixOS and definitely still not an expert, but it's simple enough that 4 machines are running it. I really enjoy it. Already migrated a critical machine, where I basically used a second machine for A/B testing, to ensure minimal downtime and rollback possibility.

My deploy story is still kinda jank. I just looked at what worked and didn't read too much about the internals. Using deploy-rs and falling back to nixos-anywhere when necessary.

Some new services were really basically as easy as adding services.example.enabled = true; and deploying.

Hope it helps an good luck!