Because grocery stores don’t make that data accessible to third party developers, otherwise someone would do what you’re suggesting and they’d risk you shopping elsewhere.
Because grocery stores don’t make that data accessible to third party developers, otherwise someone would do what you’re suggesting and they’d risk you shopping elsewhere.
I’m really enjoying Otterwiki. Everything is saved as markdown, attachments are next to the markdown files in a folder, and version control is integrated with a git repo. Everything lives in a directory and the application runs from a docker container.
It’s the perfect amount of simplicity and is really just a UI on top of fully portable standard tech.
Salient demonstration, but if image proxying were to come to Lemmy I’d hope it was made optional, as it could overburden smaller instances, especially one-person instances (like mine). We also need a simple integrated way of configuring object storage.
I wrote a few scripts to automate this entire process for me:
If you’re able and willing to self-host, I’ve developed a pretty great system that automates my entire process. The app I’m using on mobile is also available on iOS
I welcome any alternatives to the current situation, but unfortunately that’s where we are right now.
The only solution would be a massive effort that requires decades of engineering hours and a few million dollars.
Firefox is actually a bit faster and lighter than Chrome these days. Worth checking out it or it’s forks over Chrome
Lesser of two evils
Go ahead and try scraping an arbitrary list of sites without an API and let me know how that goes. It would be a constant maintenance headache, especially if you’re talking about anything other than the larger chains that have fairly standardized sites