Maybe they should consider rebranding, then. The word comes from Tolkein's Lord of the Rings series - the palantir were telepathic communication devices which were often used to deceive others by showing selective truths and lies of omission.
Many schools of thought believe that it is impossible to prove the absence of something. Personally, I would like some firm proof that there are no pixies living in my garden, but all I can say is that I've never seen one.
If a court determines that their behavior is illegal, this argument sounds a lot like: "Let us break the law, because someone else is doing much worse."
If it is necessary to reform how we handle copyright and IP licensing to remain competitive, we should find ways to do that.
The law should apply equally to everyone, whether they are competing with Chinese companies or not.
Does it sound elitist to say that maybe a small barrier to entry could make for better quality social networks? Especially if the tradeoff was giving users more creative control over their spaces?
I guess you wouldn't get billions in ad revenue that way, but your expenses could be miniscule, and isn't it possible that a rapacious profit motive is part of the core problem with Meta, Twitter, & co?
Or are there really too few people in the world who could figure out how to log into a <$5/mo cloud VM?
Is it really too much to ask for people to host their own content on a cheap VPS?
Wouldn't that neatly solve the content moderation problem? You register your server on an index or two, and you choose what your server will publish and accept. Each user would be responsible for finding a hosting provider who doesn't have a problem with what you post, and problematic content reports would go right to the hosting providers. The indexers could basically be DNS for usernames.
The AWS free tier would cover 99% of people, and between VNC and web UIs, you wouldn't necessarily need them to ever touch a shell. Plus, requiring a reasonably consistent public IP address would help to cut down on bulk spam.
It's easier to get good results by generating 2-8 images for each prompt, picking the best result, using that as the starting point for a new run.
Tweak the parameters of how close the new image should be to the old one and the prompts, tweak the prompts to address problem areas in the image, generate another 2-8. Rinse and repeat until you have something decent.
I doubt that the really impressive SD images are coming from submitting a prompt once and taking that output. It's better than past open-source efforts like the mini dall-es, but it also still has a way to go before it can reliably produce good results on its own.
AI art on products is an interesting idea, but personally I would use a more fully-featued SD web UI to generate the image locally.
It would be a return to the norm. Parents used to warn teenagers not to give out any personal information online. Using someone's real name in a public online setting was considered gauche.
Maybe a generation or two of dredging up digital sins will get us there.
Look, if you set up a permanent account on a pseudonymous forum, you are essentially linking it to your real identity.
Your writing voice, anecdotes from your life, what topics you understand and are interested in, it all comes together with enough time.
Not everybody wants to be bothered with all of that. Doesn't mean they're bots. It's worrying how often people assume that disagreement is necessarily inauthentic.
I wish I had learned earlier that when somebody makes an accusatory statement, it is wise to consider that they may be inadvertently projecting their self and their intentions onto the people around them.
It is very human to believe that most people think and feel in more or less the same way. So when we hear generalized statements about what people are like, or how they would likely react to a course of action, the sentiment will often be biased by how the speaker thinks, or would react.
I suppose a leak would be serious, but presumably these sorts of large-scale batteries would be buried in a containment unit.
Flywheel batteries are usually placed in small bunkers, because the failure mode of a giant rapidly-spinning concrete wheel jumping its bearings is not exactly pretty. Dams are usually designed with diversion channels and mechanisms to limit the damage if they burst. Etc.
Really, it's strange that we are so cavalier about lithium battery failures compared to the other sorts.
"Mechanical batteries" are a thing, like flywheels or hydroelectric reservoirs. Batteries store energy, the electricity that flows in and out is just one way to manifest that energy. You could measure it in Joules rather than Watt-hours.
At the end of the day, a chemical battery is a reusable bomb that is designed to go off very, very slowly.
It's the license that matters, not whether the code is visible on Microsoft's website.
Code which anybody can view is called "source available". You aren't necessarily allowed to use the code, but some companies will let their customers see what is going on so they can better integrate the code, understand performance implications, debug and fix unexpected issues, etc. The customers would probably face significant legal risks if they took that code and started to sell it.
"Open source" code implies permission to re-use the code, but there is still some nuance. Some open-source licenses come with almost no restrictions, but others include limiting clauses. The GPL, for example, is "viral": anybody who uses GPL code in a project must also provide that project's source code on request.
What do you think the chances are that Microsoft would surrender the Copilot codebase upon receipt of a GPL request?
Asking somebody to prove that a computer won't do X is a fool's errand, outside of some shrinking safety-critical industries.
That said, you could always make your own smart speaker with a hardware button or shell script instead of a wakeword:
https://developer.amazon.com/en-US/docs/alexa/alexa-smart-sc...