I was originally going to make this as a reply on Omniscients' thread, which can be seen here: https://hackforums.net/showthread.php?tid=5605313, though, I decided to make a whole suggestion out of it, as I would like a larger groups opinion on this.
What you are going to read below, is a suggestion of furtherly expanding the 'hopefully' future product purchase validation we are going to have here on Hack Forums to make the marketplace a better place. I do realize, that the idea itself hasn't been put into work, yet, but I do feel like this would be a great addition to the idea itself. Big props to Omni for coming up with the brilliant idea itself, hopefully, I can contribute something positive towards his idea.
The actual idea, for those of you who are too lazy reading Omnis' thread, is pretty simple. There is going to be a drop-down menu for a product/service, where the buyer enters a serial, which then confirms the identity of the HF user, who purchased the seller's product/service. The seller can use this information to connect their product to the user, perhaps even use it as a communication tool, to share further information with their buyer.
Instead of being so garrulous, let's get onto the suggestion.
If you were to sell a product on HF exclusively, or, as you stated, want to differentiate HF sales with off-site sales, then this would be an amazing way to do so. You stated, that sellers can either have it voluntarily to have a verification or make it an obligation if you want the seller's product. My idea goes this way; click a 'VERIFY UID' button, after clicking this button, information will automatically be put into a database(?), and then, the buyer will get directed to a sales thread. The seller can then register if the user purchased his product or if he decided not to proceed with the purchase.
This could work in a couple amazing ways, and I have listed below, what the positives are for this idea.
Determining HF sales
By using this function, you will be able to determine how many copies of your product you sold strictly on Hack Forums. It would have a count, that shows you who went through and ordered your product, and it would be strictly Hack Forums sales, as it would be registered here on the site, perhaps under a directory - hackforums.net/productsales.php(?)
Knowing who purchased - potential anti-leak
By knowing exactly who purchased your product, you would be able to determine who may have been responsible for the leak of your product. You would be able to see the users' profile, and thereby being able to determine their credibility, and also have a statistic of who purchased your product, and what sort of status they have on Hack Forums.
Communication to your customers/not-customers
By having a table, or a database, if you will, of who purchased and did not purchase your product, you would be able to contact your customers, perhaps with updates, new products(?) and just general support. By having a table of people who went through by verifying their HF profile, but decided not to purchase, after all, you would be able to get in touch with these so called prospective customers, and perhaps convince them to purchase your product.
Restricting sales to a specific target group/forum status
You could(?) restrict sales to specifically upgraded users, Ub3rs only or perhaps even a whole other status. This could help people selling high-quality products/e-books, by limiting it to only upgraded users being able to purchase your product. That could decrease the possibility of people leaking your product, as it would be very, very unwise of a high-profile user to leak your e-book. If you have limited your sales group, then it would definitely be easier for you to determine who may have leaked your product, or heck, just limit it because you would like to keep the exclusivity.
What you are going to read below, is a suggestion of furtherly expanding the 'hopefully' future product purchase validation we are going to have here on Hack Forums to make the marketplace a better place. I do realize, that the idea itself hasn't been put into work, yet, but I do feel like this would be a great addition to the idea itself. Big props to Omni for coming up with the brilliant idea itself, hopefully, I can contribute something positive towards his idea.
The actual idea, for those of you who are too lazy reading Omnis' thread, is pretty simple. There is going to be a drop-down menu for a product/service, where the buyer enters a serial, which then confirms the identity of the HF user, who purchased the seller's product/service. The seller can use this information to connect their product to the user, perhaps even use it as a communication tool, to share further information with their buyer.
Instead of being so garrulous, let's get onto the suggestion.
If you were to sell a product on HF exclusively, or, as you stated, want to differentiate HF sales with off-site sales, then this would be an amazing way to do so. You stated, that sellers can either have it voluntarily to have a verification or make it an obligation if you want the seller's product. My idea goes this way; click a 'VERIFY UID' button, after clicking this button, information will automatically be put into a database(?), and then, the buyer will get directed to a sales thread. The seller can then register if the user purchased his product or if he decided not to proceed with the purchase.
This could work in a couple amazing ways, and I have listed below, what the positives are for this idea.
Determining HF sales
By using this function, you will be able to determine how many copies of your product you sold strictly on Hack Forums. It would have a count, that shows you who went through and ordered your product, and it would be strictly Hack Forums sales, as it would be registered here on the site, perhaps under a directory - hackforums.net/productsales.php(?)
Knowing who purchased - potential anti-leak
By knowing exactly who purchased your product, you would be able to determine who may have been responsible for the leak of your product. You would be able to see the users' profile, and thereby being able to determine their credibility, and also have a statistic of who purchased your product, and what sort of status they have on Hack Forums.
Communication to your customers/not-customers
By having a table, or a database, if you will, of who purchased and did not purchase your product, you would be able to contact your customers, perhaps with updates, new products(?) and just general support. By having a table of people who went through by verifying their HF profile, but decided not to purchase, after all, you would be able to get in touch with these so called prospective customers, and perhaps convince them to purchase your product.
Restricting sales to a specific target group/forum status
You could(?) restrict sales to specifically upgraded users, Ub3rs only or perhaps even a whole other status. This could help people selling high-quality products/e-books, by limiting it to only upgraded users being able to purchase your product. That could decrease the possibility of people leaking your product, as it would be very, very unwise of a high-profile user to leak your e-book. If you have limited your sales group, then it would definitely be easier for you to determine who may have leaked your product, or heck, just limit it because you would like to keep the exclusivity.
![[Image: I36qJLM.png]](https://i.imgur.com/I36qJLM.png)
