Pills here!
Badabinski @ Badabinski @kbin.earth Posts 0Comments 393Joined 1 yr. ago
Badabinski @ Badabinski @kbin.earth
Posts
0
Comments
393
Joined
1 yr. ago
I swear I've seen people use bump keys on high quality tubular locks before.
Sounds like you may want to use a union filesystem like overlayfs. I'm not sure if the specific behavior of overlayfs will work for you, but it's worth investigating.
Thank you for putting your use-case in your post, since otherwise I think this might be an XY problem.
EDIT: There's also mergefs and unionfs. I don't know what the features and drawbacks are for these three union filesystems. mergefs seems like it might be the most configurable, but it's also FUSE. unionfs and overlayfs are both in-kernel, so they'll perform better (which may not matter for your use-case). overlayfs is the one I'm most familiar with of those two, since it's used by most container runtimes.
I remember reading this article on the subject and finding it interesting: https://archive.ph/8xyWx
My terrible summary of that article is that it's really hard to turn cell goop into something that is recognizably hamburger. There's a shitload of structure to meat so you have to make the cells do their "turn into this part of a cow" thing. That's been really difficult to scale up. One shortcut you can take is to use actual animal meat as a starter, but then you're no longer making vegetarian meat, and I seem to recall there being some other issue with that.
I really want lab grown meat to work, but I'm losing hope.
I have some issues with these assertions.
Assuming we're talking US law (relevant because it's Facebook), reverse engineering has been tested in court and is not copyright infringement. It can be patent infringement, but is not necessarily so. That means that clean-room RE efforts like Wine are absolutely above board. If Wine devs haven't personally seen decompiled Windows code then they're good to do whatever.
WindowsFX/LinuxFX/Wububtu/whatever is sketchy. It has problems with trademark and copyright infringement (can't just yoink MS fonts, they have restrictive licenses). It does not represent the mainstream Linux distro community and is not something people should really be using (or paying for). Their license database with PII has been breached multiple times, as an example.
ElementaryOS's DE Pantheon looks and acts like MacOS, but Apple does not hold a patent on an application dock. You generally can't patent or copyright UX unless you're doing something really novel (like Apple's swipe-to-unlock feature back in the day). There's plenty of prior art that would prevent Apple from patenting most parts of their UI/UX. Pantheon's theming has a strong resemblance to Apple's "trade dress," but I'm guessing it's distinct enough to not be considered copyright infringement (it's not a derivative work and wouldn't be confused for or reduce the market share of MacOS).
Kali Linux is nothing special. It's just a Debian derivative with a bunch of pentesting and security tools installed by default. You could install most or all of those tools on Windows or MacOS, and I'm sure many people do. I have personally installed nmap on every computer I've owned over the past 10 years. There's nothing magic about Kali, it's just somewhat more convenient for people who do pentesting.
If someone at Facebook thinks this way, I hope they're disabused of their notions.
Like, fuck Facebook, I don't use that shit, but also fuck this weird dumbass decision they've made.
So, I really don't like Teams. What follows is basically an unedited stream-of-consciousness that came out of me after reading the question. I've reread it and now realize that it comes across as extremely angry and dramatic. I would not put Teams in the top 50 difficulties of my life, but I do not have much patience for incompetent software. I'm also just in a bad mood and decided to swing at Teams.
Fuck Teams' stupid fucking pseudo-markdown WYSIWYG editor. Either be markdown or don't, you fucking useless cretinous moron! If you're going to automatically insert an interactive code block when I enter a triple-backtick, then you should god damned well do the same fucking thing when I paste in a fully formed code block. (edit here) I do not want to see triple backticks, a new line, my code in a stupid non-monospace font, and then another triple backticks. I wanted a code block which is why I indicated my intention for it to be rendered as one by using the triple fucking backticks that you recognize(end edit). This is just one example, and I feel like I'm taking crazy pills every time I use that piece of shit chatbox.
I use Linux, which means I use Teams exclusively through the browser (they used to have an electron app for Linux but they got tired of dealing with it and deprecated it). I'd be fine with the browser thing were it not for the fact that when I type in the Teams URI, there's a 50/50 chance that I'll be sent to Teams V1 versus Teams V2. Like, why the fuck are you like this, Teams? I have clicked the god damned "take me to V2" button so many times! I think there's like, an option or something for it that I've also clicked. (edit here) I have cleared my cookies and browser data for Teams, I have completely nuked ~/.{config,cache}/google-chrome for Teams, I have installed Chrome Beta for Teams, and still the issue persists (end edit). I do not want to wait 30 fucking seconds for the V2 version of the page to load when I already waited 10-15 seconds. Don't get me started on how broken the "install this as an app" bullshit is, ugh fuck I hate it.
Finally, Teams has been really great at not fucking reading my auth cookie recently. My company uses Okta for SSO, and like, fuck man, most shitty web apps seem to get it. My browser stores a JWT, it sends that shit in a cookie, some magic crypto shit happens, and boom I'm authorized. Teams is just fucking deaf to this though, and it makes me click a "sign in again" button or some shit, which then has a chance to proc the V1 vs V2 UI issue. Like, come the fuck on bro I SEE the cookie when I look at my network requests, just put the fries in the bag and stop making my life that little bit more irritating.
Moss Landing uses NMC batteries instead of LiFePO4. NMC lithium batteries are more energy dense (they're often used in long range EVs), but they can also produce hydrogen and can autoignite if they go into thermal runaway. LiFePO4 batteries cannot autoignite and can't produce hydrogen. They last longer, and the reduced density is worth it for the safety benefits, which is why more recent grid storage setups use them and not NMC. A BESS using the right chemistry could not have gone up in flames like this.
Part fart? Parting farting?
In this case, there were 5 shooters. One of them had a cartridge loaded with a wax bullet, so 4 of them had live rounds.
Oof, I didn't know that about firejail. I'd heard of it, but I'd never used it. Like, c'mon folks! If you need privilege escalation, either require launching as root (if appropriate), or delegate the responsibility to a small, well-audited tool designed explicitly for the purpose and spawn a new privileged pid. Don't use SUID. You will fuck it up. If you reach the point where setuid is your only option, then you've hopefully learned enough to rearchitect to not need it, or to give up, or use it if you're, say, someone who maintains a libc or something.
EDIT: this is overly dramatic, but also it's not. I personally feel like using SUID is kinda like rolling your own crypto in terms of required competence.
Ooooh, I love that idea. That would be the perfect play, and the best part is that everyone (except for the people being exploitative shits) would benefit. Personally, I'd love it if Canada started jailbreaking cars, because then I'd be okay with getting an EV. I want a (used) BEV, but I don't want all of the spyware bullshit that new cars come with. I'd be overjoyed if I could spend $500-1000 to permanently enable all subscription features and rip out all of the data collection. I have never gone to a dealership for servicing (better to support independent local mechanics), so I wouldn't give a fuck about losing any sort of warranty. Bonus points if the jailbreak is FLOSS.
Here's to hoping some Canadian parliamentarian reads that article and agrees.
There was a huge kerfuffle about it here when it happened. We had a law on the books that allowed it and the dude insisted on it, ostensibly for religious reasons. I can't remember if we took the law off the books or not, but I hope we did. While nobody else knows who fired the killing shots, the people who did it know. If they're the type that wants to kill, then I don't want to give them the pleasure. If they're not, I don't want to make those people live with a violent death on their conscience. It's fucked up, just like executions in general.
EDIT: Execution by firing squad had been removed in 2004, but anyone sentenced before then had it as an option. Gardner was grandfathered in.
Yeah, little gasping breaths are a super clear symptom. I'd wake my partner up by thrashing, and afterwards she said I'd always be gasping and lurching around. Many people snore, not so many do the whole unconscious "oh fuck I can't breathe" thing.
I've likely had sleep apnea from before that age (I'm in my mid 30s now) and I never snored. I seem to recall that there isn't actually strong correlation between snoring and sleep apnea, although I could absolutely be wrong.
More indicative would be nocturnal gasping, waking up frequently, morning headaches and excessive tiredness, and lots of movement at night.
EDIT: also, weight is not a reliable indicator that one has sleep apnea. When I was diagnosed, I was 5'11" (180 cm) and weighed 130 pounds (59 kg). I was a very skinny man. I've packed on a sick beer gut since then without a worsening of my symptoms. Some people just have a shitty throatus that refuses to stay open.
You're correct that they can enter thermal runaway, they just can't autoignite. I really suspect that if this site has been using LiFePO4 cells instead of NMC, it wouldn't have gone up like it did. 3000 MWh of NMC cells sounds absolutely bugnuts crazy to me.
This is why you don't use battery chemistries that can thermally run away autoignite in grid storage. The plant was using LG JH4 batteries, which use an NMC chemistry. I don't think that LiFePO4 cells were as ubiquitous when this plant was first constructed, so the designers opted for something spicy instead.
This shit is why you use LiFePO4. It can't thermally run away autoignite, it lasts longer, and the reduced energy density doesn't really matter for grid storage. Plus, it doesn't use nickel or cobalt so the only conflict resource is lithium.
EDIT: LiFePO4 batteries can enter thermal runaway, but they can't autoignite.
We lack the materials and engineering necessary to make lifted weight storage systems enter the order of magnitude of energy storage needed to compete with batteries, let alone pumped hydro. It's just really, really hard to compete with literal megatons of water pumped up a 500 meter slope.
I believe that the plant in question was using something besides Lithium Iron Phosphate batteries. This press release mentions LG JH4 which are deffo not LiFePO4. LiFePO4 batteries are far, far safer than other Lithium chemistries, and are now the norm for BESS (not cars tho, since they have lower energy density but better a better lifetime than NMC/NCA). This fire would not have happened with a BESS using LiFePO4 batteries.
Now that batteries with aqueous sodium-ion chemistries are becoming available, we should begin transitioning pre-LiFePO4 sites to those wholesale. Aqueous sodium-ion batteries should be even safer than LiFePO4, and while they have kinda shit energy density, they're still fine for grid storage.
EDIT: correction, LiFePO4 batteries can run away, but they are incapable of autoignition.
Someone produced a brief song documenting the details of the Bass Pro Shop pyramid: https://youtu.be/jYE-1HfReQo
They have it for now. I expect that procedure will be removed within 5 years.
This is why I made the reference to Go. I honestly hate Go, I think exceptions are great and very ergonomic and I wish that language had not become so popular. However, a whole shitload of people apparently disagree, hence the popularity of Go and the acceptance of its (imo) terrible error handling. If developers don't have a problem with it in Go, I don't see why they'd have a problem with it in Bash. The error handling is identical to what I posted and the syntax is shockingly similar. You must unpack the return of a func in Go if you're going to assign, but you're totally free to just assign an err to _ in Go and be on your way, just like you can ignore errors in Bash. The objectively correct way to write Go is to handle every err that gets returned to you, either by doing something, or passing it up the stack (and possibly wrapping it). It's a bunch of bubbling up. My scripts end up being that way too. It's messy, but I've found it to be an incredibly reliable strategy. Plus, it's really easy for me to grep for a log message and get the exact line where I encountered an issue.
This is all just my opinion. I think this is one of those things where the best option is to just agree to disagree. I will admit that it irritates me to see blanket statements saying "your script is bad if you don't set -euo pipefail", but I'd be totally fine if more people made a measured recommendation like you did. I likely will never use set -e, but if it gets the bills paid for people then that's fine. I just think people need to be warned of the footguns.
EDIT: my autocorrect really wanted to fuck up this comment for some reason. Apologies if I have a dumb number of typos.
yeah fuck this, my soul crushing depression and ADHD are largely independent of my environment. I get that this is true for some people, but posts like these make me angry.