Erin Dickins 
@ajroach42 Is mstdn.social same as mastodon.social? I am a political activist and a musician. Do I need to move? If so what would you recommend.
May Louise@erindickins @ajroach42 Great question! And I would love to hear a bit more details about the moderation problems? I have no idea what is wrong.
Andrew (Television Executive)@MayLouise @erindickins as I said up thread, mstdn.social is not mastodon.social. These are different, but named similarly.
As for what happened? This was the latest incident, but not the first. This time, a post was removed for racism. The post in question was about not reading books by white guys.
It may have been a mistake, or the decision may be reverse, or the whole thing may have been faked (unlikely, but possible.) It's hard to say! But it's not the first time a thing like this has happened. That instance has too many people and not enough moderators.
@ajroach42 @erindickins Thank you for responding so thoroughly Andrew and also for shining a light on these issues. Appreciate it!
TakingOff@ajroach42 @MayLouise @erindickins The problem was that the post was about not reading books by white guys? Or the problem was that this post was removed? Or was the problem something else?
@erindickins mstdn.social is not the same as mastodon.social.
That bit is unreasonably confusing, and I wish it was easier.
mstdn.social and mastodon.social are unaffiliated as far as I'm aware.
You're fine, although you might be happier on another instance at some point in the future, or maybe you won't.
Thankfully, migrating between instances is pretty easy, should you decide to do so in the future.
@ajroach42 Thank you so much! I greatly appreciate your assistance. I’ll stay where I am for a while until things sort themselves out. I’m sure you’re all going nuts!
Scot Hacker@ajroach42 @erindickins Migrating is easy enough to do, but it’s a rude awakening when you realize that migrating does not actually migrate your existing content. It’s a huge disincentive for potential migrators. I hope mastodon is addressing this gap.
@ajroach42 @erindickins in fact, I’ll go further and say that it shouldn’t even be called “migration” until it includes your content. No where else in the tech world would we call a process that leaves your content behind a “migration.”
@shacker @ajroach42 True dat.
Marya@shacker @ajroach42 @erindickins agree! As I take a look at different servers, I regret that I’ll lose my first posts.
@emdot @ajroach42 @erindickins I agree, just make your choice and bite the bullet. Fortunately, we’re all pretty new here. And don’t have a lot of history to worry about losing.
Vidar Hokstad / Galaxy Bound@shacker @ajroach42 @erindickins There's an open issue about this, and the opposition to it has been that it makes "faking" your timeline easier. Weak argument IMHO as it's trivial to fake now (run your own instance and mess with the database). Simple solution is to label migrated posts. Slightly harder, but far better, is to implement signed, securely timestamped posts. Refusing to migrate posts is just silly.
@vidarh @ajroach42 @erindickins Interesting, thanks for the info. I hadn’t thought of the fakery aspectI am definitely in favor of doing it right, with proper signing. Just needs to be prioritized I guess.
Blondish@erindickins Thanks for asking this, Erin. The answer is what I hoped it would be!