Conversation

Notices

1. Embed this notice
   feld (feld@bikeshed.party)'s status on Saturday, 17-Feb-2024 02:26:39 JST feld

   in reply to

   • :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:
   • Michael Downey 🇺🇳
   • Louis
   @selea @louis @downey @sheogorath how do you even determine if they have open registration? every ActivityPub server is going to do this differently and anyone can lie about it at whatever designated API endpoint we choose to use as the source of truth. Seems like an easy anti-spam check to evade.
   • Embed this notice
     :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse: (selea@social.linux.pizza)'s status on Saturday, 17-Feb-2024 02:26:41 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:

     in reply to

     • Michael Downey 🇺🇳
     • Louis

     @louis

     You where clear - suspend all instances that have open registration.
     Thats what you wrote.

     @downey @sheogorath

   • Embed this notice
     Louis (louis@emacs.ch)'s status on Saturday, 17-Feb-2024 02:26:42 JST Louis

     in reply to

     • :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:
     • Michael Downey 🇺🇳

     @selea Who said "nuke everything"? I'm sure you are aware that there are multiple levels of Federation. Such a feature wouldn't necessarily mean to suspend half of the Fediverse. It means that I have options based on the settings of a remote instance.

     To be more specific: "Don't accept more than X DMs per Y hours from instances which allow unapproved registrations" with the option to see those instances trying to send DMs and individually add them to an exception list. Same as the Moderation tools already there for the "Trending" section.

     @downey @sheogorath

   • Embed this notice
     :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse: (selea@social.linux.pizza)'s status on Saturday, 17-Feb-2024 02:26:43 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:

     in reply to

     • Michael Downey 🇺🇳
     • Louis

     @louis

     For being an open network like this, spam is relatively uncommon compared to twitter, or other social platforms.

     Deciding to nuke everything because of an instance decides to have open registration is just bad.

     @downey @sheogorath

   • Embed this notice
     :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse: (selea@social.linux.pizza)'s status on Saturday, 17-Feb-2024 02:26:45 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:

     in reply to

     • Michael Downey 🇺🇳
     • Louis

     @louis

     It is.
     You think it is a good solution to suspend ALL instances that have open registration during the time of the check being run.

     That will end up with you, being alone with a few single user instance in the whole network.

     Sure, you do you. But claiming that it is a good solution for the network is not great.

     @downey @sheogorath

   • Embed this notice
     Louis (louis@emacs.ch)'s status on Saturday, 17-Feb-2024 02:26:47 JST Louis

     in reply to

     • :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:
     • Michael Downey 🇺🇳

     @selea I don't think so. Fact is: almost all spam waves come either from mastodon.social or other instances that allow unapproved registrations.

     @downey @sheogorath

   • Embed this notice
     :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse: (selea@social.linux.pizza)'s status on Saturday, 17-Feb-2024 02:26:48 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:

     in reply to

     • Michael Downey 🇺🇳
     • Louis

     @louis

     What a dumb suggestion

     @downey @sheogorath

     feld likes this.
   • Embed this notice
     Louis (louis@emacs.ch)'s status on Saturday, 17-Feb-2024 02:26:49 JST Louis

     in reply to

     • Michael Downey 🇺🇳

     @downey @sheogorath A single feature would bring a lot of relief:

     "Automatically suspend federation from instances which allow unapproved registrations." Check. Done. Problem solved.

   • Embed this notice
     Michael Downey 🇺🇳 (downey@floss.social)'s status on Saturday, 17-Feb-2024 02:26:51 JST Michael Downey 🇺🇳

     @sheogorath BDFL

     feld likes this.