Also seeing the spam, though assuming your feed looks the same as mine, I'm not sure how you could possibly doxx anyone appropriately. It's not like the spammer is posting their own details (I mean, I could be wrong, but it's not the usual MO).
More likely, by repeating the info they're spamming, you'd be helping the spammer.
Re tighter posting controls - count me in. There's a number of ways to do it, and we're a community of developers / designers / architects. Probably the best I've seen was LifeHacker US before the site was sold to Gawker Media. Initially your account was "untrusted" and your posts hidden unless others wanted to look at hidden posts. Over time, as people replied to your comments or "gave love" or "upvoted" your posts etc, you gained "reputation." Eventually you have enough rep that your posts are visible by default. No-one could see their own rep, and rep could be negatively impacted too (confirmed spam reports etc).
As for the doxxing, I assume that the spam posts are being flooded on everyone's feed since the posts don't have any tags. And I'd safely assume they are fake accounts. Yet I am unsure if that will be the right thing to do. Also, a lot of these posts have contact numbers. To start off, the enforcers can look at them.
This type of logic prevented me from posting in many reddit groups, to the point that I gave up on them. In my opinion, it provides a better user experience for older accounts at the cost of a not-too-nice user experience for new people.
I would leave the internal logic to the people at dev.to and the OSS contributors they have. Irrespective of that, you're idea seems a bit stringent since a lot of beginners post to dev.to. If I were to suggest, a round of recaptcha is perfectly reasonable at the least.
The logic is of course, up to the platform maintainers to determine, I was just throwing out an example for preventing comment spam that I'd seen work well (LifeHacker US posts, back then, could only be published by LifeHacker employees). There was a simple button for anyone who cared to view new user comments.
But yes, that system wouldn't work well for new users trying to post content, rather than comments.
Re doxx'ing - again, the contact numbers you're seeing are the ones the spammer wants you to see. Chasing those is like chasing faked emails, where the email has been sent from a server that allows open relaying. Regardless, my personal opinion is that doxx'ing should never be done. There's better ways to handle the situation, whatever the situation is (not just limited to spamming).
Also seeing the spam, though assuming your feed looks the same as mine, I'm not sure how you could possibly doxx anyone appropriately. It's not like the spammer is posting their own details (I mean, I could be wrong, but it's not the usual MO).
More likely, by repeating the info they're spamming, you'd be helping the spammer.
Re tighter posting controls - count me in. There's a number of ways to do it, and we're a community of developers / designers / architects. Probably the best I've seen was LifeHacker US before the site was sold to Gawker Media. Initially your account was "untrusted" and your posts hidden unless others wanted to look at hidden posts. Over time, as people replied to your comments or "gave love" or "upvoted" your posts etc, you gained "reputation." Eventually you have enough rep that your posts are visible by default. No-one could see their own rep, and rep could be negatively impacted too (confirmed spam reports etc).
As for the doxxing, I assume that the spam posts are being flooded on everyone's feed since the posts don't have any tags. And I'd safely assume they are fake accounts. Yet I am unsure if that will be the right thing to do. Also, a lot of these posts have contact numbers. To start off, the enforcers can look at them.
This type of logic prevented me from posting in many reddit groups, to the point that I gave up on them. In my opinion, it provides a better user experience for older accounts at the cost of a not-too-nice user experience for new people.
I would leave the internal logic to the people at dev.to and the OSS contributors they have. Irrespective of that, you're idea seems a bit stringent since a lot of beginners post to dev.to. If I were to suggest, a round of recaptcha is perfectly reasonable at the least.
The logic is of course, up to the platform maintainers to determine, I was just throwing out an example for preventing comment spam that I'd seen work well (LifeHacker US posts, back then, could only be published by LifeHacker employees). There was a simple button for anyone who cared to view new user comments.
But yes, that system wouldn't work well for new users trying to post content, rather than comments.
Re doxx'ing - again, the contact numbers you're seeing are the ones the spammer wants you to see. Chasing those is like chasing faked emails, where the email has been sent from a server that allows open relaying. Regardless, my personal opinion is that doxx'ing should never be done. There's better ways to handle the situation, whatever the situation is (not just limited to spamming).
Thanks. I wasn't aware of that. I hope the devs look at your suggestions as well.