Set and forget APIs that just work are kind of cool... maybe that's the moral of the story there lol
https://www.ebay.com/itm/125134793099?mkcid=1&mkrid=711-5320...
4GB RAM, 64GB SSD, and an i5-1035G is misparsed as 64GB RAM and 1035 GB SSD.
A flag button may be the most useful practical reaction to this problem. That way you can outsource the problem of faulty reports - and best case scenario even build up a following of trigger-happy users who are helpfully inclined to click the flag button in the future when the occasional glitch sneaks through.
Publishing the parser may also honestly be a good idea as well. Not the whole site, just the parser specifically - maybe with instructions on how feed in the results of small-scale scrapes (~100 pages) - so people can understand exactly what it's doing and provide feedback.
This is a very community-oriented sort of project IMHO, so by definition you'll wind up with a small following of stragglers if you hang in there; by the same token, it's possible (gain, best case scenario) that leveraging the spare cycles the community might be able to bring to the table may make it viable to maintain a level of quality that would otherwise be very hard to sustain long term.
I'm the kind of person that always buys electronics used on eBay, where you can get really powerful but 2-3 years old devices for a few hundred $. And, I find shopping for used electronics elsewhere is still terrible (how good is a 1yo i5 vs a 3yo i7?). So, I made this site to help me in that -- I started scraping eBay listings for laptops, picked out the specs and cross-referenced them to benchmarks.
True to form, I made this early in the pandemic for the fun of it (I'm not even a software dev), then realized marketing is boring and never shared it with anyone. Real life makes me busy, but there's tons of features I want to add eventually. And now I have a very interesting dataset to play around with.