![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/c0e83ceb-b7e5-41b4-9b76-bfd152dd8d00.png)
Wait. I can automate my meetings too? I dig it.
Wait. I can automate my meetings too? I dig it.
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.
I had to read that again as I thought it was someone telling that to Oracle, which would make WAY more sense.
So I’ve heard they’ve been making some controversial decisions as of late but I’m out of the loop. What happened?
Ah, that’s a good point. I was thinking specifically within Lemmy apps, and not so much across the board.
I was just thinking that needs to become a feature. More technically minded folks could easily update the link on their own to plug into their Lemmy instance to subscribe, but for new users that could prove cumbersome.
I wonder if the functionality could be brought directly into clients.
I’m lucky in that my employer went the opposite direction. Downsizing our local office and just letting us all be 100% remote. We’re a geographically distributed group so it doesn’t make sense to enforce office requirements.