Wait how is what you’re proposing different from ICE hybrids?
Wait how is what you’re proposing different from ICE hybrids?
the religion that gets you the most stuff in the afterlife.
I think it would be rather the opposite, should be the one that promises the worst fate in the afterlife to non-believers
I’m confused on how to read that hashtag. Anti-kings are losers? Anti-“kings are losers”?
It’s a new-ish term, I believe. Trying to get away from the notion that the trans experience is all negative things
I was thinking of an approach based on cryptographic signatures. If all images that come from a certain AI model are signed with a digital certificate, you can tamper with metadata all you want, you’re not gonna be able to produce the correct signature to add to an image unless you have access to the certificate’s private key. This technology has been around for ages and is used in every web browser and would be pretty simple to implement.
The only weak point with this approach would be that it relies on the private key not being publicly accessible, which makes this a lot harder or maybe even impossible to implement for open source models that anyone can run on their own hardware. But then again, at least for what we’re talking about here, the goal wouldn’t need to be a system covering every model, just one that makes at least a couple models safe to use for this specific purpose.
I guess the more practical question is whether this would be helpful for any other use case. Because if not, I hardly doubt it’s gonna be implemented. Nobody is gonna want the PR nightmare of building a feature with no other purpose than to help pedophiles generate stuff to get off to “safely”, no matter how well intentioned
Yeah but the point is you can’t easily add it to any picture you want (if it’s implemented well), thus providing a way to prove that the pictures were created using AI and no harm has been done to children in their creation. It would be a valid solution to the “easy to hide actual CSAM between AI generated pictures” problem.
I think that’s a general steam feature by now, not exclusive to the steam deck!
I can get behind that
Ohh the “what time is it in films” argument is good, haven’t heard that one before, thanks
It’s gonna get much worse when you start to try mapping days of the week onto the new times. Are days gonna be the same everywhere as well, to stay from 0 to 24? If so, have fun saying things like “Let’s find a time on Wednesday/Thursday”. People likely couldn’t be bothered and would probably just use the day that their normal wake-up time falls on to mean the full solar day instead. At which point you could also just say okay, weekdays are still following local solar days. But now what weekday is it halfway around the world? Now you need to look up their solar day.
All this to say - abolishing time zones will introduce the reverse problem for every problem that it seemingly solves. You can’t change the fact that our planet rotates and people in different locations will follow different schedules. Turning the lookup-table upside down is just a cosmetic change that doesn’t remove the situation that’s causing the confusion. I’d rather just stick with the set of problems that we’re already used to dealing with.
Yup, you got it. Even the solution to your confusion. Good encryption algorithms are set up so that even the smallest possible change in the input (a single flipped bit) will produce a completely different result. So yeah, if you have just a small set of exact possible messages that could be sent, you can find out which one it was by encrypting it yourself and comparing your result to what was sent. But there is a super easy protection against this - just add some random data to the end of the message before encrypting it. The more, the harder it will be to crack.
Exactly that! KISS is an often cited rule among software devs.
It’s easier to understand, easier to review for correctness, and less likely to cause problems with additional changes in the future. Even though it sounds counterintuitive, software developers generally try to write as little code as possible. Any code you write is a potential liability that has to be maintained, so if you can instead just call code that others have already written and that has been tested, you’ll want to do that. (Note that “less code” doesn’t mean fewer lines of code, it means less logical complexity, which is often, but not always, also less in terms of characters/lines)
Using YearMonth.atEndOfMonth would have been the easier choice there, I think
Looks very much like it! I’m a bit jealous, they were already out of stock when I looked at getting one
There are some cases though where the code is just complicated for reasons outside of your control, in which case “what” comments are good - but they should never be taken at face value, but only used as a first step in understanding the code. There’s a significant risk of the code not actually doing what the comment says.
You’re right that words can be coined and their usage changed, but you seem to be misinformed about how that happens. You just deciding we’re gonna do it this way now in a random thread on lemmy is not gonna cut it, sorry
Gotcha, thanks for explaining!