Similar to that jets effectively would be grounded the second that the US decides they would not be exportable to a former ally, my guess is that not many would, in this scenario, believe a former US owned AWS region in Europe to operate completely autonomously to the degree that it can be “easily” nationalized.
But long before that, I believe there will be other noticeable effects.
As someone working in a medium sized European company, with substantial investments across private infrastructures, AWS, GCP and some Azure, I can testify to that since last couple of weeks the Public Cloud Exit strategies around having services being prepared is a very hot topic. This concerns both existing services preparations as well as enforcing standards and configurations for new services.
Mosaic had support for XBM format prior to introducing color images. I did set up the Office of the Swedish Prime Minister around February-March of 1993, on a SUN SparcStation 1 if I remember correctly, running in a cabinet on a floor below the actual office on a 64kbps leased line. It was really a gopher site, but with that XBM support, albeit only black and white, found it useful to create an HTML “welcome” page to that gopher content of press releases, talks and articles.
Claude does seem to be explicitly blocking people living in GDPR jurisdictions to sign up. I don’t know what to make of that, but this statement from the first paragraph rings false.
That experience likely isn’t transferable to Siri, that has deeper problems. People, me included, are reporting their problems with Siri, e.g. setting it to transcribing what they and Siri says as text on the screen, and then are able to show that given input as “Please add milk to the shopping list” results in Siri responding “I do not understand what speaker you refer to.”, in writing.
Likely problems like these could be overcome, but preparing better input would probably not address the root cause of the problems with Siri.
I was happy seeing this news headline, as Twitter stopped accepting my TOTP after I successfully changed my password in December. I haven’t been able to log in since then, Authenticator step failing. Alas, it seems as if I missed the window; 2FA is now back being required.
Anywhere where you have payments related or any other PII data, then transitive dependencies, framework and language choices, memory sharing and other risks are taken into account as something that you as someone developing and operating a service is solely responsible for.
> We have no reason to believe that the exposed key was abused and took this action out of an abundance of caution.
This is not verifiable, right? As the authentication method has no public and required revocation source, and given that the key, if having leaked, likely will be acquired by an authoritarian government, they can selectively MITM organizations and users that are not aware of this blog post.
Bard opened to a US-only audience. For being the engine in applications that might propel an LLM ahead of the others, I fail to see that this would be advantageous for opening markets and greeting new customers.
As an example [of the contrary], I noticed Swedish Klarna among the partners that OpenAI revealed when announcing their plug-in API today.
>> I was reviewing GCP…
> Google is notoriously bad at this…
Do you mean Google or GCP? We don’t see complaints about AWS because Amazon closes Dash buttons or Spark, and also Azure is not seen in any worse light due to Microsoft discontinues Skype and what not.
Can we name one remotely popular service of GCP that has been shut down at all?
Their “Security Bulletin: Recommended Actions for LastPass Free, Premium, and Families” linked on this page is not available. Outage/overloaded? As a premium user, I got a popup in their app as well leading to this information page, but the actual information on suggested actions is not retrievable.