Good morning,
Thanks for your thoughts.
In one sense I agree with them all to a degree but I think that if the idea is liked then they are not breaking reasons and some would naturally disappear over time.
Back to your idea, I think I understand the principle, people attach proof of their post history to stop others from feeling that they'd be wasting their time answering questions by those who haven't looked it up. It's pretty much the same reputation system that drives Stackoverflow and the various other Stackexchange sites, but without the enforced rules on posting/replies/accepting correct answers.
You are sort of correct and this is possibly one area where I am struggling either with the idea or the explaining of the idea. The answer is both yes and no.
The key point of reputation systems on stack exchange and similar ideas on various forums is that reputation is a sliding scale, whereas I am aiming at just two/three levels, new, good along with a few that are new and bad. But I expect new and bad to be deleted by their owners or possibly by automatic housecleaning.
It all seems very user-driven, in an era where bad actors are almost entirely automated, what countermeasures do you propose to stop someone building a fake profile? Amazon is riddled with fake 5 star reviews for third rate products (I bought a soldering iron off there the other day and the tip oxidised almost immediately and it came with a scratchcard voucher that links to a phishing site).
The key point of the idea is that absence of a code is a status in itself. Yes I know that that is a pretty big statement and ambition.
The idea does rely on users deciding that they dislike the use of a code to the degree that they would report it. These reports are then looked at by a real person and for me funding these people is a big issue.
Imagine that you are hired to post 100 fake reviews. If you get genuine codes then anyone looking up one code would also see the 100 other codes you also had issued at roughly the same time. Getting 100 codes would also reduce your productivity.
You might decide to take the chance on using the same code on all 100 posts on different sites where they would then not match the declared use of the code when checked.
An automated posting bot that needs to get codes to include in its automated posts could easily get into a long term battle of code, but in the early days automated posting systems probably won't be bothered with getting codes.
If the biggest e-commerce company on the planet is failing to meaningfully deal with these issues,
Big e-commerce companies have little motivation, they are happy to leave it to the reader and possibly add a "Verified purchase" type sticker to the comment.
something user-driven and which requires manual user lookup and is limited both by those who sign up and remember to post their code first is of limited utility.
I think that this will not be an issue if people like the idea and only time will tell.
As a bare minimum there'd either need to be a widget embedded into every site that uses it, or a browser plugin that automates the code-addition and lookup.
But when?
If the idea has merit and catches on then in the early days I don't agree.
If 18 months down the line there was significant use of the code then such facilities would start to appear on sites.
Although I hadn't considered it Chrome, Firefox and Edge adds-in would be easy to create, that only leaves Safari on iThings.
Given that most forums are based on standard platforms then integration could be seen as useful and would appear. It's the same for most ecommerce, a lot is based on Shopify etc and if they are not adding in an API call is something that the developers can sneak in.
And since the code contains a URL, it will trip a lot of comment spam monitoring systems.
Again if the idea catches on then users of the spam filter would add the site to the exemptions list for that filter and question any filter doesn't have such a list.
Finally, assuming your service becomes successful, what happens when your site is breached? (and from bitter experience, when you are involved in running a successful site it is when, not if) that's a lot of user data to mine and/or generate.
I don't think that there is any useful information to steal as it is all already public and if anyone wants it they can already scrape it from forums and review sites.
Account Record - ID, Contact Email, username, password, Some status flags
Code Record - Account Record ID, Site URL, Username on site, flags for issues
Code Record - Account Record ID, Site URL, Username on site, flags for issues
Code Record - Account Record ID, Site URL, Username on site, flags for issues
I'm not trying to make you disheartened, the more weapons we have to combat bad faith actors, the better.
I'm not, I agree that your arguments
could be true but I don't think that they
have to be true. I would ask you to think about Twitter, something that sounded absurd when introduced with no users.
For me the biggest issue is would users be willing to donate or subscribe to the service or only use it if were free and the best way to find out is to try it.
Bye
Ian