![](https://lemmy.ml/pictrs/image/6af95a4f-27e9-45cb-a70d-41bd228eb44f.jpeg)
![](https://lemmy.ml/pictrs/image/ba912e85-f869-489d-baeb-5da9edecb532.png)
This is fantastic news!
This is fantastic news!
I am a bit confused by the status of that, I know Lemmy instances are already defedrating from meta so it must be part of it right?
I much prefer the Netherlands goverment approach where they host their own Mastodon instance.
Wild story thanks for sharing!
What’s the story behind how you got that?
Yes this would be amazing!
Very interesting indeed.
I guess a usecase like this easily slips past most developers due to lack of exposure :?
Is the need to respond as a separate entity so frequent that separate accounts for each entity would not be enough or is the user switching process too much friction?
As someone with senior experience in cloud engineering here is my input, naming things is hard.
And God forbid you decide down the line you need a sub domain the terror of having service-b.service-a.com give me the chills.
But yeah 100% naming thing is difficult so you end up naming it after the software and using the group as the parent domain
Lovely 🌹
Do you do anything to plan how and when everything gets used?
I always struggle with trying to pack my fridge according to consumption :/
And then sometimes you use a work server to design the pattern for the home server.
Great read _
Definitely sending this to some of my friends who are stuck in this exact situation.
Started with Evangelion Magi naming and now I just use the pet name generator in Terraform.
Fantastic _ Hopefully this can makeup for the lack of SMS support
What about envoy proxy?
Nothing else on the market has as low latency implications to workloads that I am aware of.