djac1d

It won't login for me at all. Just crashes

As a software engineeer, I agree to this, It wouldn't be too hard to build a small spa (single page app) or even a small api that you could integrate better into your existing toolset - with a submit price feature, where users submit their prices.

There is, as always, a cateat to this of course being that people could spam incorrect prices - throwing off the prices.

Which is why a majority trust model (think about it as how bitcoin confirmations work) would work well.

Things to know before reading the process I have in mind:

• Each user is assigned a trust score (wrong prices awards negative trust, correct prices awards positive trust)
• Items are repriced when the system sees enough updates with a similar price (including possibly threshold)
• Users are given a cool-off period of a specific number of hours/days - if x number of price update submissions are deemed incorrect (within a specific theshold of an agreed price) 

This is obviously a very quick and rough idea of the process: (which I'm sure others could improve and have ideas about)

1. User submits price update for item
2. Price is added to a event store (queue) along with that user and their "trust score"
3. After a number of submissions / a set interval of time - the event store/queue is looked at for updates, aggregates these, ignores outliers and sets new price
   1. Users whose price submissions were used gain positive trust
   2. Users whose submissions were ignored are deduced trust

What do you think?

Reason for arriving at this thread?

I was just looking up my sales and saw something in the tracker, searched ssw, saw it was out by +300% (ssw says ~1k, item tracker says 3k), searched on how to submit price updates and saw this thread.

My creds if anybody cares: Have worked in development for over 15 years.

Would love to help anymore if I can

If NC aren't willing to do this, I could create a chrome plugin that tracks any visits to shops, lookups on SW/SSW and submits them, although of course that would be an entire different service outside of neocodex. But it'd be better keeping it on here I guess