#dev 2019-04-14

2019-04-14 UTC
SinaCutie, gRegorLove, [tantek], [chrisaldrich], ja1, eli_oat, tw2113, [eddie], [dougbeal], ingoogni and [Rose] joined the channel
#
@jackyalcine And just like that, I lost a crap ton of Webmentions. I know they exist in my object storage but they’re not in my database. (https://v2.jacky.wtf/post/f8d8176f-b071-4eb8-9aa1-6504c7572912) (twitter.com/_/status/1117329465275756545)
seblog, [kevinmarks], doubleloop and gRegorLove joined the channel
#
@jgmac1106 ↩️ Here it is https://indieweb.org/Getting_Started I then go https://brid.gy and sign up and then use IFTT to send all post to Twitter but adding microformats to blogger is the first step... (https://quickthoughts.jgregorymcverry.com/s/8GbxG) (twitter.com/_/status/1117389334074863619)
[jgmac1106], doubleloop, ingoogni, swentel and [kimberlyhirsh] joined the channel
#
@jgmac1106 ↩️ The patches are beautiful...I don't do formal anything been playing with badges as I kind of blog comment called webmentions. Just credentialing at the domain level and allowing trust and credibility to be the source of trust and credibility (https://quickthoughts.jgregorymcverry.com/s/1KvEnW) (twitter.com/_/status/1117425923169628161)
gRegorLove and doubleloop joined the channel
#
doubleloop Oof: https://github.com/wallabag/wallabag/issues/2800
#
Loqi doubleloop: [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?
#
sknebel hm, no Loqi previews?
#
sknebel (also, yes, oof)
#
Zegnat That 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
#
sknebel I would have expected a simpler "just copy-paste an API token" approach then though
#
doubleloop Nice to see aaronpk's page/book referenced in the discussion :)
#
Zegnat It *is* a really good book
seblog joined the channel
#
aaronpk whoa that thread
#
aaronpk that is painful to read
#
aaronpk so much making up random stuff
#
aaronpk at least that last comment gets it right, but i can't tell how that ended up playing out in the product
#
aaronpk i need to go re-read that whole thread to figure out why people are confused about this stuff and try to write some more posts that explain it
[tantek] joined the channel
#
[tantek] I have no idea what this is talking about but I like the analysis: https://hueniverse.com/http-frameworks-must-die-717a37b6b164
#
sknebel stupid clickbait title though
#
doubleloop aaronpk: 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
#
doubleloop And client apps are still storing user credentials (e.g. https://github.com/wallabag/wallabagger/issues/151)
#
Loqi [TheCapsLock] #151 Critical security issue : Username and password are stored cleartext in storage.js
#
aaronpk ugh
KartikPrabhu, chrisaldrich, leg, tw2113 and [jgmac1106] joined the channel
#
jacky hmm that's troubling
KartikPrabhu, tw2113, chrisaldrich and krychu joined the channel
#
jacky aaronpk: lemme know if you began tinkering with EventSource/SSE for microsub
#
jacky I'm thinking about doing it for bondye (my microsub server)
eli_oat joined the channel
#
aaronpk ah cool
#
aaronpk i do think that's the right option once we start going down that route
#
aaronpk since it's closest to HTTP out of all the realtime options
#
jacky yeah and seems to be more friendlier than hammering the server with requests
sl1 joined the channel
#
aaronpk i use SSE already for a bunch of stuff thanks to nginx having a module that can support it, so i can even use it from PHP :)
#
aaronpk it'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
#
aaronpk looks like there are some libraries for ios and android for it too
chrisaldrich joined the channel
#
jacky I wonder if providing a way to discover streaming methods could help with this
#
jacky could also encourage a common vocabulary across them
#
jacky `action=stream`
#
aaronpk i 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
#
jacky Hm okay
#
jacky I was thinking past browsers (like maybe over MQTT)
#
aaronpk eventsource works outside of browsers just as well though
#
jacky but keeping it simple and way more testable makes sense
#
jacky Ah okay
#
aaronpk there'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
#
jacky ah just reading more into now
#
jacky hm okay thankfully someone's worked on this bit already lol
tw2113 and [tantek] joined the channel