Looks like it doesn’t specifically but you can lock it down still.
https://www.perplexity.ai/search/how-to-configure-go-to-social-AZeSr5ilSRaqHCNOh9Qbmg
Looks like it doesn’t specifically but you can lock it down still.
https://www.perplexity.ai/search/how-to-configure-go-to-social-AZeSr5ilSRaqHCNOh9Qbmg
Does GtS not support relays? That’s what everyone uses to seed their new instances. I’m on a single user instance and have thousand of posts from hundreds of instances coming in daily.
This is not an airport. You don’t have to announce your departure. You can just leave.
You can’t just say blocked. It doesn’t work that way. #michaelscott
That’s the app I use. It is nice.
I just find the federated timeline a good way to find new people. Because everyone is stuffed onto the flagship instance, there’s prolly lots on the local timeline. But not so for smaller or newer instances.
A true poet!
This comment hurts my brain. There’s a lot more to the fediverse than a single app.
I recently had a Kona loaner with that. It was so dumb.
There’s an enforcement component. It’s designed to punish the producer so it hurts so it won’t do it again.
Many moons ago I used heartbeat for this, but you’d need both servers in the same cidr range. I assume that’s not the case here.
In your case you could probably use a dynamic DNS service to move the IP around, but the challenge would be knowing when to kick it off.
You could write scripts to determine when the live one goes down, but we’re probably already more complicated than you were looking for.
Federated DNA data storage service. My bad.
“Warez”. That’s a name I’ve not heard for a long time.