rschoultz

I distinctly remember, and found, the NeWS (Network extensible windowing sisten), where you could develop with PostScript(TM) for application windows.

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.

Developers worldwide have tested it…

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.

Indeed, and about their statement

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.

You might be right, though there is a vast difference between not supporting a language and actively barring access from different countries.

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?

And we had the “calling card” already with the `.plan` file, thank you very much.

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.

How unacceptable.

We are on Java 19 now. Several that spits out the same sentiment as you seem to be stuck with Java 8 and EE legacy projects from 2012.

Even credible news sources are bound to have an implicit bias, to a certain degree. There is, however, quite a few other types of media sources ranging from media bias, to fake news, misinformation, disinformation etc. I recommend reading the Cornell university library guides to learn about how to distinguish one from the other.

That's Sweden, its highly illegal to do trades while disconnected from the Nanny [State].

This sort of implies that cash registers must be connected online to the tax authority or some governmental function in order to operate. That is simply not true.

It is quite a stretch to begin thinking of a company as having turned evil because of that issue.

As a minor detail but nonetheless I think makes a difference, the name of the other language was "Go!", not "Go". That makes the similarity in line with C#, C, C--, C++ and F, F#, F* and several others. Yes in some cases these languages are inspired by the others and in some cases not.

who cannot compute what is the time in another place by adding 7 [...]

As someone who frequently talks to colleagues across timezones that are -9, -2, or +3.5 hours from me, where each of these have different dates for summer time, or don't have summer time, and meeting recurrences gets skewed etc, I don't see how asking about the current time off a location could be seen as "pretentious".

I don't think Geoff Huston argued for more CAs or a different distribution. His view is, in my experience, shared by many, regardless of nationality, though not as vocal. There are simply too many examples of compromised CAs, and the webpki system makes anyone vulnerable to the weakest of them.

I remember this. Yes, the web was in black and white for a few months, while Mosaic only supported XBM format.

It seems like you are right. On the company's pages I find "... Instead of doing this, Cloudflare will make the request from one of their own IP addresses near the user. This provides geolocation without tying it to a particular user. ".

Still, my concern is that this is no longer a function of the technology, but by a service that is maintained by one company, limited to the coverage that they provide in different parts of the world.

This feature will break dns-based geo-lookup, so as a user I might get directed to services that are 130ms away from me instead of 1-5ms. For any client application, this will likely have strong negative effects on user experience.

We had to move one end-user facing service from a proprietary (distributed) on-premise data centers solution running rented/hosted. We set up a number of criteria for evaluating cloud vendors as well as on-premise and semi-hybrid solutions. We had been following Kubernetes since some time back, and the platform had matured considerably, so we decided to continue our further cloud vendor evaluations by using Kubernetes.

At the end, the Kubernetes solution neutralized the choice of cloud vendor, at least from a software release and management point of view. From a security, availability, latency and a few other aspects the choice of cloud provider became less of an issue/equal challenge.

We have faced a few minor challenges when using Kubernetes. The knowledge barrier; The problem, as well as the beauty of Kubernetes, is that it takes on quite a comprehensive view of network management, service discovery, DNS management, deployments, container orchestrations, secrets management, system administration and much more. We use this as an opportunity for learning more than we see problems. But several roles (in the enterprise) need to come together on a pull request for a change, rather than having tickets and side projects. Switching to new features, like RBAC, TLS policy for AWS ELBs and generally keeping up with new features is another. The mostly excellent documentation has helped a lot.

Using Kubernetes, we noticed that latency of using the service was slashed to 50-80%, depending on the location of the end-user. This, however, we attributed more to the ability to roll out in more regions and auto-scaling. Of course k8s is not alone in supporting this, but it really comes out of the box.

A second effect we noticed was that by integrating the releases via Kubernetes, we reduced the time from the point of being ready in system test, to be passing our Release Readiness Check (yes we are an enterprise), and have user acceptance test environments and production environments being provisioned using about 15% of the manpower of our previous processes, and having releases being available in minutes and not in days (weeks), with enhanced visibility and maintainability. As an example, having the possibility to easy tear down or upgrade projects, with the right security and scale at all times (and no lingering volumes, load balancer pools or firewall rules)

For us, Kubernetes has brought a higher predictability of releases, and monitorability of the total solution. We did also switch a solution from one cloud provider to another, and might switch back. For the move we needed some labeling of services and management (referencing) of certificates.

Having built and used internationalised and localized applications for many years (answered no when asked by Netscape at the time whether I18n domain names were important), my advice is:

I18n, not that important. I.e. likely your target audience is familiar with English. L10n, more likely to be needed for the ability to use a service.

As a European user, I need at least: (1) Have weeks count as starting on Mondays. (2) Have ISO-8601 / rfc3339 date and timestamps. (3) Decimal point and (4) 1000 number separators localized, time zone indicators, (5) UTF-8 support.

Yes I remember that, and also http was on port 82 before it was assigned 80, if memory serves me right.

I reserved port 63 for whois++, that by the way rests fine where it is, in very few people's memories, during the same era. The motivation went something like 43 for whois protocol, 53 for ns, so 63 looks like evolution, though there were no aspirations to replace the name service protocol.

This will be incredibly useful, thanks for posting. Now I need to learn what the GNU Free Documentation License allows, how/if it can be reused or derived.

Certainly, in my experience and where I currently am, most of the texts that are published externally receives good editing, but many communications and documents are not, and 90% of the documentation is for internal purposes. This guide might just make the documentation a bit improved and more fun.

Also I appreciate the details about appropriate use of "$" or "#" for prompts, to name one. That is the way one would expect since at least the days with Bourne shell in the 80s, but I have not seen it spelled out.