7 ms·
Eventually, depending on how it goes, the URL will contain a key to some DB entry, so multi-device persistence can work. Adding all this to the URL is doable to
by educated_idiot 6y ago
Eventually, depending on how it goes, the URL will contain a key to some DB entry, so multi-device persistence can work.
Adding all this to the URL is doable too, I might just start with that, thanks for the idea ;)
- bko 6y agoIf at all you could make it stateless, you should. For one, you don't need a db. Also, there were some people in the thread that liked the local storage feature. Finally, as a user, I can feel safe using your service because I know at any time, if you site disappears, I have the url and I can trivially parse the url into json and do whatever I want with it. You could even build the parser or have an export to json button. If you want to add more stuff like images, longer descriptions, some links, etc, then yeah you'll likely need a backend
- educated_idiot 6y agoYeah, I haven't given it that much thought. It only started as a weekend project. I would like to keep it as local as I can. Possibly, there will be 2 uses: a non-db, non-url, local version AND an account based thing.