


SysAdmin
A chimpanzee and two trainees in a trench coat
It’s been a long road, but this issue is finally resolved.
We’re not opposed to hosting non-Star Trek communities as long as they adhere to instance guidelines, but before you move you should know that the federation gap with .world is closing and should be finally caught up before the end of the week.
Time for startrek.website/c/theymightbegiants?
No worries at all, we want to make sure we’re providing a fast and reliable (well, as fast and reliable as is possible with beta software at least!) experience. Like I said I don’t notice .world missing very much but that doesn’t mean we don’t realize the value their communities provide to the overall ecosystem.
Hey just want to update you on this, we made some changes that appear to be working. We’ve gone from 1.47 weeks behind to 1.42. You can see the recent change here.
Startrek.website has banned the user and blocked/purged the communities.
As ValueSubtracted said please report. Reporting alerts startrek.website admins and the admins of the user’s home instance. If we notice another instance regularly not cleaning out their trash, we have the option to defederate from them.