So I'm in a phase where I'd like to start hooking up my #tightbeam app with a GraphQL backend (thinking patchql as many of you pointed out).
The basic idea (for now) is to start Patchwork with a small plugin (needs to be incredibly easy to set up for the end-user), then open the mobile app and hook that up to the patchwork machine to start receiving gossip.
There are however 2 problems that I'd like to tackle at some point:
1. I can't bother my users with ip-addresses nonsense.
To take myself as an example: I keep patchwork installed on a laptop that is moving from network to network so I would need to update the phone side all the time to find my laptop. second issue with that is that most WIFI networks I connect to don't allow me to just login to the router to open up ports.
The dat protocol is pretty sick, you can basically take a hash-address and connect to it... I'm going to need something like that to start a connection with PatchQL. how, no idea.
I will need to create some kind of rate-limited auth/oath system on top of PatchQL or the connection above to make sure others can't just get in on my session and read/post on my behalf (especially when I start interfacing my PatchQL instances to public ports. For this I probably need to start a chitchat with @Piet.
One of the solutions would be to make my own graphQL server (that also allows the creation of new gossip), but that's potentially going to be a big extra stone in the maintenance-backpack.
I'd love to have a chat with you @Piet and @Matt McKegg if you have some time this week to go over some questions and more importantly, hear you out on the thoughts you have on that fancy PatchQL system you built.