I've deleted the post in question manually because I think that would be best to avoid potentially putting the person on blast in this specific context
like if I rechost something and add to it, is that just gone
edit: wow yeah it effectively does, which is uhhhhhhhhh PRETTY SHITTY
edit 2: literally the only way I was able to figure this out at all was by switching to a different profile and looking at this profile to see what was going on. so it's not deleted but my own post is completely invisible to me because the person it replied to has blocked me. this leads to a few problems because:
- I am left wondering what happened to my post
- If this was handled by leaving my post but removing the original, context is completely removed
- there is a fundamental "exploit" in this system that can be gamed via profile switching
like idk what the ideal solution is here but it feels like "not this" is at least part of it
edit 3: see, the problem with 1 is entirely user experience based. it makes it so there's no real understanding of what's going on and whether or not this is a bug or a feature. I'm not sure what the ideal solution to this is because if you pop something up going "this post is muffled because you were blocked" then it kinda sets up a whole messy situation as far as the online social contract goes when it comes to blocking
the problem with 2 is outlined in what 2 is and I don't know what kind of elegant solution for this there is? maybe removing the connection to the original user and replacing it with a block quote???
the problem with 3 is... like... shit, I'm not sure how to approach this. I think blocks should probably be account wide, or at least have the option to be? I love the idea of actually having profile switching, but if profile switching is going to leave this sort of potential loophole open, I think it needs to be pretty specifically looked at, y'know?
edit 4: ALSO if other people can see it and respond to it, I imagine it'd muffle notifications to the person who got blocked? idk there seem to be a lot of problems with this from a UX/backend perspective
