That depends on where your live (and when), but: Protest is the cornerstone of democracy and in general you shouldn't need permission to organize a demonstration.
I prefer voting. I find protests annoying. They're a good way for people to let off steam, hang out with friends, get photos for the international press etc. but they're not the right mechanism for finding out what the people want.
They're definitely effective when most of the country wants the government out, but by that point a vote would certainly do just as well, and with fewer flying bricks.
Protests can serve as an implied threat if the government is gaming the election process. They're certainly preferable to a riot or a coup attempt in that scenario.
They also serve to draw attention to issues that aren't showing up on the ballot for whatever reason. The system doesn't always work in an ideal way. To that end protests are supposed to be annoying to those who don't care.
Everyone prefers voting.. But to be able to vote, a vote must be happening. Protests are sometimes the only way to make a vote happen in the first place.
They are also a good communication tool for the world to see what the people are struggling with.
Name three currently existing democracies. USA is out (protests illegal), Europe is out (protests require registration which is denied for anything that has a risk of effecting change), the Middle East and Asia are out for obvious reasons. Maybe there's a democracy somewhere in Africa?
> I guess the Prius line was a popular “statement car” of the pre-Tesla era, though, like how Brian drives one on Family Guy, or the “Smug Alert” episode of South Park, but it was never that for me.
... So you admit to falling for Toyota product placement in cartoons.
Anybody who has ever run an internal pentest knows there's dozens of different ways to game-over an entire enterprise, and decisively resolving all of them in any organization running at scale is intractable. That's why it's called risk management, and not risk eradication.
Risk management is not my day job, but I'm aware of a cottage industry of enterprise services and appliances to map out, prevent and mitigate risks. Pentest are part of those as are keeping up with trends and literature.
So on the subject of something like Recall or Copilot what tools and policies does an it manager have at their disposal to prevent let's say unintentional data exfiltration or data poisoning?
(Added later:) How do I make those less likely to happen?
Essentially LLMs are recontextualizing their training data. So on one hand, one might argue that training is like a human reading books and then inference is like writing something novel, (partially) based on the reading experience. But the contract between humans considers it plagiarism when we recite some studied text and then claim it as your own. So for example, books attribute citations with footnotes.
With source code we used to either re-used a library as-is, in which case the license terms would apply OR write our own implementation from scratch. While this LLM recontextualization purports to be like the latter, it is sometimes evident that the original license or at least some attribution, comment or footnote should apply. If only to help with future legibility maintenance.
There is evidence that coal has worse environmental impact than other fossil fuels. For one, burning gas produces CO2 and water, whereas burning coal results in just CO2 (+ soot and other pollutants). Another is that (open) coal mines have devastating effects on large land areas.
So yes, best leave all fossil fuels where they are, but coal is especially bad.
The point that the article makes is about opening up NeXT to other hardware platforms. So while from one perspective, you might argue it lives on inside Apple, you could also argue that's where nextstep died.
In the early 2000s I worked for a company that went all in on NeXTSTEP a decade earlier. The product was developed in a "4 GL" called 4D or 4th dimension.
We had to do a painful migration to windows nt/xp because NeXTSTEP was discontinued and apple actively fought to kill attempts to fork or open source the code base.
For starts, wouldn't it be kind of ironic to set up limits and authorization in a context that is about making some content available to the public?
I'd say any technical or legal restrictions or possible means to enforce DRM ought to be disabled or absent from the media format used when disseminating content that must be disclosed.
Censorship (of necessary) should purge the data entirely,ie: replace by ###
Well, in video land there is patent pools. For example, you pay nominal fee to download specs from iso/ice 14496-12 to learn the details about BMFF and then pay mpeg-la a couple of dollars per device of it uses an AVC / h264 decoder.
These are open standards, but mpeg-la tries to recoup some of the research costs from "freeloaders".
Open source implementations like ffmpeg are a bit of a grey area,here
For now at least - for H.264 AVC, the patents are expired in most countries and most of the final US patents that may apply to AVC High profile will expire in the first half of 2026 [1].
Except in Brazil, where there are even MPEG-4 patents still in effect (expiring later in 2026) and the H.264 patents will last until the early 2030s, I think because of a rule that gave 10 years extra but is now changed but not retrospective for these patents [2].
reply