I think having a single place to record all your transactions would be a good feature. And if they have a way to send receipts to customers via SMS/whatsapp, it would be a great.
I would like a simple record keeping box that can be shared with more complex devices for applications requiring messages or complex reports. I would like to see the device maintain a simple "Datagram" approach for each transaction with text file export of grouped transactions.
We few people know it could be bypassed. But how will the millions of other users who know nothing about VPNs? Also what if Airtel blocks all these popular VPNs?
Also its not about if we can bypass it or not. It is about what is morally/ethically right and what is wrong.
The earth's axis is tilted so in addition to needing to know the timezone and the date in a solar sense, you also need to know the latitude and need to be able to combine those three things in your head... in practice you just look it up instead.
Oh, that's easy: the sun never sets on the British empire.
Seriously, though, time zones do not help with that. The sun sets at nine in the evening in Leicester in July. Can't be helped, the length of the day is different.
Time zone info doesn't just pop into your head. You have to look that up too, or at least receive it somehow. Sunrise data could be obtained the same way. The difference being, of course, that you wouldn't need to look up anything that didn't care about the sun, while time zone info needs to be known to make sense of any time.
If you have compiled it to HTML, wouldn't it be more efficient to serve it up as static HTML files via nginx (or any web server). Why store the HTML in redis and serve off it via an application?
With aggressive disk caching on servers static files are probably near enough in-memory anyhow (+ I'm sure you could configure a modern web server application to cache anyhow), so yeah it's probably pretty fast.
However it's more limiting to simply serve static files - you're limited to what you've generated. With redis you can serve it as json data and use it dynamically for e.g. search or showing all articles with a given tag, in a given date range, etc.
Additionally, I'm not a big fan of a whole bunch of static files sat in a folder somewhere that needs to be regenerated every time I change something. Personal preference, perhaps :-)
I host it in DigitalOcean's New York datacenter (on a 512 MB VPS). They're pretty alright, but any VPS would do the trick. In fact, I only use a VPS because I can't properly set caching or gzip headers on GitHub pages.
As far as I know, the only thing that I do that most static sites don't is precompile gzip files for HTML pages, and minify pretty much everything (including HTML and images.) PageSpeed, Pingdom and RedBot were very helpful for providing web server optimizations. I would just observe and implement every tweak they mentioned; there's a lot you can do managing your own server that you can't with AWS or GitHub.
I love how crazy fast your site is on my slow browser (chrome on iOS seems to drag when you've got 100+ tabs). I'm starting a blog network as a side project and setting it up as Jekyll for exactly this kind of performance.
Also love the honest assessment that in your repo's description that your setup is "far more neckbeard and far more work" :)
Interesting. It's still useful to have the data in REDIS so you can easily search through data server-side, but of course that could simply load from static JSON if + when REDIS is restarted/new data is added.
I want to build more features and add support for any RSS feeds too.
Nothing to make money out of, but something for my personal use.