It’s not how code works. There’s no reason to send this information to the client because the filtering runs server side, so the client never needs to know about it.
You’re assuming proper design. I’ve worked on systems where filtering was done client-side (and fixed that), it’s stupid, but it’s what happens when a FE is assigned a task and uses the tools at their disposal. In fact, I think Lemmy used to filter deleted comments clientside a few versions ago.
If they were deleting contents client-side then you could get around the filters by using something like tweet deck. Since we know that doesn’t work we know that the filtering can’t be done client-side.
It’s not how code works. There’s no reason to send this information to the client because the filtering runs server side, so the client never needs to know about it.
You’re assuming proper design. I’ve worked on systems where filtering was done client-side (and fixed that), it’s stupid, but it’s what happens when a FE is assigned a task and uses the tools at their disposal. In fact, I think Lemmy used to filter deleted comments clientside a few versions ago.
If they were deleting contents client-side then you could get around the filters by using something like tweet deck. Since we know that doesn’t work we know that the filtering can’t be done client-side.