Nullboard: Kanban board in a single HTML file

(github.com)

578 points smusamashah | 2 comments | 19 Dec 24 14:29 UTC | HN request time: 0.462s | source

Show context

huijzer ◴[19 Dec 24 16:58 UTC] No.42463359[source]▶

I really think we are as developers underusing setups like this. If you could somehow figure out a simple but effective sync between devices then that would be able to cover many use-cases.

Maybe we just need an sqlite with better support for replicas? Then people have one tiny server with a bunch of sqlite’s to which the apps can sync?

replies(10): >>42463533 #>>42463581 #>>42463651 #>>42463678 #>>42464303 #>>42464442 #>>42464633 #>>42469937 #>>42476545 #>>42479191 #

1. WickyNilliams ◴[20 Dec 24 10:42 UTC] No.42469937[source]▶

>>42463359 #

I feel GitHub gists are a very good store for data: writable, versioned, shareable and read-only for non authors, workable, support for arbitrary data including binary

replies(1): >>42479805 #

2. huijzer ◴[21 Dec 24 14:14 UTC] No.42479805[source]▶

>>42469937 (TP) #

I tried that. The problem is that you will always need a middle-end (a separate server between your stand-alone front end application and the GitHub server). You can't just distribute a stand-alone app and let it talk to GitHub directly. Or well you can but only if you get a token with *FULL* scope for all repositories. What I as a developer need is a scope for only one repository. That's how stand-alone and especially browser-based applications can remain safe. You don't want to store tokens with full permissions in multiple apps.

↑