Wow, this is becoming real! I've told some people in private that ideally/eventually I'd like to use GraphQL for building Manyverse. I might try jsbot-patchql and see if it helps the indexing upon onboarding.
Question: what's the open source license for these packages?
@Piet Ohhhh I love this so much! Getting this out there at this point is definitely the way to go IMO. ssb-patchql is really at the point where it can start making existing software faster, better, and more robust.
@Piet This should probably be more explicit, because the jsbot-patchql package.json mentions "MIT" as license, and for all legal purposes that means that the code up until that specific commit is legally under MIT and not AGPL3.
So excited for this, thanks for the update!
Yeeeeeeees
cc @Hendrik Peter look it's alive !
Noice! going to need to get my feet dirty with this goopy GraphQL stuff sometime soon.
I'm a total newb with GraphQL, I'm going to be diving into a crash-course in the office over the next few days (I got a colleague screaming that we should run our ArticleService system over graphql), but how easy/hard would it be to implement either single-user or multi-user authentication (or some form of token authentication) into the GraphQL plugins y'all have been building?
I'm quite trusty when it comes to localhost, but exposing my database (and perhaps even write access) to wifi or over the internets... I don't know.
true @gwil @ home, apart from private messages perhaps.
here you have a machine that hosts your friends’ and family’s SSB profiles and serve up data for ‘light’ remote SSB clients that just handle UI
The intention of Tightbeam is to actually do exactly what you just expressed. It seems to handle Patchql decently enough too.
@Soggypretzels stay tuned - @piet has been working on a demo app in parallel with this development. The idea was to test what was needed, and also to build something in vanilla React (rather than our exotic homegrown stack) to show people what it might be like with some off the shelf tools
The patchql
branch of #patchbay now uses graphql to determine names.
Discussing support for subjective names also lead to this excellent conversation.
TL;DR I'm considering deprecating the ability to name other in Patchbay