@*_jߍyrope There's probably some subleties that need to be ironed out, but from my understanding it more or less is.
Comment on @ Hubzilla Support Forum I’ve been experimenting a bit again and have com
@Der Pepe (Hubzilla) ⁂ Oh so Superblock should be called Supermute, right? In a way a Supermute is exactly what I am looking for, and it would be supercool, if it already were there! @Harald Eilertsen
harald@hub.volse.no@hub.volse.no 4 days ago
No, Supermute only works for existing connections (which isn’t what it’s designed for). It blocks external channels (I tried it out today).
A mute function for external channels would probably need to be implemented separately.
"2. If I set a Superblock on a connection, posts from that connection are no longer displayed in my stream. However, the Superblocked connection can still see my posts, including any subsequent ones." ?
I guess it is more complicated, than necessary ;)
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.
What do you think?
@Harald Eilertsen
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
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 :)