> countries around Asia and you'll be surprised how people prioritise features
While this is true, I can also say that the other minority becomes large enough for any OEM to care. It might even drawf market size of other markets when only compares in numbers.
There's so much trust / dependency on NPCI at this point but I recently learned that it's not a public entity and thus excluded from the transparency acts such as RTI. I hope the EU does better!
I am not sure which country you are from but is the term “accountability” even relevant in India anymore? It’s been non existent since more than a decade.
I was just commenting on how good, widespread it is and no it is not the doing of the current Govt. It just gained traction during a massive f up of the current Govt.
The value for money is crazy on these boards, in my opinion. I'm planning on using these as a cheap replacement to a KVM. Flashing esp bus pirate (https://github.com/geo-tp/ESP32-Bus-Pirate) and leaving it connected to whatever device I want to control ( remotely in my case), is quite handy. The power draw is negligible so I just leave it always on connected to my wifi.
How do you manage display sharing using it? Another device? I have a bunch of refurb servers, which I'd like to keep access to not waiting for an engineer to visit it. The budget is tight so proper KVM is not an option.
Take a look at singleFile - a project that lets you save the entire webpage. It has an integration for saving the hash if the page on a Blockchain. You can choose to set it up between parties who're interested in the provenance of the authenticity.
Thank you. It's mostly because of costs (free tier).
I mostly use KV for storing flags specific to each project (which gets replicated automatically). Everything else goes to D1 (replication isn't needed here).
Cloudflare queues was something I might consider for async workflows.
D1 read replication was not available when I started working on FlagShip. However, since I only use D1 for storing data like project configuration, replication was not really necessary.
The flags consumed by the clients are pushed to and read from KV alone. KV already has geo replication out of the box, although there still is propagation delay for updates to KV.
It would be nice to have everything served from D1, I might consider it when replication is stable enough.
I've been using AWS CDK which now supports go. The only gotcha is that I have to cleanup the build cache occasionally which can easily build up-to several gigs over time.
While this is true, I can also say that the other minority becomes large enough for any OEM to care. It might even drawf market size of other markets when only compares in numbers.