You are viewing a single comment's thread from:

RE: In defense of the flag wars

in #flag-war7 years ago

Also the flagging system with the relatively very short lock in window for the votes is needed so that people only have time to remove accidental flags/counter flags, but once locked in the only way to go about nullifying a counter-flag would be to petition other people to flag the post simply to remove the counter-flag, and this could be done because there could be a 30 day time window since the creation of the content for this petitioning to happen, same for flags, the counter flags could nullify them under the same time frame or outright counter flag the perceived abusive flag.

Sort:  

A likely problem you will encounter is if your "solution" increases in complexity the people that have to code it are likely to become more resistant to the implementation. Their resistance might even be directly proportional to the complexity.

So if you can lay out STAGES that could be accomplished to reach your end point that'd likely make it more palatable to the people that actually have to code it.

This is a complex problem from my point of view, it has many issues that need to be addressed, flag wars, abusive flagging, repeated offenses, and it's all the problem of addressing spam, abuse and plagiarizing, on top of collusive or self voting, or better stated the problem of the community policing itself.

The stages that could make this easier would be first to tax the voting power for a downvote to 10x that of an upvote, incentivizing upvotes for large stake holders, as that is the only problem, minnows and dolphins would also suffer in draining their voting power but they have little influence over payouts to begin with.

A simultaneous step is implementing the flagging system.
The steps for this could be broken down but I don't see the benefit over a complete system instead of breadcrumbs. It would need to include the piggyback rule to deal with excessive flagging/counter-flagging, and these things are simplistic from a programing point of view. Granted something like this hasn't been seen by the community since it's inception, it's slow gradual adjustments that have got us here, that doesn't necessarily mean this idea of a separate flagging system could be implemented in the same manner. It should be one of the few changes in the HF that includes it, the perfect HF would be a flagging system along with a better, more balanced voting curve.

I do believe we need to see a different voting curve. I'm fairly certain that is something we will eventually see.

As to the rest... work up details on your stages and start writing posts with as many details and examples on the functionality as you can, and you'll at least have people like me advocating to at least try it.

I am one of those that doesn't think we should do a lot of ideas in a single HF. It makes it more difficult to accurately state with certainty which change had which effect.

I instead am an advocate for more frequent but smaller hard forks.

EDIT: And yes it is a very complex problem.

Coin Marketplace

STEEM 0.17
TRX 0.15
JST 0.029
BTC 61829.34
ETH 2395.18
USDT 1.00
SBD 2.63