Suggestion For Important OPSEC Threads : Dread | Torhoo darknet markets

Certainly, something along those lines and there are probably a bunch of ways it could be done. The main goal would be to connect the new info to the old post somehow so that as people are reading the stickies and posts deemed most valuable regarding OPSEC, that the newest information is plugged in as it becomes available.

It would require some kind of review process similar to subdreads where moderators have to approve posts before they go live to limit bad actors. I know mods already have a lot on their plate in a lot of cases, and people are volunteering their time here so maybe it could even be a matter of getting X number of upvotes from user accounts deemed eligible to discern whether or not the addendum is factual. Say it needs 5 updoots from qualified senior accounts to go live, or 1 mod updoot. One potential hangup I see is there would still need to be something to prompt users to go back and review the original stickies and writeups in the first place.

Maybe the markets and/or vendors could be solicited to pitch in on a reward fund kind of like a bug bounty. For every addendum contribution that is factual and approved, a small reward is given to the author with the option to donate that reward to the Dread platform. Vendors could even pitch in store credits or special discounts as rewards. Some kind of incentive to keep people reviewing and correcting the information would be needed I think, perhaps all it would take is a special recognition badge? I'm not sure really. But one of the barriers to entry for a lot of people to come play here seems to be the complexity of it all.

Granted, this isn't a place where just anyone should be derping around, but easier access to correct and current information could help breathe some new life into the place and make it a bit less intimidating to get involved in.

Welcome to the convo, /u/Doc15. I appreciate your thoughtful post!

I agree entirely that none of the previous steps should go into the rubbish bin. 100%. The quickest way to repeat history is to forget the past. I was thinking about this in my original post a bit when I mentioned being able to quickly identify the new information or procedure, but also still be able to view the prior. I don't have a clear image of how that would work or appear on a screen, but I'm in total agreement that the prior is an important step in understanding the current and by no means should be discarded or buried in an archive somewhere.

You're also right about barrier-to-entry. For everyone's safety around here, there must be a filter of a certain mesh to screen out those who tend to make irresponsible choices without regard to the consequences for not only themselves, but also the other users they interact with- so the complexity shouldn't be seen as something to do away with entirely.

I know quite a few people IRL whom I'd never invite here even if speaking to them on the topic wasn't a critical opsec failure to begin with. I think part of my concern is there being so much raw information to take in here, some of which is difficult to piece together and find the most current consensus on, that there are a good number of people who ARE the kind of folks we would normally welcome to the space and who would act reasonably and responsibly, and also be of apt mental and moral fortitude, that are unintentionally filtered or dissuaded by an unclear sense of how things should operate in the present moment. Opsec can absolutely change day by day and we've seen many recent examples of it.

I guess this is starting to come to what prompted me to write with concern and a suggestion in the first place. Is there anything we can do to encourage live, active, current, and correct organization of information, past and present, to foster the growth of high-quality users while simultaneously curbing the growth and filtering out lower-quality users. The idea of what a high-quality user is vs a low-quality user would probably need to be refined in the course of finding the answer and executing, but with a revamping of the place on the horizon, I felt compelled to start talking about it.

Thanks again for your input, /u/Doc15. What started off as a kind of cloudy concern is coming into sharper focus as I read and write about it.

EDIT: I forgot to add that a primary benefit of an active on-the-fly prodecure to update info in realtime would be avoiding the inevitable, eventual, and periodic major house cleaning that happens when the information reaches a point that someone or a group of people must drop everything in their life/lives to spend weeks or more bringing things up to date.

Why let things go on for so long then invest a lot of time all at once, when the task could be broken up into much smaller increments and spread across more participants and be more up to date more often than otherwise? I hope that's making sense.

The infrastructure I would have no clue about. Would have to leave that up to the folks that speak computer. In operation, I think it could be something like reporting of posts. When something needs updating, there is a report option, then it cross posts up in an invite only subdread where the posts needing updates are in a queue. Updates could get added using come BBCode I think it is, to change the font or text color of both the info that was updated, and the new info so the new info stands out. Then once it's updated, it gets a stamp of approval. Maybe the post itself shouldn't be updated, because then it might appear that the OP said things that they did not actually. But maybe the parts in question could be highlighted and the new info posted in the top of the comments. Or even just a link to the newest info post could be pinned in the top of the comments.

Just ideas. There are many ways to skin a cat. I've heard whispers of a tagging system for posts around here, perhaps something like that could be utilized, or maybe it's already happening. I'm not sure.

You would need fact-checker for the updates and outdated info