![](https://lemmy.ml/pictrs/image/6af95a4f-27e9-45cb-a70d-41bd228eb44f.jpeg)
![](https://beehaw.org/pictrs/image/c0e83ceb-b7e5-41b4-9b76-bfd152dd8d00.png)
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 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.
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?
Sorry this message didn’t make it.
The magic of the bad server is they have an R&D budget plus ops team so some waste while testing is covered, you tend to pay for mistakes on the good (home) server :P
Plus getting feedback from a good team beats a rubber duck XD
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
Thnks for the info nugget! Really cool deep dive.
What about envoy proxy?
Nothing else on the market has as low latency implications to workloads that I am aware of.