this post was submitted on 16 Jun 2023
461 points (99.8% liked)
sh.itjust.works Main Community
7716 readers
1 users here now
Home of the sh.itjust.works instance.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Are you seriously arguing on semantics?
The core of the issue is the definition of fucking censorship! It’s been a semantic issue the whole time!
Well, I've made my point. It's on you to disprove it, which, as you put it previously, "is easy". Make a burggit account, make a lemmy.world post, see how that works out for you.
See, my whole argument is that I had a beehaw account, but then beehaw blocked sh.it and lemmy.world, so I could no longer access these instances. As a user, my account and its ability to access content got censored without my say. So, I made this one instead.
When you block an instance, you are censoring users from accessing it. I can't make it any simpler than that.
Your point is moot because it doesn’t demonstrate censorship, because you can easily make an account that isn’t blocked.
Incorrect; you could still access those instances, seeing and reading posts; you weren’t able to post or comment to them yourself, and crucially are able to do so if you make a new instance that was federated with it.
Okay, so you just don’t know what “getting censored” means. This isn’t how this word is used. You don’t say “my ability to read books at the library was censored”, you say “they censored library books so I have less ability to read them”.
No. That’s not what censoring means, for one thing, and for another, you can still access the instance, just not participate in it.
I can't believe I need to explain basic English to you.
I'm going to bed, dude. If you can make that easy account and easily post, then I'll concede. But you won't, since you fucking can't.