Conversation

Notices

1. Embed this notice
   ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Thursday, 06-Mar-2025 02:55:19 JST ✙ dcc :pedomustdie: :phear_slackware:

   • Lina Inver?e
   • 313Chris:hellokitty_headbang:
   • The MILF Messiah
   • 夜化
   • Sovereign Analysis
   • VIPPER
   • Vivi Nella Verita
   • Organa The ELF
   • Organa The ELF
   @verita84 @admin @lina @Yoruka @OrganaTheElf @VIPPER @Sovereign @elfgirl6789 @lunarised Because no one has spamed it so far* you must member what p did to smart crew
   what_the_fuck_are_these_people_talking_about.png
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Thursday, 06-Mar-2025 03:12:36 JST Phantasm

     in reply to

     • Lina Inver?e
     • 313Chris:hellokitty_headbang:
     • The MILF Messiah
     • 夜化
     • Sovereign Analysis
     • VIPPER
     • Vivi Nella Verita
     • Organa The ELF
     • Organa The ELF
     @dcc @admin @Yoruka @lina @OrganaTheElf @VIPPER @Sovereign @elfgirl6789 @verita84 @lunarised It doesn't spam when the same user blocks and immediately unblocks ad infinitum quickly, because the Block activity gets deleted and replaced with an Undo activity pointing to the blocking object. The other way of preventing spam is the 30 second sleep timer before sending a block message and the other 50 second sleep timer between block checks.
     
     How do you circumvent this? You just send blocks every ~2 minutes.
     mastofanpleromaenjoyer.png
     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Thursday, 06-Mar-2025 03:27:35 JST ✙ dcc :pedomustdie: :phear_slackware:

     in reply to

     • Lina Inver?e
     • 313Chris:hellokitty_headbang:
     • The MILF Messiah
     • Phantasm
     • 夜化
     • Sovereign Analysis
     • VIPPER
     • Vivi Nella Verita
     • Organa The ELF
     • Organa The ELF
     @phnt @admin @Yoruka @lina @OrganaTheElf @VIPPER @Sovereign @elfgirl6789 @verita84 @lunarised My point exactly
     Phantasm likes this.
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Thursday, 06-Mar-2025 03:42:35 JST Phantasm

     in reply to

     • Lina Inver?e
     • 313Chris:hellokitty_headbang:
     • The MILF Messiah
     • 夜化
     • Sovereign Analysis
     • VIPPER
     • Rock DJ :catcrunk: :gigachad: :lmde:
     • Vivi Nella Verita
     • Organa The ELF
     • Organa The ELF

     @dj @dcc @admin @Yoruka @lina @OrganaTheElf @VIPPER @Sovereign @elfgirl6789 @verita84 @lunarised

     rate limiting rules are not applied to mrf posts unlike those made by the toot client.

     What are you on about? The cachex based ratelimiter in the MRF doesn't create a post when the ratelimit gets hit and instead immediately lets the activity go through without processing it further.

     The code literally is

     with ..., true <- check_cache(...) do _processing here_ end {:ok, message}

     where check_cache returns false when ratelimit is reatched.

     The (un)block gets fulfilled, but the spammy notifs didn't get created. Did you even bother reading the MRF?

     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     Rock DJ :catcrunk: :gigachad: :lmde: (dj@ak.parcero.casa)'s status on Thursday, 06-Mar-2025 03:42:36 JST Rock DJ :catcrunk: :gigachad: :lmde:

     in reply to

     • Lina Inver?e
     • 313Chris:hellokitty_headbang:
     • The MILF Messiah
     • Phantasm
     • 夜化
     • Sovereign Analysis
     • VIPPER
     • Vivi Nella Verita
     • Organa The ELF
     • Organa The ELF
     @phnt @dcc @admin @Yoruka @lina @OrganaTheElf @VIPPER @Sovereign @elfgirl6789 @verita84 @lunarised
     If anything the mrf way of blocking is weaker because rate limiting rules are not applied to mrf posts unlike those made by the toot client.