Loqidoubleloop: [grantcodes] left you a message 1 week, 3 days ago: You are exactly right about if I build granary integration into together then it is only in together. An ideal way would probably be to have an external client that could work on it's own. But perhaps with a simple rest api or something that other clients can integrate to make life easier for their users?
ZegnatThat does look like an oof indeed. Then again, I do not blame them. If I were to just start a new project and people ask me to add an API on top, my first idea wouldn’t have been to go and read a ton of OAuth specs either
doubleloopaaronpk: nothing has changed in Wallabag as far as I can see (over 2 years later) - there was a pull request which added client_credentials, which was then reverted
aaronpkit's always a tough call deciding when to extend a core protocol like microsub with something that is very different from regular HTTP requests, but I think SSE is close enough to HTTP and has built-in browser support so it's probably the right call
aaronpki don't think we need to complicate it and ask people to support more than one. eventsource is simple enough and is already in browsers, and we don't need a two-way stream that you'd get from something like websockets
aaronpkthere's already libraries for ios and android. at the end of the day it's just a TCP stream, and parsing it is very close to parsing HTTP responses too