The Public Markets have rules and laws that incentivize very destructive and predatory behaviors. Corporations behave like psychopaths to hit quarterly numbers for 'fiduciary duty' laws.

Private assets don't have these so they can build real companies with an eye on the future.

But private companies don't have nearly as much access to capital because all the investment money goes into retirement because of stupid tax laws which goes into psychopathic public companies.

And then Blackrock / State Street / Vanguard collude to tell these companies how to behave socially and politically, often against the interests of everyone else in society.

Of course this could be done poorly but the idea has merit. Congress is most likely to screw it up, but who knows, maybe they won't.

That's peak optimism for 2026.

This is a weird situation.

If the license is changed it's no longer AGPL, it's a unique license.

If the license has restrictions then the copyright is violated by not adhering to the license.

The above makes it sound like both parties want to have it both ways.

I would just give the Russians proper attribution but the European governments hate Russia so much that they couldn't possibly do that. This is a problem with having governments run open source projects.

In the en it's probably going to be like Russian gas which they sanction except for not freezing to death in the winter, when they just look the other way and stay alive to hate the Russians another day.

The whole damn thing stems from some royal cousins hating each other in the 1830's. America was designed to "eff that noise" but every stupid American politician wants to act like a European so Americans get dragged into their stupid wars and other zero-sum games.

Open Source software is supposed to be a non-zero-sum game and the licenses are supposed to create the conditions for that. Maybe FSF should consider a v4 to improve the situation. Anybody seen Eben Moglen lately? Last I heard some whackadoodles at FSF were mad at him. Maybe a post-FSF license is needed.

"Play nice, children."

And now you know why the Mormons have their magic underwear.

Yeah, and even native stuff is super bloated now.

I noticed an instance of Brave with all of the features turned off sitting at a new tab page was using 230MB.

I remember doing OK with a version of Firefox that supported xhtml and JavaScript 2 that ran on a machine with 16MB of RAM total.

And the current browsing experience isn't somehow instantaneous on a CPU with 16x the cores running at 10x the clock. The user response time is about the same.

I think that browser itself ran in 4-8MB. Probably with the Flash plugin loaded too.

FWIW that old machine would take about 15 minutes to encode a 3 minute mp3 file and my current machines does it in about six seconds. So the hardware gains are real.

Maybe ML will actually be able to find some optimizations that are too cumbersome for humans to manage.

TFS says the vape would use Bluetooth to connect with the phone/app. The vape won't work w/o the app, so they'd build any extra functionality into the app, like ads, tracking and geo-fencing. See my other post Why stop there?

If the vape is going to be app-locked, then the app can be (a) tracked and (b) geo-fenced. Establishments/locations can post if they allow vaping and the (nanny) app can track where you are and disable the vape if it's prohibited. Marketing bonus: The app will probably be running a lot, so the data it could collect could be HUGE. /s

You people have gone insane.

Stop trying to control every atom of existence and every move people make.

You're sick in the head, not visionaries, not thought leaders.

Go plant a garden and get back in touch with the real world.

No, NOT FARMVILLE!

> genuine question - why was this code pushed now

Zuckerberg has aggressively been bribing politicians to enact this at the State level.

Several news stories about it though you have to search for terms like 'lobbying' and 'Meta' as fig leaves.

The problem you get though is what I call the "California Cancer Warning Problem"
Basically, people can only pay attention to so many warnings. The more often people get false or trivial warnings, warnings where they have to continue to get things done as standard, the more likely they are to just plain ignore the warnings.

While hackers might be able to figure out a way to do something malicious without triggering the warning, the warnings back then were worse than useless, because they not only triggered for just about every document, users by default could not assess the document for safety without enabling the scripting. IE I couldn't by default open the document and look at the scripts to assess them (and some of them were only like a dozen lines) without enabling them.

Saying the warnings were necessary also ignores that there have been exploits that didn't even require opening a document to cause infection. Preview was enough.

Basically, if the hackers figured out something clever, just add that to the check. It would still be a better situation than what we had back then.

The UK actually has a king, by design; the US not so much.

I’d argue that slavery wasn’t “legal because nobody banned it.” It was legal because there were explicit laws that created, defined, and enforced the institution.

There were statutes specifying who could be held as slaves, rules that the child of an enslaved woman was automatically a slave, procedures for manumission, regulations on how slaves could be bought, sold, punished, or inherited, and laws requiring that escaped slaves be returned. That’s not a legal vacuum, that’s a full legal framework.

It’s similar to how segregation laws later forced discrimination on people who might not have engaged in it otherwise. The state wasn’t passively allowing something; it was actively mandating and structuring it.

Slavery existed because the law built and maintained it, not because the law failed to forbid it.

I remember those days where it would warn if there was any scripting at all, rather than look for dangerous commands first.
Just as a thought, not bothering if the script cannot reach outside of the document itself. Functions that access other files or documents, email functionality, and such triggering the warning instead would have been more effective.

... as long as they don't store it in a Vatican basement. :-)

An exception is the Zeropatch technique where they dynamically update machine code of the OS in memory on the fly for folks who can't tolerate downtime.

It's certainly not common on unix systems.

Or an IoT device running a 2.6 kernel that is never going to be updated. :)

Did Dolby break any countermeasures of Snap's copyrighted code in what would appear to be a significant reverse-engineering effort to make this determination?

Or do they only have a suspicion?

This scenario reminds me of the SCO lawsuits when the progress of technology made that company obsolete.