- 4 points
- Nerdsniped: You're describing a IEC 60320 C13 cable - they're technically only spec'd for 10A, which means you're looking at ~1200W, not 1800.
(However, UL will list them for the full 15A -> 1800W, and I'm sure plenty carry that. And for that matter, I suppose you can get twice that in Europe on 240v...)
- In this case? Not that I know of, but I'm not following closely.
In general? Absolutely - search 'Operation Chokepoint'.
There's a great summary in the middle of this (very long) article under that header: https://www.bitsaboutmoney.com/archive/debanking-and-debunki...
- AWS is doing that: https://www.aboutamazon.eu/news/aws/built-operated-controlle...
- Yes. All CAs trusted by browsers have to go through WebTRUST or ETSI audits by accredited auditors.
See https://www.mozilla.org/en-US/about/governance/policies/secu... and https://www.ccadb.org/auditors and https://www.ccadb.org/policy#51-audit-statement-content
- > There is absolutely no company-wide mandate to use GenAI.
There is an STeam goal for adoption and usage. There is a QS dashboard for SDMs to see statistics on their org's adoption and abandonment rates. There is BT guidance being propagated out to VPs and directors on how to roll out programs. As placardloop said, there was a mandatory OP1 FAQ question on GenAI usage.
- Between this and https://www.haproxy.com/blog/state-of-ssl-stacks, I think we need to start accepting the idea that OpenSSL is not the right way forward for anything performance sensitive.
Given how aws-lc powers both of these articles, I'm curious how Rustls compares to s2n-tls - AWS's TLS library to go along with aws-lc.
- They claimed that studio wouldn't need connect.
I don't know AGPL well enough to know if a plugin is considered a derived work but it sure seems to imply it:
> For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
- What I don't get...BambuSlicer is open source. And, not only is it open source, it's a fork of PrussaSlicer, so Bambu doesn't have the ability to re-license it.
It's licensed under the Affero GPL which is very strict about the licensing of derived works. That license requires Bambu to include the source code to any additions they make, including all of the logic, keys, etc. that they're baking into any binary distributions. If they don't, they're violating the copyright rights of Prussa and many others.
So, either Bambu has to open source all of this, which defeats the purpose (given that it's already leaked, that's gonna happen anyway) or they have to route everything through a separate program for their own slicer.
- 4 points
But since they own equity in the current company, you can give them a ton of money by buying out that equity/paying acquisition bonuses that are conditional on staying for specific amounts of time, etc. And your current staff doesn't feel left out because "it's an acquisition" the way they would if you just paid some engineers 10x or 100x what you pay them.