p_l

I remember their cheerful atmosphere about "geeks" getting pushed back down thanks to offshoring

Quite likely it exceeded that, some sensible numbers I've seen suggest between 800 to 1000 km/h final speed at impact

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.

Unless considerable amount of lobbying reverses it in a new directive/regulation, that's the case on model outputs - Originally I learnt of it from briefing prepared by lawyers regarding EU laws on AI.

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

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

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

Nodes get "NetMap" streamed to them from control plane, which contains information about nodes accessible to them. Without a node showing up in netmap, you can't start discovery to connect to that node - discovery protocol follows once you get information for given node, and allows continued connection in case NetMap gets stale (but if ACLs are changed and reach the other node, it's going to filter you out, and you're not going to know about it without initial info from NetMap)

... Because I had triggered more than one alarm recently messing with a headscale upgrade and permissions involved :D

String interpolation is a pox on the ecosystem, especially given how YAML was only originally a debug helper...