I've been using wallabag for a while, switched to Pocket for this exact reason. Maybe switching back is the answer to this? Looked around a bit, someone seems to have thought about this already.
Yep, the RaspPi client is instead of the iOS/Mac app. Basically the Turn Touch API and Bluetooth spec is open source (https://shop.turntouch.com/pages/open-source) so you can extend it in ways that I haven't built natively.
How would companies submit bids though?
Should they have their own natural language/keyword analyzer to identify which product the customer is actually looking for and submit their price for it?
We've been doing this for a while for a website that receives not too much traffic:
- we use a single server and the domain name determines which white label we are on.
- we use LESS and everything is variable. We load a single compiled CSS based on the domain.
- we never hard code anything, unless we know it's a single page for a single domain (everything is internationalized).
- the database contains everything and we filter out stuff a particular white label doesn't want.
This is because the website displays content (it's not a service like shopify) and most white labels want most of our editorial content, so syncing DBs is not an option (is it?).
We have 40+ white labels and unless the customization is heavy we can create a new one in a matter of minutes.
None of HTML's new form attributes replace server side validation (which is annoying since you end up repeating code and having slight differences), however it's a good start.
With CORS and CSRF tokens, it would cut down on accidental issues – which for most sites is a bigger deal than malicious activity.
In that sense, it'd be a perfect analogue to the "maxlength" attribute on text inputs. (In fact, I wonder if it'd be sufficient to just make that attribute apply to file inputs as well...)
