![](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.
That’s if they know about it and have access to any of the accounts.
For example you can setup a domain.com account that’s almost completely anonymous.
Some form of compute with a recurring job that checks for a DNS address or domain.
Choose a domain that needs to be regularly paid for as a target.
Reason I would choose something you pay for as the trigger is because not paying a bill after your death is one thing that will be actioned on no matter what.
Exactly what I would have done !
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?
I feel like this is the answer to almost any case where many people hate on something.
Not sure if clever meta humor or wrong community XD
Not sure if clever meta humor or wrong community XD
Sorry this message didn’t make it.
Great read _
Definitely sending this to some of my friends who are stuck in this exact situation.
Fantastic _ Hopefully this can makeup for the lack of SMS support
I wonder if this iteration will end up being the iteration that finally becomes viable.
Started reading this thinking it was posted in the wrong sub but ended up inspired!
This is very true, pretty much exactly what enterprise code is.
What about envoy proxy?
Nothing else on the market has as low latency implications to workloads that I am aware of.