Why? Multi-tenant environments. First, we need to understand a few differences between environments:

• End-user UI
• Agent Runtime Environment
• LLM Server

So

• When you run Claude Code on your local MacBook, the first two are always local. The third is usually the Claude.ai server.
• When you ssh to a virtual private server (VPS) and install Claude Code there, the first two are your remote server. The third is still the Claude.ai server.
• When you run Claude RC on your virtual private server and code from your iPad using the Claude app, the end-user UI is on your iPad, the agent runtime environment is on your VPS, and the server is still Claude.ai.

Most people physically separate their tenancy, such as Claude Code, from their personal vs. work laptops. So in most cases, it's not a big deal.

But when you need multi-tenancy, it becomes super stressful. For example, say you have two different toolkits:

• personal toolkits (personal Notion, personal Sentry, personal Linear)
• workplace toolkits (company Notion, company Sentry, company Linear)

Most MCP auth states or code harnesses don't support profiles, so you can only log in to one.

So therefore... a natural evolution was to have both:

• a personal VPS with all personal toolkits set up
• a workplace VPS with all workspace toolkits set up

to physically isolate tenancies.

Now we've solved the multiple-profile issue, but the client's problems persist. Now let's get back to the environments:

• End-user UI
• Agent Runtime Environment
• LLM Server

All MCP auth or toolkit auth info should always be saved in the Agent Runtime Environment IMHO. However, a surprising number of harnesses tie them to the LLM server (such as Codex Apps or Claude.ai Plugins) or put them in the end-user UI (Claude Desktop or Codex Desktop).

Now the problem is:

• If the auth data is put on the LLM server, you cannot reuse LLM accounts across tenants
• If the auth data is put on the end-user UI, you cannot use the same app to access multi-tenants.

The only way to reliably isolate different auth information is thus:

• You ssh to a virtual private server (VPS) and run Claude Code there. Never use LLM server plugins.

Then

• End-user UI
• Agent Runtime Environment

are both isolated VPS, and

• LLM Server holds no information on the tenancy

This way, you can provide different toolkits, creating multiple dev environments.

Project Linguine is an initiative to define a deterministic list (i.e., the Linguine Recipe) to cover all linguistic Sprachraum. That is,

How many people around the world do not speak any of the languages defined in Linguine?

... should be near zero.

Candidates are...

• BCP 47
• Ethnologue 200
• DeepL
• Google Translate

Supporting Ethnologue 200 is too much. Also, for BCP 47, it's not only unfair but also excessive to translate for en-US, en-CA, and en-GB separately. So we agree that a linguistic Sprachraum should be simplified, yet considering variants like Taiwanese (zh-TW is different from zh-CN)

Do we still need to support i18n? It's an extra bunch of costs, not going to lie. But technology is in an exceptional stage, where people from all regions are flying to silicon valley for a better life. People seek information worldwide, and considering those, backfilling the data would be relatively easy. It's laying out fisher rods worldwide, with just an extra cost.

After looking into the subscriber lists of hn.cho.sh, I did notice that there are bogus subscriber lists. For example, I have no authentic Finnish subscribers. However, I want to keep the window open for international free minds to find the service. For example, I got an email from an Italian subscriber:

I found the service thanks to the advertisement in your extension of Bing Chat for All Browsers. This service is very innovative, and I especially love the fact that it is in my language. I will certainly share this news with my friends who are tech enthusiasts. The first time I visited the site, I had the amazing feeling of being catapulted into the kind of future I've always dreamed of but never seen realized. Thank you for providing such a fantastic experience! Make the web truly innovative!

The most important thing is to keep the net service profit, or net neutral at least. At this burn rate, we cannot continue the service.

DeepL vs Google Translate vs Bing Translate Offering Comparison

So, in conclusion:

1. Use the following list.

2. For Curated Newsletters, you cannot sign up for more than three locales. This is to prevent bogus subscribers.
3. As such, we will have zero subscribers for Finnish, for example, because we have yet to have an actual customer. We will still translate the top 3 articles for advertisement and the 'magical landing experience.'
4. There can be a button to request translation. Maybe this can be a pro feature?

While comparing offerings, I found that nb and no are both used in the Norwegian Langauge. Interesting.

230713

Linguine Engine Test Drive Result 2023-07-13