Comment on @ Hubzilla Support Forum I’ve been experimenting a bit again and have com
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
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
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
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?
Personally, I don’t need a mute function that brings back the posts that were previously hidden once the mute is lifted.
It doesn’t really seem necessary either, because when you mute something, you do so for good reasons… you don’t want to see those posts. If you lift the mute, most users will simply assume that applies going forward.
Ultimately, therefore, an ‘Ignore’ and a ‘Block’ option would be entirely sufficient, provided they can also be applied to third-party channels and the lists can be managed via the add-on.
@Mario Vavti