we even made an interface in code that runs a given task on a lambda (backed by a docker image) or batch (backed by the same docker image) depending on cpu/mem/time constraints. the tasks themselves also send a message when they're done so you can just subscribe to that vs. long polling.
We ended up just putting up the site on S3 and CloudFront and unsurprisingly it's much faster to load now (Vercel also claims "blazing fast sites") and we're probably paying a couple dollars a month at worst.
kernel | Los Angeles, CA / Culver City, CA | Full Time | Onsite | Engineering
Kernel is looking for talented embedded, hardware, and software engineers! We are building next generation, non-invasive, mind/body/machine interfaces (MBMIs). Our team of neuroscientists, engineers, and physicists are working on the frontier, pioneering in multiple fields. The
technology we’re building will improve how we address mental disease and dysfunction and usher in a new era of exploring, improving and evolving our cognition. Neuroscience is the new rocket science.
Hey all! The first commit is almost 10 years old now but many are still finding a use case for our canvg library, which takes an svg string and renders it on a canvas. We just released v3 which is a complete rewrite in TypeScript and support for OffscreenCanvas as well as unifying the node and browser side. Would love to hear any feedback or questions!
Same in my city of Chicago ... but in this example it's just more marked and apparent that you'll get a fine (i.e. directly in the middle of the intersection showing your speed). If there was already a speed camera installed, it probably would be indicated by some average looking sign a mile back.
Once I find some time, I was going to let people register for their key, then add a routing number search, but your idea is great for the next todo. For some institutions it's easy (etc. CC#) but for others I had to push my way through the account not found messages so this would definitely help with that.
I am not disagreeing with your claim and am using OFX, for now.
My initial goal was to provide a simple and cheap API that one can get started with in minutes vs. having to gather a server list, maintain it, read through the OFX docs, etc. In my testing, I have never had a problem with stale data, but that doesn't mean that it doesn't exist. Going forward, I am not opposed to scraping if there's a demand for it.
I've never had a problem with them - granted I only tested with accounts I had access to through family/friends. That said, it is up to the bank to maintain their end of the API and make sure that their server has the uptime and correct code to parse the request and return the response, so when that doesn't happen, the only resort is to scrape. Do you have a link to the thread where the claim occurred?
I was thinking that if it doesn't take off, I'd just release the whole thing as an open source project since most of the work did not come from writing the code, but rather acquiring and maintaining the list of institutions, servers to query, and eventually websites to scrape.
From your idea, perhaps I can release the code completely free (or small one time fee) but charge for use of my up to date databases. Thanks for the help!
(1)
The toughest part is to build credibility but somehow mint.com did it. Other than getting a few users who have communicated with me privately to act as references, I haven't figured that part out. It does take some trust on the part of the users but the risks are alleviated by the fact that the money is insured and even if I had your credentials, your bank should not allow me to log in as I'm accessing it from a different computer.
(2)
Good question. I had to restrict the query as it was over 1MB in size for the full list, but I'll run it and make the xml file available for people that don't want to query each time. I created the list from a couple of sources and have only tested it with my and my family's accounts so it is hard to tell how much of the data is valid and how much is stale.
we even made an interface in code that runs a given task on a lambda (backed by a docker image) or batch (backed by the same docker image) depending on cpu/mem/time constraints. the tasks themselves also send a message when they're done so you can just subscribe to that vs. long polling.