> CF could have kept coasting on what Astro was building, but instead they are paying for it. But in return they get a lot of control.
Supabase pioneered the modern implementation of this model. Probably, RedHat before it? Google also tend to "acquihire" maintainers of popular FOSS projects, like Ben Goodger (Firefox), Scott Remnant (Upstart), Junio Hamano (Git), Guido von Rossum (Python).
TFA is missing a host of many a popular isolation techniques like Isolates, Code Interp / Binary Translators [0], Enclaves, Exclaves, Domains/Worlds, (RISC V) SEEs, TEEs, SEs, HSMs, pKVMs ...
> as the CLOUD Act "gives the US government authority to obtain digital data
AWS maintains a similar stance, too [0]?
The CLOUD Act clarified that if a service provider is compelled to produce data under one of the limited exceptions, such as a search warrant for content data, the data to be produced can include data stored in the U.S. or outside the U.S.
> Microsoft admitted that it 'cannot guarantee' data sovereignty
Hm. As for AWS, they say that if the customer sets up proper security boundaries [0], they'll ensure will keep their end of the bargain [2][3]:
As part of the technical design, access to the AWS European Sovereign Cloud physical infrastructure and logical system is managed by Qualified AWS European Sovereign Cloud Staff and can only be granted to Qualified AWS European Sovereign Cloud Staff located in the EU. AWS European Sovereign Cloud-restricted data will not be accessible, including to AWS employees, from outside the EU.
All computing on Amazon Elastic Compute Cloud (Amazon EC2) in the AWS European Sovereign Cloud will run on the Nitro System, which eliminates any mechanisms for AWS employees to access customer data on EC2. An independent third party (the UK-based NCC Group) completed a design review confirming the security controls of the Nitro System (“As a matter of design, NCC Group found no gaps in the Nitro System that would compromise these security claims”), and AWS updated its service terms to assure customers “there are no technical means or APIs available to AWS personnel to read, copy, extract, modify, or otherwise access” customer content on the EC2 Nitro System.
Customers also have additional mechanisms to prevent access to their data using cryptography. AWS provides advanced encryption, key management services, and hardware security modules that customers can use to protect their content further. Customers have a range of options to encrypt data in transit and at rest, including options to bring their own keys and use external key stores. Encrypted content is rendered useless without the applicable decryption keys.
The AWS European Sovereign Cloud will also benefit from AWS transparency protections over data movement. We commit in the AWS Service Terms that access to the EC2 Nitro System APIs is "always logged, and always requires authentication and authorization." The AWS European Sovereign Cloud also offers immutable, validated logs that make it impossible to modify, delete, or forge AWS CloudTrail log files without detection.
Definitely there exist customers one must fire, but the flip side is, some of them might have genuine complaints.
... an extremely popular marketing tool ... sending an equally excessive amount of data above what they were paying for. They were far less adamant about the product, and on some days I didn't even want them as a customer. If there was a minor blip in the service, they were the first to complain. Reminder, [Sentry] was still a side project at the time so I had a day-job. That meant it was often stressful for Chris and I to deal w/ customer support, and way more stressful dealing with outages.
We had one customer who loved the product, and one who didn't. Both of these customers had such extreme volumes of data that it had a tangible infrastructure cost associated with hosting them. We knew the best thing to do was to find a way to be able to charge them more money for the amount of data they sent. So we set off to build that and then followed up with each customer.
To our surprise, the customer that loved the product didn't want to pay more. The customer who was constantly complaining immediately jumped on the opportunity. What's the lesson to take away from this?
... when I was a teenager I worked at Burger King, and there was an anecdote I will never forget: for every customer that complains, there are nine more with a similar experience. I've cemented this in my philosophy around development, to the point where I now believe over rotating on negative feedback is actually just biasing towards the customers who truly see the value in what you're offering. The customer that was complaining really valued our product, whereas the customer that was happy was simply content.
> I agree with the sentiment, but unfortunately often this is too simplistic. For example, a lot of Palestinians are not tolerant towards LGPT people -> a lot of LGPT people are not tolerant towards Israelis -> a lot of Israelis are not tolerant towards Palestinians.
Nice bait with broad sweeping generalizations there.
One of critiques of "Paradox of Tolerance" is its proponents (probably not Karl Popper himself) take the argument to its extremes (similar to the generalization you posit), while the reality is more of a spectrum.
I didn't intend it to be bait. It is a generalization, but if you read carefully, there is "a lot" at each point.
And pretending that there aren't large swaths of people who have different ideas and you can group them into "tolerant" and "none tolerant" is also a generalization.
Yes, I think of “paradox of tolerance” as a sort of glib rebuttal people give when enjoined to tolerate someone.
“Fuck you, that person is intolerant, I get to do whatever I want to them. And man, how uncultured are you that you would even suggest otherwise. You must never have heard of this philosopher!”
> Gemini pointed me back at MY OWN comment, above, an hour after I wrote it. So Google is crawling the web FAST. It also pointed to: https://learning.acm.org/bytecast/ep78-russ-cox ... I had ChatGPT regurgitate my HN comment (without linking to it) about 15 minutes after posting it.
Sounds like HN is the kind of place for effective & effortless "Answer Engine Optimization".
Supabase pioneered the modern implementation of this model. Probably, RedHat before it? Google also tend to "acquihire" maintainers of popular FOSS projects, like Ben Goodger (Firefox), Scott Remnant (Upstart), Junio Hamano (Git), Guido von Rossum (Python).
reply