@Hubzilla Support Forum i would not mind to collect all the muting, ignoring and blocking in superblock and removing it from the contact interaction (or at least use the same backend). Not sure how well the addon will integrate with core. The current core ignore and block state is stored in abook. This data is usually already there for various other reasons. It can obviously only be used for connections. Siperblock uses pconfig IIRC. Maybe those can be combined in the superblock frontend?

I can imagine some sort of soft ignore (current superblock behaviour) and hard ignore (current contact ignore behaviour) and block (current contact block behaviour). Not sure what mute could be in this context. Maybe the current superblock behaviour could be named mute?