NonCredibleDefense
A community for your defence shitposting needs
Rules
1. Be nice
Do not make personal attacks against each other, call for violence against anyone, or intentionally antagonize people in the comment sections.
2. Explain incorrect defense articles and takes
If you want to post a non-credible take, it must be from a "credible" source (news article, politician, or military leader) and must have a comment laying out exactly why it's non-credible. Low-hanging fruit such as random Twitter and YouTube comments belong in the Matrix chat.
3. Content must be relevant
Posts must be about military hardware or international security/defense. This is not the page to fawn over Youtube personalities, simp over political leaders, or discuss other areas of international policy.
4. No racism / hatespeech
No slurs. No advocating for the killing of people or insulting them based on physical, religious, or ideological traits.
5. No politics
We don't care if you're Republican, Democrat, Socialist, Stalinist, Baathist, or some other hot mess. Leave it at the door. This applies to comments as well.
6. No seriousposting
We don't want your uncut war footage, fundraisers, credible news articles, or other such things. The world is already serious enough as it is.
7. No classified material
Classified ‘western’ information is off limits regardless of how "open source" and "easy to find" it is.
8. Source artwork
If you use somebody's art in your post or as your post, the OP must provide a direct link to the art's source in the comment section, or a good reason why this was not possible (such as the artist deleting their account). The source should be a place that the artist themselves uploaded the art. A booru is not a source. A watermark is not a source.
9. No low-effort posts
No egregiously low effort posts. E.g. screenshots, recent reposts, simple reaction & template memes, and images with the punchline in the title. Put these in weekly Matrix chat instead.
10. Don't get us banned
No brigading or harassing other communities. Do not post memes with a "haha people that I hate died… haha" punchline or violating the sh.itjust.works rules (below). This includes content illegal in Canada.
11. No misinformation
NCD exists to make fun of misinformation, not to spread it. Make outlandish claims, but if your take doesn’t show signs of satire or exaggeration it will be removed. Misleading content may result in a ban. Regardless of source, don’t post obvious propaganda or fake news. Double-check facts and don't be an idiot.
Join our Matrix chatroom
Other communities you may be interested in
- !militaryporn@lemmy.world
- !forgottenweapons@lemmy.world
- !combatvideos@sh.itjust.works
- !militarymoe@ani.social
Banner made by u/Fertility18
view the rest of the comments
That's not what's happening. A blahaj admin is tailoring this community's content to fit their specific views.
As seen on their site right ? They aren't actually changing the content of the community on sjw, they are just changing what is federated.
Yes, the other way around would be impossible.
Blahaj banned CDRmittens 6 months ago, which would explain the discrepency between posts as viewed from there.
Honestly, they could very well decide to just remove the community on their end if they so wished.
admin of an instance can still police their own users on external communities, this happened before (once i think) with lw (ie lw admin removed post of lw user on ncd@sjw)
Kind of, but only if an admin bans them with content removal.
Removing individual remote content from home users currently doesn't federate.
I would rather that than their admins quietly censoring NCD and their members brigading us https://lemmy.blahaj.zone/post/18102304/11350330
Blahaj doesn't even have downvotes and there isn't a bunch of their users stirring shit in here either so idk about brigading.
That one user above posted a rather neutral comment, maybe helpful even. Whatever.
The modlogs are pretty straight forward.
A blahaj admin banned CDRmittens 6 months ago, which means those posts simply don't federate there anymore.
That's... pretty much all there is to it.
Like, there isn't a blahaj mod actively watching this community and removing things in a big-shark-conspiracy kinda way. The posts never even make it there because they're from a user they banned locally.
Lemmy kinda sucks in how one could never know about some remote bans, I'll give you that.
Correct. This is an awareness post for NCD users on Blahaj that their view of our community is being censored.
oooOOOOOooo drama! SPILL THE TEA
It's very important that we know in to make informed choices about instances going forward ^and^ ^also^ ^we^ ^love^ ^drama^
The fact that the instance is named after an IKEA product was enough reason for me not to make an account there...
I get it, the shark plush is cute. Just a bit too....consumer? For me
My limited understanding is that there's an association between the shark's colors and the trans flag, and that this predates that instance in the trans world.
Honestly, I don't even care if people want to run a censored instance -- like, some people legitimately do not want to see some content -- but I do think that they should be clear that they are doing so, which it sounds like they were not in this case.
Also does make one wonder whether other material might be missing on other topics from other communities.
ponders
As a general solution to making instance censorship visible, I suppose that it'd be technically-possible to write a bot that could spider Threadiverse instances and look for discrepancies between views of a community, provide a summary of instance censorship activity. If an admin wanted to silently censor content and wanted to go to enough work to make the censorship silent, they could try to identify the bot and only show posts to it, but I imagine that it'd be more work, especially if it acted anonymously and from a VPN.
As a bonus, that could also flag post propagation problems of the sort I mentioned elsewhere in this thread, kind of be a "Threadiverse health monitor".
Regardless of the origin, it's still a bit too close to corporate worship for me.
And as shitty as it is to selectively filter posts like that, I don't think it's a problem worth creating a bot for track. OP calling it out to make others aware was the right thing to do - let the users there decide if they care.
Now if you'll excuse me, I need to create my own instance: McChicken.zone
I imagine that it's not too complicated to just look at the community via lemmy.blahaj.zone, which presumably will show missing posts.
NCD's native sh.itjust.works, which presumably has all posts visible:
https://sh.itjust.works/c/noncredibledefense?dataType=Post&sort=New
Lemmy.blahaj.zone's view:
https://lemmy.blahaj.zone/c/noncredibledefense@sh.itjust.works?dataType=Post&sort=New
Nuke, you sure that it's intentional removal? I've seen propagation issues on instances before -- like, two weeks back, my home instance, lemmy.today, was two days late on material from sh.itjust.works. In that case, resolved itself shortly after I posted to my local instance discussion community about it, so the instance admin didn't dig into it, but two days of delay definitely has something breaking somewhere in lemmy or on one instance or another.
https://lemmy.today/post/17802050
I still don't get NCD showing properly on sh.itjust.works, but I DO get new posts in my timeline, for some incomprehensible reason.
But in this case, it's in the modlogs, not a bug.
From this Tar_Alcaran@sh.itjust.works account? Like, no federation involved, just an account with home instance sh.itjust.works and sh.itjust.works-hosted community?
Hmm. Are you sure that you have the right post sort order for the community? Like, "New" (not "New Comments", which is a separate setting)? I distinctly remember, on several occasions, viewing a community and thinking "posts are not showing up", when the actual issue was that I'd changed the post ordering and not noticed. That'd produce that kind of behavior.
Yes, all the removals are about the Israel/Hamas/Hezbollah/Iran.
Okay, fair enough. Just wanted to avoid possible drama if it had been a similar technical issue.