![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Ah, neat! Yeah that would work then. I’d hope that your usernames are unique in your self-hosted setup, so that should work just fine. Very nice!
Ah, neat! Yeah that would work then. I’d hope that your usernames are unique in your self-hosted setup, so that should work just fine. Very nice!
Hmm…this should work but I do have a concern on it based on my experience with AWS. Maybe this is different with minio though.
In AWS, S3 bucket names are globally unique. Not just to your AWS account, but across ALL S3 buckets period. So let’s say you have a username of “test” and use that policy. If that user attempts to create a bucket and that bucket name is taken, well that user is out of luck.
Obviously if minio doesn’t require globally unique bucket names you’re probably fine, but otherwise this could realistically become a problem.
What makes that better is that VS Code is running on Electron, meaning it is running Chromium under the hood. Or at least part of it. Been a while since I read up on it so I can’t remember for certain.
I had to read that again as I thought it was someone telling that to Oracle, which would make WAY more sense.
I don’t know about you, but I was going to test to see how many human heads you could fit in one of the headsets at a time. We’ll see who’s laughing then!
Full disclosure: Haven’t read the article yet.
Working in corporate IT, this most likely is targeted toward enterprise customers who either take a long time to roll out OS upgrades or can’t due to technical limitations within their environment. In those cases, paying the cost of extended support is more palatable to troubleshooting or rushing mass OS upgrades. This is a fairly common practice with enterprise software vendors.
Edit: Okay, just skimmed it. Looks like this is actually a new program for non-enterprise consumers, which is interesting. First I’ve heard of that.