It's important to mention: they were compliant, because they trained the model at an AI hosting provider that had a partnership with Moonshot AI, but Moonshot didn't know Cursor was a customer.
My guess is: Pick a popular keyword from Google trends of which the Chinese company only released Chinese content and take the domain and put up English content.
I'm gonna ask something stupid, maybe: what is keeping you from having a minisplit in each room ? You don't have to run them the whole day. Just where you are going to be for a couple of hours.
My guess is: the cost of the minisplits, pretty certain if you had them and turned them all on, you could still draw that much power from the grid.
And probably you are underestimating the cost of nuclear anyway.
I think they are doing really well (by their own standards), the job is to destroy the government. They want to get rid of taxes and rules and regulations that prevent them from keeping their money and doing whatever they want.
Nobody cares about pirating, it's when the masses are able to do the pirating easily and get the content easily that is when things break down.
That is what DRM is about preventing.
If some knowledgeable people can copy it and put it low-fi on some competitor of Youtube and Google doesn't show in in search results. That isn't that bad. That means the general public won't easily find it.
I think Tor will get faster, now new protocols like TLS/1.3, HTTP/2 and QUIC are being developed.
Currently Tor looks like HTTPS done with TLS/1.2 on TCP (like regular HTTPS). As these newer protocols get more and more delpoyed Tor can start using them too which will help make Tor faster.
Well, Diffie-Hellman Key Exchange does something similar.
Create a key out of nowhere for 2 parties to boot strap communicate safely. (obviously Diffie-Hellman doesn't solve all problems like knowing who you are actually talking to)
Also notice how the plan is to push not only DNS entries but also TLS certificates:
"Right now, people are really keen to get HTTP/2 “out the door,” so a few more advanced (and experimental) features have been left out, such as pushing TLS certificates and DNS entries to the client — both to improve performance. HTTP/3 might include these, if experiments go well."
I think why Mozilla still doesn't want DNSSEC is because when it breaks it breaks in a big way. And DNSSEC still hasn't got their root key (ksk) rollover process in place. Which is something they would need to properly support to make sure nothing breaks.
On the transport front. Eventually I would expect them to use HTTP/2 over UDP/DTLS which is actually pretty darn efficient. It's the IETF standard based on Google QUIC. Which will probably be called QUIC. Because the IETF workgroup is called QUIC.