Matthew Hollingsworth

Community Staff Joined over 1 year ago

  • 47 stories
  • 6 comments
  • 30 upvotes
Load more stories
  • Posted to So this downvote bombing thing is interesting ..., in reply to Ken Em , Apr 22, 2019

    That's a good point. We do remove content that isn't flagged occasionally, but it's harder to do. We can do better there, especially now that we have more people to help. You should see an improvement there as we go. That being said, we'd love for the community's continued help in flagging things that aren't DN appropriate.

    The invite only system (or something more restrictive) is something we're still considering, but wanted to see what the effect of the delayed comments for new users was first. If the consensus is we should go back to a more restrictive invite system, then we're certainly open to discussing it. There are lot's of things to consider, but it's definitely still on the table.

    1 point
  • Posted to So this downvote bombing thing is interesting ..., Apr 22, 2019

    Hey all!

    Thanks for the feedback. I can assure you it’s not falling on deaf ears. This thread is important, and I wanted to give some context as to why we made the decision to go with downvotes. As you’re all well aware -- we were having some serious spam issues last year (especially Oct/Nov). The solution that we came to (after asking the community for their input) was to implement downvoting so that the best content would be the most visible. Downvoting obviously isn’t set in stone, but it the most requested option at the time, so we went with it. Also, we delayed comments for new users for five days in order to make sure these were people that were actually interested in being a part of the community.

    I’m sorry that some here feel the community is going in the wrong direction, or that we’re doing a poor job. We’re doing the best we can. To be honest, it’s been difficult to find the right balance here, as some of the direct messages to us have been nasty and unproductive. For those who reached out with productive feedback that we missed, I’m sorry. That’s on us. We’ve brought on more moderators to catch lousy content and remove it. Yes, sometimes we miss them, but we’re active here regularly throughout the day, every day. I personally remove around 4-5 stories a day that are flagged.

    That all being said -- let’s talk about ways we can improve. We want to hear them!

    5 points
  • Posted to ATTN MODS: What is being done to stop the flood of sports spam currently underway on DN?, Oct 08, 2018

    Yes Ken, it's been a bit chaotic for us over the past few days trying to find a solution. I spent most of my time deleting spam while the dev side tried to find a better solution. We certainly were not ignoring it. The thanksgiving weekend (in Canada) was spent trying to figure out what to do and how to solve it.

    I know this sucks, and I appreciate the community's patience with it. It was easily the worst spam attack we've seen and we were caught a bit off guard.

    We're genuinely sorry. I understand this was frustrating and turned people away. All I can say is that we're doing the best we can, and need all the help we can get.

    Matt

    12 points
Load more comments
https://www.designernews.co/users/86056/matthew-hollingsworth
www.designernews.co
crawl=CC-MAIN-2019-18
50535
application/http; msgtype=response
sha1:SQPJZLGLTXZVWETCXJ5INB7EFTCTC4PE
<urn:uuid:f377e7f7-23d2-4ad5-92ea-548d6923bc12>
2019-04-23T18:06:06Z
52.72.250.2
text/html
sha1:B23VAQMWQHTDONJ7U35QCXBROUQYMLC7
<urn:uuid:b96f9de1-669d-4c1e-affe-54047f0dcbf0>
https://www.designernews.co/users/86056/matthew-hollingsworth
response
<urn:uuid:c640d168-874c-4fb0-8a44-0483429bc753>
isPartOf: CC-MAIN-2019-18
publisher: Common Crawl
description: Wide crawl of the web for April 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-169-175-90.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/