Echo JS 0.11.0

<~>
tracker1 2041 days ago. 
I know it's been discussed before, but have the following suggestions.

1. When something is spam, instead of downvoting, just post a comment of simply "SPAM";  Others should upvote the SPAM comment.

2. When something is a thinly veiled wrapper over a given release's notes, "USE <RealUrl>", where the RealUrl is a link to the release notes or change log for that release.

Thoughts?

peterc 2040 days ago. link 2 points ▲ ▼
"instead of downvoting"

Disagree. Maybe in *addition* to downvoting, but the key thing is getting them off of the front page because then there's no motivation to keep posting spam.
tracker1 2039 days ago. link 1 point ▲ ▼
Fair enough... was just thinking in terms of bypassing the cost of a downvote.
harambe 2039 days ago. link 1 point ▲ ▼
An extra button would be helpful here. “Mark as spam”
MaxArt 2040 days ago. link 1 point ▲ ▼
1. Isn't that the standard practice?
2. So, it's just a comment to add?

I have several ideas to mitigate spam posts on Echo JS, but they'd all imply code changes to the platform... and I don't know Ruby 😕
moliper 2041 days ago. link 1 point ▲ ▼
So much spam being posted and it's kind of "expensive" to downvote them all. I think is a good idea to post a comment. Although posting a comment is not as "visible" as downvotes.
tracker1 2041 days ago. link 1 point ▲ ▼
Yeah, but many/most posts don't even get comments... I usually look at anything with comments anyways.  And I do agree on it being expensive.