p_l

Same here - just started to really get going with herdr not sure I want to worry about moving again

Unfortunately I can't link to IRL discussion with lawyer (wish it was so easy!)

We got guidance that:

a) weights should be considered to be public domain due to "blender" aspect of training on otherwise copyrighted data (similar argument as to why stable diffusion weights can't be infringing - because any specific copyrighted work provides less impact on process than RNG)

b) model outputs should be considered public domain as far as "work done by model" counts - prompts/inputs done by human are copyrightable.

However, model output can infringe - essentially same framework as if you used a ton of Disney stuff in a drawing you made by yourself - since the drawing would remain what it is without the copyrighted information, it is infringing even if you did it from memory.

Similarly any human-made addition to model output are copyrightable, but to make an useful distinction there would need to be some significant work. So let's say you made an image that incorporated model outputs for parts of it - going back to "prompts" it also counts if you made a sketch/wireframe/etc. and then used a model to "fill in" or postprocess it.

In EU especially it's already settled, afaik, as are direct model outputs

I guess it's also because the model is available to at least one group, and this releases embargo on information about it.

The point of the lower pricing is to move compute (and sysadmin) capacity around

Nah, Elon is well reported to have been crazy about "X.com" since ~2000 and thus it makes sense it got incorporated into SpaceX name

AFAIK they are all (Barium, Argon, Carbon) different checkpoints of the same (ongoing) training run

Arguably it's trivial to fix for most netbooting environments, the one iffy case would be corporate laptops configured to boot from net for management purposes because there "attacker controls the network and timing" suddenly can become easy

"Think" (thinkpad, thinkcentre, etc.) series have AFAIK completely different R&D team plus the whole aspect of building on top of what was done for earlier models, and on those the UEFI Capsule mechanism (which allows passing firmware updates from booted OS to firmware) works just fine - it's also used to ship firmware upgrade as part of Windows Update.

UEFI provides a way to update in OS agnostic way, unfortunately motherboard vendors do not necessarily provide archives that can be uploaded this way (assuming they updated to new enough version to support the interface in the first place).

Unfortunately we're suffering from "eh, it boots windows, ship it" mentality of many hardware manufacturers, whether back in horrible era of BIOS emulating faux IBM PC 5150, or with modern UEFI

No, by DPI. SSH has recognizable signature as does web sockets etc.

Takes flipping one switch for 443 to be made HTTPS + HTTP2 + websocket only by egress firewall if you paid for one with DPI

Have you seen the slopreport for the vulnerability?

I fully understand being carefully worded when you need serious brain power just to figure out every claim in the logorrhea

and includes AoE 2 :D

Reserving any judgement on the actual vulnerability or disclosure process - It was still very hard to read, and not because the topic was hard - the writing just sucked.