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?
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
Same question, are they adding anything to the game?
What happens to the talent at these studios?
Are all these buyouts just a way to force hire workers.