Yes, I'm sure children in poor countries who may or may not read English are desperate to get ahold of, say, an obscure 1993 book on VCR repair.
These are books that are unsold for a reason.
It's a testament to the interplay of words that forms the tapestry we call language!
But leaving out a comma can certainly make sentences more fun
Anyway, let's eat Grandma.
Companies should, in general, avoid keeping any user data one second longer than they legitimately need it. Data should be viewed as a liability more than an asset, and every company that achieves significant scale with user data soon realizes this, though some take longer than others to learn the lesson.
The reason it's a liability is because it exposes the company to an endless stream of warrants and subpoenas, and contrary to popular belief, the government does not pay for that data. In some cases the government might pay a portion of the expenses the company incurs in responding, but it's always still a net loss, and most of the time the government just shows up with a court order and says "Hand it over or be held in contempt of court". What makes it even worse is if companies actually want to be good stewards of the data and not hand over more than they should, they'll often get overly-broad requests and then have to go to court to fight to narrow or quash the requests.
This all gets very expensive. It's just a cost of doing business... but it's a cost that can be avoided if you don't have and can't get the data.
Encrypt everything, and arrange to destroy the keys when you no longer need the data is the best way to do it, too. Scrubbing large databases quickly and effectively is hard. Deleting a set of AES keys is a lot easier. This also means that you can focus your internal access controls on controlling which systems and employees can get the keys.
I'd encourage Ring to find ways to close the window of access even more.
....are books that they can buy by the meter, for pennies on the dollar, if that much. These are surplus books that publishers - the world's leading destroyers of books - would have to destroy anyway.
Trainers can't afford to buy actually rare, desirable books.
It's a shame that all of this data is locked up on private servers, but that's really more of a problem of the copyright system than anything else. Anyone who scanned these books would be banned from making it public.
Why, what's the hurry?
Probably worried about competition from Tesla's Robotaxis.
The quote was from the Bavarian government guy, so it seems unlikely that he's concerned about Waymo's competitive worries.
Also, German regulators are very cautious, so I expect Tesla's camera-only and less-mature robotaxi service will have a harder time getting approved.
Now we need to move quickly from testing to real-world deployment.
Really? That is a need? Why, what's the hurry?
You know another company that moved really quickly from testing to real-world deployment? OceanGate.
Well, given that Waymo has been testing for nearly 20 years and been operating commercially for six years, currently operating nearly 4000 vehicles in 11 cities doing 500k rides per week... there's not a lot of risk.
Roads in Munich aren't terribly different from roads in US cities. Stoplights work a little differently. Munich does get a little snow, but rarely very much and it almost never lasts long. If Waymo's vehicles can't deal with it they may just suspend service... though I expect they'll probably handle it fine. They're supposed to go live in Detroit and Minneapolis this year, and if they can handle the weather there (where just shutting down for snow is not an option), Munich will be no problem at all.
So, not much like OceanGate.
Notarization is Apple's strict code signing process, which makes it hard for non paying and anonymous developers to distribute third party Mac software. Linux lets you run unsigned software without compromise.
Thanks for the definition.
So far, I've not run into a problem with this....
And with specific regard to my local AI and OpenClaw experiments and tools required for that....haven't run into a problem at all yet.
So, not a barrier of merit.
That execution is the recording engineer's job. Dre is mostly a producer now, and that does require considerable talent and creativity. Depending on the situation, they may do everything except write and sing the lyrics.
The recording engineer only records (and maybe mixes) the audio that is generated, which is part of what I meant by "mechanical process", along with generating the audio. Dre could use AI to transform his ideas into digital audio tracks, obviating the recording engineer and the performers, and to then select and mold the results. This would still require talent and creativity, which was my point.
Especially with AI and ARM64 server development. Having to go through brew, containers and Apple's notarization process makes MacOS not a serious platform compared to bare metal Linux. In a twist of fate it is MacOS that is not ready for the AI desktop. Asahi is stuck on M1 and M2 so can't help you with M6 Macs.
Err...actually, OSX, so far in my experience is quite adapted to local AI.
Brew? What's wrong with that...pretty much the equivalent of of apt-get on some Linux installs, or whatever package manager you use there...
Docker is easy to run on Mac...actually it seems to give a bit more isolation they way it works on Mac...but set up is a breeze and while containerization is not required to run AI or OpenClaw on a Mac, it IS a good idea for security reasons to do so....Mac or Linux!!
Not familiar with any 'notarization" on my Mac set up, please explain?
OH...and running stuff on ollama, you get to take advantage of of the MLX framework for running local AI models....really speeds things along....
So, not quite sure why you are trying to say Macs aren't good for AI work....they actually are quite good for it AND I guess a bit more plug and play to get things set up and running.
And with any platform the more secure you make it, well that adds complexity, but it's worth it....I'd not want to turn OpenClaw or the like free on any platform without guard rails....
They were not in any way the same company
This is, of course, capitalism-worshiping nonsense. Corporations are legal fictions. Having bought one, you have become the owner of the entire fiction, including the name. They are SCO now in every sense that matters, and I say that as someone who used to run SCO software and who knows several former SCO employees. That SCO is dead, hopefully this SCO can also die soon, but they are legally the same SCO.
Caldera didn't buy SCO.
"[Racism] is right twice per day" is the phrase that comes to mind.
Racism....where does that come into play with this?
I don't see anywhere where any specific race was targeted or any restrictions were based on skin color, creed or sex, etc.....it just says that H1B (which could be anyone in the world) would be more $$ to bring into the US.
You're really reaching on this one.
If I'm mistaken PLEASE cite and point out where this is meaded out by race in the exec order or rule....
The money is already earmarked to go to funding ICE and enforcement. Which, well, I'm not even sure how to word what that vibe is.
Hmm...how about:
Amazing!!
Fantastic!!
About fucking time...
Getting what I voted for...
Were you looking for something along those lines?
This is all moot because it's false that if you use AI you cannot gain copyright on the work. I literally hold a copyright registered with the US copyright office (I registered with them, despite not being a US citizen, because they're precedent-setting), fully disclosing the use of AI in the process, and directly speaking about the matter with a copyright examiner.
What the standard is is that raw, unfiltered outputs are not copyrightable (and even then, there's wiggle room; the argument put forward by the copyright office was "based on their current understanding" (as of several years ago) and presumed very minimal control by the user over the outputs (which was actually already obsolete by the time they put it out, but that's nitpicking)). But the human creative action you take with those outputs can cause the resultant product to be copyrightable. This can be things like sample mixing, mastering, adding vocals, etc, but can also even just be the selection process itself. Yes, assemblage, selection, curation, etc are all potentially copyrightable acts.
In my case, while the samples were (overwhelmingly) AI, the whole project was weeks of work, involving hundreds of generations, track splitting and reassembling, things down to the level of editing individual phonemes (or for example in one part, stripping the vocals and instruments from a sample down to just the residual "other" channel, throwing it into reverse, and then piling on progressively more reverb and volume up to a sudden cutoff to create a tension-point transition). No issues whatoever registering the copyright on it. I'm sure you could do far less and still have a copyrightable work.
The only person who always got his work done by Friday was Robinson Crusoe.
