Tables and/or spacer gifs.
Tables and/or spacer gifs.
Gee Louis, that reminds me of the time I lost my job after watching Family Guy for 48 hours straight
There was also a deleted verse where Judas shouted “IT WAS A PRANK BRO” to Jesus after he came back from the dead.
https://cuelang.org/. I deal with a lot of k8s at work, and I’ve grown to hate YAML for complex configuration. The extra guardrails that Cue provides are hugely helpful for large projects.
It all makes sense now. Spiderman 2 was an Italian conspiracy to stop anon from jerking off.
Just steal one. As long as you hide it well, they’ll never catch you.
You’re right, my bad
Bro’s whole world was shattered when he discovered Marika is trans
I can’t think of any possible problem with this. It’s flawless. Kudos to anon for discovering such a bulletproof plan.
If it’s a publicly-accessible repo, then immediately revoke the key and leave it. Force-pushing isn’t good enough because the old commit will still be tracked by Git until the garbage collector kicks in, and you don’t have control over the GC on GitHub (not sure about other providers).
If it’s an internal repo that’s only accessible by employees, then you probably should still revoke it, but you’ve got more leeway. Usually I’d create a ticket to revoke it when there’s time, unless this is particularly sensitive.
Please tell me the replies roasted the shit out of him
That’s not what I’m saying at all. I’m saying the rich and powerful have a vested interest in not taking risks that jeopardize their power and wealth, because they have more to lose.
The reason these models are being heavily censored is because big companies are hyper-sensitive to the reputational harm that comes from uncensored (or less-censored) models. This isn’t unique to AI; this same dynamic has played out countless times before. One example is content moderation on social media sites: big players like Facebook tend to be more heavy-handed about moderating than small players like Lemmy. The fact small players don’t need to worry so much about reputational harm is a significant competitive advantage, since it means they have more freedom to take risks, so this situation is probably temporary.
Unfortunately, retrofitting CSP on an existing site can be nightmare, especially if you have external dependencies. At my job, we spent months trying to enable CSP on one our oldest sites, but ultimately gave up because one of our dependencies won’t work unless we added “unsafe-inline” everywhere, which kinda defeats the whole point of CSP.
Can’t divide by zero, so it’s undefined. They exist in a quantum superposition of being a chad and a virgin