When screening was first designed, the idea was to set-up network based account storage for the whitelist by using the mute and follow options. This way, multiple Thoth accounts could use the same whitelists and blacklists. This is how blacklisting was implemented. The drawback, however, is that the list is public, and the Thoth operator might want to keep it private.
Later, for whitelisting, the list was implemented by a local file that the Thoth operator can keep private. This has the reverse drawback that it can't be shared between accounts.
To maximize flexibility for the Thoth operator, both options should be possible for whitelisting and for blacklisting. This means:
For whitelisting:
- A network account registry needs to be added, and the two lists need to be merged.
For blacklisting:
- A private file capability needs to be added, and the two lists need to be merged.
When screening was first designed, the idea was to set-up network based account storage for the whitelist by using the mute and follow options. This way, multiple Thoth accounts could use the same whitelists and blacklists. This is how blacklisting was implemented. The drawback, however, is that the list is public, and the Thoth operator might want to keep it private.
Later, for whitelisting, the list was implemented by a local file that the Thoth operator can keep private. This has the reverse drawback that it can't be shared between accounts.
To maximize flexibility for the Thoth operator, both options should be possible for whitelisting and for blacklisting. This means:
For whitelisting:
For blacklisting: