Crom, Kobold King @vahnj@awoo.space

@asonix@asonix.dog the d stands for "dammit"

@InspectorCaracal@tootplanet.space Yeah! If you need to clear out messages that snuck through, try this in the rails console:

Account.remote.where(suspended: true).each{|a| SuspendAccountService.new.call(a)}

@asonix@asonix.dog try:

sudo journalctl -u service-name.service

@ebeth@witches.town thanks!

@ebeth@witches.town can you repeat the warning for me? i want to watch it eventually

@Firstaide so pure~!!

@Elizafox Now That's What I Call Subtoot™

Hello! I want to let you all know I wrote a thread yesterday about navigating our situation with some usable tools to try to navigate this.

Maybe we're too far gone for this to be useful, but if this helps anybody navigate what's happening, that's a win for me.

https://awoo.space/@vahnj/2069298

#socialharm

@inurashii you too friend

Here's some very straightforward instructions if you're not intimately familiar with git (pff, like anyone is):

1. go to the base directory of your project
2. run "git fetch"
3. run "git cherry-pick b9d241c6f554570e0677d9354b27dad21322e341"

Then, the next time you update, make sure you run "git pull --rebase v1.#.#" so your git history doesn't get ruined compared to the official branch

There's a major issue in stock 1.6 that requires that you make some changes to ActivityPub, as suspended users' messages are not being properly rejected. This includes domain blocks.

To fix it, run git cherry-pick against this commit and restart:

https://github.com/tootsuite/mastodon/commit/b9d241c6f554570e0677d9354b27dad21322e341