activistPnk

@[email protected]

This profile is from a federated server and may be incomplete. Browse more on the original instance.

activistPnk,

Ah, I think I see what happened. A collection of accounts were used to down-vote my post then up-voted a bunch of older posts. This pushed the post off the 1st page in a way that goes unrecorded in the modlog.

activistPnk, (edited )

It could be legit.

It might be interesting for to add a smart algo that checks whether a rapid sequence of down votes occurs in a short span of time and see if the set of accounts used for the down voting shows a voting pattern with other posts. Or even without timing analysis, voting patterns alone might reveal accounts used for timeline tampering particularly if the same IP address is used.

activistPnk, (edited )

Exactly… makes no sense that that post would trigger a lot of people. We can only guess because down votes don’t come with an explanation.

What I’ve noticed in the nation-specific communities is there’s usually a strong amount of national pride. Denmark in particular but I notice the same in Netherlands communities. If a post can be taken to be negative or embarrassing to the region, criticism tends to be unwanted and down votes are likely.

In the case at hand the post was factually accurate and not really provocative. Since people wouldn’t likely get too emotionally hot-headed about ATMs, it seems unlikely that a large number of people would be so emotionally triggered. Probably just one person with many accounts.

activistPnk,

Indeed. IIUC, OP said 33 reqs/min is a ceiling and tunable on a per-target basis.

If the target is a Cloudflare instance, you could perhaps even do 300 reqs/min without even being noticed.

activistPnk, (edited )

That is way beyond acceptable use

Each server would have its own acceptable use policy. Also consider the social detriment of Cloudflare nodes. We could even say @bahmanm has a moral /duty/ to overwork the Cloudflare nodes :)

@Blaze: thanks for pointing out lestat. That’s one of the very few services of this kind to be responsible enough to red-flag the Cloudflare nodes. I hope @bahmanm follows that example; though it could still be improved on.

It’s misleading for any tor-blocking Cloudflare node to have a 100% availability stat just because by design it deliberately breaks availability to a number of users in an arbitrarily discriminatory fashion. lemmy-status.org and lemmy.fediverse.observer/stats do a bit of a disservice by not omitting or flagging nodes.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • uselessserver093
  • Food
  • aaaaaaacccccccce
  • test
  • CafeMeta
  • testmag
  • MUD
  • RhythmGameZone
  • RSS
  • dabs
  • KamenRider
  • TheResearchGuardian
  • KbinCafe
  • Socialism
  • oklahoma
  • SuperSentai
  • feritale
  • All magazines