Who knows how true it is, but the claim is that 26 Israeli tanks were destroyed in 1 day in southern Lebanon, by these drones.

It's interesting to note that apparently European mainstream media has less censorship about the topic of Israel, so they're much more red-pilled.

Bad news for me...

Yes it's fun, and interesting to see, but the browser extension mainly just exposed the problem for me.

If some kind of protection against downzap censorship, doesn't become a default for all users, then it's almost useless.

I don't want to write into a vacuum, and have well written , thoughtful posts be downzapped to oblivion.

I might be misunderstanding how much the downzaps affect ranking, over time. Could you explain more about that?

I first started looking into this topic when a post of mine that got pretty popular all of a sudden disappeared. Then I looked into it, and saw that it had been downzed very heavily.

I wrote a browser extension to compare the lit feed with another version of the lit feed, that didn't include down zaps. There's huge differences.

The downzapping on anti-zionist post doesn't occur unless they achieve some visibility.

This is a great discussion to have. I think there's a lot of options out there.

For instance, only allow down zaps to affect your feed ranking if they're not anonymous?

Or don't allow down zaps to affect your feed ranking unless they are established accounts?

One part of the answer, I believe, needs to be that this must be a default setting. Because it's if it's some obscure thing that 99% of stackers don't even know about, it'll be useless.

I think your post may have been down-zapped potentially just to obscure the actual target of the downzapping. You can see a pattern happening, especially if you look months ago, into what was downzapped.

Older posts that were downzapped, there was usually a very obvious quality reason - ai content, copy paste posts. And the amounts were much smaller.

Now the pattern is completely different. Except for posts that I believe are decoy downzaps.

I checked some of my old posts, to see if they were downzapped. There were a few, but only very minor amounts, on some of my old carnivore posts.

But now there's crazy high downs zaps occurring on anything that is anti-zionist or anti-iran war.

Check out some of my previous posts to learn how to make downs zaps more visible on stacker news with a browser extension.

I was under the impression that down zapping was originally meant for that purpose, to downvote low quality content. But now it's being used for something completely different.

We should talk about this. There should be active discussion.

You can't just give me a one-liner, you have to point me to a 1500 word github page?

How did Alby join into shitcoinery?

Maybe. But I doubt it.

I think a more likely explanation is that the strategy has become more sophisticated. This is not the first time I've posted about the "decoy downszaps".

Check out this post #1473885

There have been some very aggressive downzapping campaigns, going to more than 300k sats, that were downzapped to keep them off the main feed, and then @Solomonsatoshi was upzapping them to counteract that. These were all on anti Iran War, anti Zionist content.

I've pinged him on a couple comments.

I don't think that just incorporating my extension into stacker news is the best idea overall, it was just my immediate reaction to realizing how much censorship was ongoing.

I just want to see the whole topic discussed - the fact that it's trivial for someone with a lot of sats to completely bury posts on a topic that they don't want discussed. Any topic, not just anti Iran War, anti Zionist posts, but absolutely anything.

The default for 99% of users is for this censorship to be invisible, and I believe something needs to change.

Regarding the safety of the browser extension - I think browser extensions are safer than almost any other software, because you can actually read the code (this is not an extension that's packaged on the google webstore, you put it in manually).

You don't even need to understand javascript very well, it's mostly understandable on it's own. If you look in the manifest file, you'll see that it ONLY matches stacker.news, so that's the only one it can act on. And there's no special permissions requested (cookies, downloads, etc).

@k00b

Depends on who's doing it.