I understand you may want it to fall to the UN, but to the extent that it does it is merely a courtesy.
If someone wants to launch satellites with a radio violating every ITU regulation there is, unless someone is going to knock on their door with a gun, it doesn't mean squat. The buck stops at your nation's capital - if they're okay with what you're doing, you can do it. Everything else is just diplomatic window dressing and doesn't really mean anything at the end of the day.
For anyone interested in current data like this, Jonathan McDowell maintains GCAT which is a General Catalog of Artificial Space Objects (and does so fastidiously).
Toms Hardware usually includes a "Sustained Write Performance and Cache Recovery" test
The test measures the write cache speed and the time to the fall to the native NAND write speed. There are usually irregularities in the sustained write speeds as well.
The other test I've seen is based on writing and using up free space, SSD performance can drop off as the free space fills up and garbage collection efficiency goes down. I think this impacts random writes particularly
In the enterprise space, drives tend to keep more over provisioned NAND free to maintain more consistent performance. Very early on the SSD timeline, it was advisable to only allocate 80% of consumer drives if you were using them outside of desktops and expected the workload to fill them.
A playright-mcp server, or any bidi browser automation, should be equally capable of discovering/injecting and calling the same client JS exposed MCP-B site API?
It's like an OpenAPI definition but for JS/MCP? (outside of the extension to interact with that definition)
What are the advantages to pljs over plv8? I thought the context creation would have been the big one, but it doesn't appear so in the current benchmarks.
How did the project weigh the intermittent updates of bellard quickjs and the community fork quickjs-ng?
I too was surprised about the slower startup and am planning on spending a lot of time in the quickjs repo to try to improve it. Thankfully most use cases use a connection pooler, which removes startup costs from the equation, leaving conversion speed much more important. I was able to speed up conversion of jsonb by writing a custom conversion from jsonb to quickjs and back, but feel there is still a lot of room for improvements.
As for quickjs vs quickjs-ng: ng is a fantastic project and I’m really hoping it pulls an egcs and ends up canonical, but when this project was started, it did not exist, so quickjs was chosen as the starting point. As for why it has not been adopted yet by this project, it comes down to a few things that helped make the decision:
* quickjs is still having releases
* as learned from plv8, when there are constant changes it becomes much harder to maintain, so a steady target is easier to deal with (this is constantly being evaluated)
* the build system change from make to cmake adds friction to Postgres embedding, I already have to patch quickjs, and would need more complicated patches for quickjs-ng. I have a good working relationship with Ben Noordhuis, but it’s still a source of friction that isn’t needed now.
As things change, everything will be re-evaluated, but for now quickjs itself works great.
What's the motive "to gain trust and encourage users to use AI on WhatsApp"? Meta aren't a charity. You have to question their motives because their motive is to extract value out of their users who don't pay for a service, and I would say that whatsapp has proven to be a harder place to extract that value than their other ventures.
btw whatsapp implemented the signal protocol around 2016.
"motive is to extract value out of their users who don't pay for a service"
that is called a business.
if you find something deceitful in the business practice, that should certainly be called out and even prosecuted. I don't see why an effort to improve privacy has to get a skeptical treatment, because big business bad bla bla
The headers are seen by the monster-in-the-middle CDN.
It's obfuscation at best. I'm not sure the encrypted traffic will look particularly php-ish for example. Compressed formats might look vaguely passable.
I can't see any stenography code or libraries in the repo.
Then maybe the 4(+) countries that can field anti sat weapons beyond that.