This was about 8 years ago and I am not sure I ever retained a local copy of the repo. If I find it, I’ll resurrect it in a public Github repo unless there’s some NDA/IP issue.
Especially if that person is in a different country than the US. Wiring money from the US to many countries is an exercise in frustration and futility.
This is great. I'm going to use this with something I'm working on. The edge behavior is just what I need.
When you say limitations are a "relatively small number of clients need to share some state over a relatively short period of time," I read in another comment about a dozen or so clients, but what about the time factor? Can it be on the order of hours?
> but what about the time factor? Can it be on the order of hours?
So far I’ve focused on use cases where clients are online for overlapping time intervals. When all the clients go offline, Cloudflare will shut down the worker after some period and the replay ability will be lost. The core data structure is designed such that it could be stored in the Durable Object storage Cloudflare provides, but I haven't wired it up yet.
One more thought - any consideration of hooking this to Cloudflare's queue? Then you could optionally connect another worker to that and e.g. persist everything in their D1 SQLite database.
I haven’t looked at the queue specifically, but Durable Objects have a nice key/value storage mechanism that happens to map nicely. It would take a bit of munging to make it work for a stream instead of a single value, but I have a design in mind.
Been playing in beer leagues for a long time. There's one for everyone - whether it's hockey (my vice), baseball, softball, basketball, etc. - just tons of options.
It's half about the sport and half the people. I've made lots of friends playing hockey at midnight during the week.
This is great. I've been working on an adventure motorcycling trip planning app which has similar requirements of being able to work offline as you ride your preplanned trip.
Yours is a good example of what can be done by keeping it simple and not getting wrapped around the axle with complicated frameworks.
It makes me regret all the time I've spent trying to figure out the absolute best tech stack to use rather than just working on finishing the damn thing.
I've extensively used Osmand off-line during my overlanding trips, from Cape Town to Europe across west Africa and from Czechia to Mongolia. Why reinvent the wheel?
In my case, looking at a very similar set of requirements for a project yet to be started, a target audience that includes both Android and iOS and people who might be reluctant to install an app (but should have the option to "offlinify" the website they use, perfect match for PWA)
I know that pain. It helped that I had a two week time constraint! I really wanted to use Svelte, but I found it nearly impossible to use without a build script.
I'd love to hear more about what improvements you'd like to see. Nothing is ready to be shared yet, but when it is I'll announce it here first for beta testers:
It's open source so when it's ready you can fork it and call it anything you want. Some of the features are meant to be specific to motorcyclists. And as far as getting the word out, it's easier to make it specific to a particular community since I know where they hang out online and how to get it in front of eyeballs.
You can subscribe by sending an email to ~scooter/mototripper-dev+subscribe@lists.sr.ht. Feel free to send a hello to the list with what you'd like to see. I'm banging away on it every night when I get home from work.
You can subscribe by sending an email to ~scooter/mototripper-dev+subscribe@lists.sr.ht. Feel free to send a hello to the list with what you'd like to see. I'm banging away on it every night when I get home from work.
Let's just accept you can build just about anything in any language. When I see posts like "I built X in Rust," I just assume the process was so onerous that they had to impress others by saying they did it the hardest way possible. /s
I have a couple apps that only I use or are used by a handful of friends. For hobby projects, I never regret building things that I think are useful but I can't be assed to try to market them to others.
1. Mototripper - live streams my location when I'm on a long distance adventure motorcycle trip so my kid knows I'm still alive and moving.
(e.g. <https://www.mototripper.app/track/~knobbies> - a trip through Finland, Sweden, and Norway I took a couple weeks ago.) Built with Sveltekit.
2. Vatinator - an app to apply OCR to Estonian receipts to claim VAT reimbursement. Built with NextJS.
