It’s not a person, doesn’t have any sort of social characteristics, so it doesn’t have a gender any more than a lamp with a very convincing fake beard.
Lamps aren’t female in French, they’re feminine but this is purely grammatical and doesn’t imply any social gender. It’s just part of the word - see “fleuve” and “rivière”, both words meaning river, one masculine one feminine.
We actually have a committe called "Mannanafnanefnd" which rougly translates to "Human name committee"and if you want to use a non-typical name for your child you have to apply for permission from them.
I’m all for being able to make your kid what you want, but I would definitely support a law in the US that stops you from being named these types of names that will get them bullied and picked on.
Whether it be Abcde or whatever the hell Ellon named his spawn, we could stand to have common sense naming laws to avoid the type of situation in this post going forward. And yes, I know it’s probably in the UK because it’s Daily Mail UK, but it’s a problem worldwide if you ask me.
Worse: X AE A-XII Musk (only named this because X Æ A-12 was not acceptable to California regulations due to having non-English characters both in the form of numbers and of Æ), and later, another named Exa Dark Sideræl Musk (nicknamed "Y"). Both of these were with Grimes. Both of these are the official names given to these children, that is what is written on their birth certificates.
However, they were also preceded by around 8 other children with different women given much more normal names, so it's unclear how much influence Grimes had on the decision making here. X AE A-XII in particular though I will definitely attribute to Elon because his fixation on the letter X extends back decades at this point.
The developers probably added a pretty detailed prompt to the backend that the AI uses whenever someone asks it to do this. If I was making an AI, I would not risk it spitting out something scary when given this prompt.
While cool, I am surprised this is considered noteworthy enough for an article. There’s so much experimentation constantly going on with these models, what makes this special? It’s more like the inspiration for a creepypasta.
I’m a pretty firm believer that Loab is a hoax “cryptid” due the unwillingness of the author to publish anything on the generation parameters. I think the author got one weird result from putting “Loab” in the negative prompt and then used img2img from there. Anyone who shows images of a “cryptid” they discovered but refuses to show proofs is untrustworthy in my opinion.
If I was in charge of one of these large AIs, I’d totally have it create the opposite of what OP got. I’d have it be some random eldritch horror creature any time anyone asks it to draw itself just for the fun of it.
Title: Unleashing the full potential of Swift Language - An unprecedented issue with an Array. “One More Thing”
Body: Ladies and Gentlemen, Developers of all Languages, this isn’t just another Stack Overflow question. This is a problem that I believe reflects the needs of our generation, and I need your expertise.
Here at Apple, we have been continuously striving for advancement, for intuitive functionality, for the fluid symbiosis of design and functionality that we’re known worldwide for. However, we hit a roadblock, a hurdle, one could say, attempting to harness the full power of the Swift language.
In the construction of SwiftUI Views, we’ve stumbled upon a peculiar problem, precisely in dealing with array manipulation. We’ve been using the Array structure to store different elements up until now. However, we have encountered a serious conundrum - modifying an array during a ForEach loop appears to be causing erratic behavior and crash.
Now, before I go any further, let me share the code we’ve been perplexed by:
This advanced piece of computer language, designed to remove the letter ‘b’ from our Array, is unexpectedly causing a runtime crash.
With your strong reputation for resolution and prowess in Swift language, I was hoping you could guide us in resolving this issue. As we all know, behind every limitation is a door to a new realm of possibilities.
And now, for that one more thing I promised…
In addition to the issue specified above, we are also facing a similar challenge within List where views are disappearing in the middle of a mutation, causing an ‘Index out of range’ error.
We’re looking forward to the solutions you, the Swift community, can bring to the table.
lemmy.ml
Oldest