Conversation

Notices

1. Embed this notice
   Pleroma-tan (kirby@lab.nyanide.com)'s status on Wednesday, 27-Mar-2024 14:29:33 JST Pleroma-tan

   • Christi Junior
   • Avatar of Chaos
   • Zergling_man
   • Owl! 🦉
   • Witch Hunter Siegfired
   @MK2boogaloo @Zergling_man @ChristiJunior @Witch_Hunter_Siegfired @lonelyowl13 that's unironically more preferable than shitting up this instance with a poor attempt at a dos because we are actively rejecting your spam attempts.
   • Embed this notice
     Pleroma-tan (kirby@lab.nyanide.com)'s status on Wednesday, 27-Mar-2024 14:31:42 JST Pleroma-tan

     in reply to

     • Christi Junior
     • Avatar of Chaos
     • Zergling_man
     • Owl! 🦉
     • Witch Hunter Siegfired
     @Zergling_man @lonelyowl13 @ChristiJunior @MK2boogaloo @Witch_Hunter_Siegfired are you finally going to stop spamming so I can turn the filter off?
   • Embed this notice
     Zergling_man (zergling_man@sacred.harpy.faith)'s status on Wednesday, 27-Mar-2024 14:31:43 JST Zergling_man

     in reply to

     • Christi Junior
     • Avatar of Chaos
     • Owl! 🦉
     • Witch Hunter Siegfired
     @kirby @Witch_Hunter_Siegfired @MK2boogaloo @ChristiJunior @lonelyowl13 If I wanted it to be a poor attempt at a dos I wouldn't have put a cooldown in. It's specifically designed to not encourage that sort of anti-spam measure, just to be annoying enough to make the target mute me.
     But whatever, if you want sysrq to keep seething, fine. I tried to fix it.