Not sure if it’s the same on Lemmy, but on Mastodon, your blocks are definitely shared to other instances. So the instance of the user you blocked definitely stores that you’ve blocked their user. And their system admin can view if their user has been blocked (via the PostgreSQL db).
Technically, hiding your posts from your intended blockee should be doable. But someone could run a modified version of Mastodon and display content from people who have blocked them.
Or just create a new account.
I’m unsure if Lemmy is coded in this same way (storing remote blocks on instances of the blocked user).
Not sure if it’s the same on Lemmy, but on Mastodon, your blocks are definitely shared to other instances. So the instance of the user you blocked definitely stores that you’ve blocked their user. And their system admin can view if their user has been blocked (via the PostgreSQL db).
Technically, hiding your posts from your intended blockee should be doable. But someone could run a modified version of Mastodon and display content from people who have blocked them.
Or just create a new account.
I’m unsure if Lemmy is coded in this same way (storing remote blocks on instances of the blocked user).
You can show them even if you don’t allow them to comment.