completely naked
completely naked


close, but it would actually be missing the codec in proton. bazzite actually comes with a very comprehensive ffmpeg build and all its dependencies.
steam just can’t include those proprietary libs in proton. luckily, protonge exists for this exact reason.
this is most likely an acpi issue. acpi is vendor specific and it’s hard to support every one. there are some work arounds, I’d see if there’s anything in dmesg and go from there. definitely annoying tho.


I haven’t looked at that GitHub but I’m familiar with most of the terms so here goes (verify them if you wish, I can’t promise full accuracy).
portable file server with accelerated resumable uploads: portable most likely means it’s easy to transfer from one server to another should you ever upgrade servers or anything else. resumable means you can pause the transfers if you desire.
dedup: it will automatically deduplicate files. so if you upload the same file twice it will just use the one you previously uploaded, saving space.
webdav is for distributed authoring and versioning. I don’t know a crazy amount about it but assume it means there’s some code in place that aids with collaboration as far as sending a file, working on it, and reuploading goes.
ftp: file transfer protocol.
tftp: trivial file transfer protocol. good for small things but iirc it’s not inherently secure
zerconf: plug and play. no messing with configs needed.
media indexer/all in one file: most likely indexes media uploaded and stores the generated thumbnails in one big file. most likely this is so it’ll be easier to transfer the install to another server if needed (you can move one big file containing all the thumbnails instead of a bunch of tiny ones).
no deps: no dependencies, everything you need is self contained in that repo.
again, double check things your curious about but that’s my interpretation of what most would agree is kind of just a keyword filled description lol


can’t pronounce the name of this song itself, but there’s this Japanese band called glim spanky that has some absolutel bangers.


according to that page the issue stemmed from an underlying system responsible for health checks in load balancing servers.
how the hell do you fuck up a health check config that bad? that’s like messing up smartd.conf and taking your system offline somehow


almost done re setting everything up after a catastrophic failure (ended up replacing multiple drives, the CPU, the motherboard, the psu, and the ram).
now I’m just running long command after long command, waiting for drives to zero, ensuring extended smart checks pass on new drives, cloning to my backup drives…
this things been down for a few weeks and I’m so excited to have it back up soon!
anyways, moral of the story is, the 3-2-1 strategy is a good strategy for a lot of reasons. just do it, it may save your ass down the line.


you can fix all of these issues at once by covering the lights with duct tape!


coffee and weed


depends on the job. shitty jobs I won’t give two weeks especially if there’s already animosity from management (which has lead to some pretty entertaining quitting stories). most I’ll do for something like that is ask my coworkers if they think they can get by without me (assuming I also liked the coworkers).
if it’s a job I liked, I typically give notice via email and then go and bring it up in person to the recipient as well.


depends on the type of solder but yeah, I’m not exactly holding it there tho. just high airflow at that temp for a few seconds to push the rosin underneath the chips. helps a lot with bga chips where water can actually get underneath the chip and short connections or leave debris even once evaporated. for actually reworking chips I use around 480c.


no. if you want to do component level board repair for water damge, this is how you do it professionally. I’ve been using this strategy for 5 years or so now and it has much better success rates than just cleaning the board with ipa.
maybe overkill for most people since it requires more specialized tools but if you go to a shop they’ll most likely use similar techniques at least to assess the damage


best way I’ve found to isolate and repair water damage is to open it up and apply some high quality liquid rosin to the water damaged areas. then hit it with hot air (300c should be fine) to get the rosin under all chips and connectors. lastly, do not clean the board, it can push the corrosion around and cause more issues.


yes. I think a lot of people can. the thing is, the people who can won’t be the runs running for office


Mexican and middle eastern and I’d die happy


in the same vein (storing more data in less bits) you should check out tagged pointers as well!
I don’t think that’s a useless implementation at all. code looks relatively clean, and it definitely has its uses in the embedded systems world.


we’re in a thread about a script that can download and activate windows editions in place for free…


honestly proton and lutris are godsends for getting old software to work. I feel like I can get old exes working on Linux that wouldn’t work on windows
I think modern compilers do actually compile recursion to be equivalent with an iterative model.
edit: yes when possible they will compile to be iterative, but if it can’t be written iteratively it will be a series of calls and returns. depends on the specific type of recursion it looks like.