Comment on @ Hubzilla Support Forum I’ve been experimenting a bit again and have com

jrp@hub.kliklak.net@hub.kliklak.net ⁨4⁩ ⁨days⁩ ago

• pepecyb@hub.hubzilla.hu@hub.hubzilla.hu ⁨4⁩ ⁨days⁩ ago

  @*_jߍyrope
  
  That’s exactly what I wrote. A superblock is a ‘supermute’ when applied to connections. But a Superblock is a ‘Superblock’ when applied to external channels. That’s why it would make sense not to display the Superblock menu item in Connections, or to extend Superblock so that, when applied to Connections, it also blocks or unblocks those channels within the Connections.
  
  As it stands, it’s a bit confusing for the user, although I myself would never think of blocking a connection with Superblock, as that’s precisely what the function in the ‘Connections’ section is for. In my view, the most sensible approach would be to hide the Superblock menu item for channels you’re connected to. After all, Superblock exists precisely so that you can block third-party channels (with which you have no connection), which isn’t possible with the connection block. I don’t think implementing the menu suppression would be too complicated either.
  
  @Harald Eilertsen

  original

  • mario@hub.somaton.com ⁨4⁩ ⁨days⁩ ago

    @Der Pepe (Hubzilla) ⁂ i think you are missing out on the fact that superblock is not invasive while the contact ignore and block are. Superblock just hides content for you. Undoing superblock will let you see all messages again. Ignore will stop storing content for you and block will even stop sending content. Unignoring or unblocking will not bring the missed content back. So those are completely different usecases. I am fine with controlling them all from the same place but i do not think it makes sense to exempt connections from superblock.

    original

    • pepecyb@hub.hubzilla.hu@hub.hubzilla.hu ⁨4⁩ ⁨days⁩ ago

      @Mario Vavti In that case, it would make sense to rename the add-on to ‘Supermute’ and change the menu option to ‘Mute from channel’.
      
      Perhaps, however, when it concerns connections, the menu could be expanded to include ‘Ignore’ and ‘Block’ to avoid having to go via the ‘Edit connection’ editor (although I don’t actually find that route particularly cumbersome).
      
      @Harald Eilertsen

      original

      • harald@hub.volse.no@hub.volse.no ⁨4⁩ ⁨days⁩ ago

        @Der Pepe (Hubzilla) ⁂
        

        In that case, it would make sense to rename the add-on to ‘Supermute’ and change the menu option to ‘Mute from channel’.

        
        How about just "Mute"?
        
        Adding "Ignore" and "Block" to the menu items of connected channels is trivial. Adding the same expiration feature that Superblock now has is also doable. If we move all this functionality to Superblock, it would almost come by itself. (I think...)
        
        The question is: Do we really need all three options? "Mute", "Ignore" and "Block"? Or would it be enough with just "Ignore" and "Block"?
        
        Do we really want that posts and interactions posted while "muted" should reappear when the mute expires?

        original

        • -> View More Comments
• harald@hub.volse.no@hub.volse.no ⁨4⁩ ⁨days⁩ ago

  @*_jߍyrope
  

  To me, a block is a block. That means i don't see their content, and they don't see mine.
  
  Whereas a mute would let them see my posts and eventually even let them like & comment, however i wouldn't see any of their posts.

  
  I'm open to change how we name things if that can make it less confusing. Exactly what the names will be is less important as long as we agree on, and can describe how the different features work and fit together :)

  original