I am someone with a real name that is relatively common first+last name, iirc about 1:50000 or so in the US, there are lots Michael Ryan's out there, I've met a couple unrelated to me. And a handle (tracker1, azTracker1, xTracker1) on various social media, and a *lot* of them are not me.
While interesting at best, this is dangerous at worst. As long as you're only testing for actual indicated names on other social platforms, then this *might* be okay. If you want real verification, most of them have some sort of OAuth interface that you can use for only name/email identification matching. If you're using a self-registered interface for what is "public" you may be violating TOS (which can be interpreted as a crime in the US.
I'm not the one who down-voted, but can completely understand why one would.
edit: Just an example of how mangled things get, the main image/job title is not me, but other pieces of information are me. https://rocketreach.co/michael-ryan-email_25502930
I was on vacation this past week, so wasn't active, but generally do a sweep at *least* once a day of all new posts... on busier days, I tend to concentrate on those that look spammy by title, have comments or are downvoted...
If you don't want to downvote a comment is usually the best option for getting attention. While it's not as quick/active as it could be, there are usually not *that* many new posts each day.
And, no, I don't always delete downvoted posts... which is again why even if downvoting, a comment helps understanding why it was downvoted.
Okay, this is the 4+ Dannjs post in less than a month... it's getting excessive and if it continues I'll start deleting future posts on it and block the repo and related domains.
When a downvoted article is "deleted" you get double karma back... I usually pay extra close attention to articles that are downvoted, so will get it back and then some 9 out of 10 times. Might be interesting to give a karma zap on upvotes if an article is removed and remove the ability to upvote if negative karma.
Downvoting and adding a comment as to why it was downvoted can help to understand why it was downvoted... either spam, low quality, off topic etc. This is especially true in the case of Video posts, where I'm less inclined to sit through the videos, I usually scan through a video and if I don't see a code editor and/or it's obviously OT, then I lean into removing it.
Note: I also try to also upvote said comments before deleting a spammy article, I don't always remember to do so.
Was on vacation this past week and haven't been as active... today has been hectic, but should be back to at least once a day sweeps again after today.
Would suggest changing your aes example to use aes-256 and the password example mention why a higher iteration count is important, and may want to switch to the async methods, especially for higher iterations and mention countermeasures as this can be a point for DDoS depending on configuration and implementation details..