#dev 2021-02-09

2021-02-09 UTC
[benatwork] joined the channel
#
jacky jamietanna[m]: this is basically what I think silo.pub / micropub-based syndication would be sending! https://github.com/indieweb/micropub-extensions/issues/19#issuecomment-775498512
#
jacky maybe using `replace` to swap out the syndication url (or add it somehow?)
[snarfed] joined the channel
#
[snarfed] you all may be interested in https://github.com/snarfed/bridgy/issues/796
#
Loqi [snarfed] #796 micropub API for bridgy publish
#
[snarfed] would continue to entrench bridgy as an SPOF, but the vast majority of the hard work iw already done (syndication to a bunch of silo APIs, web interface, lots else)
#
[snarfed] the only work to do is writing the micropub to granary wrapper
#
[KevinMarks] isn't that effectively what kyle did?
#
@kevinmarks ↩️ why does that need a special kind for XR? Use IndieAuth or something else built on OAuth. (twitter.com/_/status/1358946646407729156)
#
[snarfed] yup, except his was standalone, didn’t use granary
#
[snarfed] i just meant bridgy is one path if we want an equivalent to silo.pub that’s maintainable and has clear ownership. not the only path
#
[KevinMarks] I thought he used the granary libraries
#
[KevinMarks] Interesting - DNS over Tor - thats a different decentralized approach https://alecmuffett.com/article/14188
#
Loqi [alecm] WANTED: public review of the v2.0 draft of “A Year of DNS over HTTPS over Tor” ; includes absolute and comparative performance measureme...
themaxdavitt, stacktrust, jolvera and [Tim_Nolte] joined the channel
#
jacky Secure Scuttlebutt << https://gitlab.com/ahau/ssb-crut/
#
Loqi ok, I added "https://gitlab.com/ahau/ssb-crut/" to the "See Also" section of /Secure_Scuttlebutt https://indieweb.org/wiki/index.php?diff=74536&oldid=69175
#
jacky very handy if anyone gets curious
[schmarty] joined the channel
#
[schmarty] jacky: ooh i hadn't thought about playing with ssb at that level. i had a Patchwork profile set up a couple of years ago
#
jacky it's something I've been wanting for
#
jacky it's really the only thing stopping a bridge tbh
#
jacky [Rabble] actually put me onto it
gRegorLove joined the channel
#
[schmarty] dang i really rely on github stars to bookmark projects
#
jacky hahaha
#
Loqi nice
#
[schmarty] looking at this gitlab project thinking "oh well i will never find this again"
#
jacky I have to bookmark it in my browser
#
[schmarty] resorting to pinboard (which i will forget to check later)
#
jacky haha
[chrisaldrich], ShadowKyogre, gRegorLove, Saphire, pmlnr, genehack, mitchell, jimpick and mattl joined the channel; pmlnr left the channel
#
@XabCorinti #100DaysofCode R3|D9 Still fighting with webmentions and bridgy https://www.andreacorinti.com/posts/1-web-dev-log/ (twitter.com/_/status/1359114143219990530)
petermolnar[xmpp, petermolnar_, Artea, shoesNsocks, [Rose], KartikPrabhu and jolvera joined the channel; petermolnar_ left the channel
#
GWG Anyone have any strong feeling about iso3166-2 codes?
[KevinMarks] joined the channel
#
[KevinMarks] mostly useful, easy to turn into flag emoji
#
GWG [KevinMarks]: How about region level?
#
GWG https://en.m.wikipedia.org/wiki/ISO_3166-2:GB
#
[KevinMarks] UK ones look OK
#
GWG [KevinMarks]: I am having problems with standardization of output from reverse geocoding to tag with the right code
gRegorLove joined the channel
#
@aquicarattino Reading @Mappletons note on transclusions (https://maggieappleton.com/transcopyright-dreams) and it made me immediately think about WebMentions. What would happen if the scope is limited to a group of people, for instance knowledge generation in companies? Initial thoughts: https://www.aquiles.me/transclusion/ (twitter.com/_/status/1359203479869403139)
[tantek], [jeremycherfas], [arush], [snarfed], shoesNsocks, [KevinMarks] and [tonz] joined the channel
#
@raymondcamden Got the final bits of "Disqus to static HTML comments" done for my blog at lunch. Webmention support will come next week. Tonight I'll write about how I did it. Or I'll watch TV. Or both. Tune in to find out... (twitter.com/_/status/1359240392407924742)
[Rose] joined the channel
#
[Rose] Does anyone have experience migrating from WordPress to Jekyll? The importer is erroring
#
GWG [Rose]: We'll miss you
nertzy and Danielstaleiny joined the channel
#
[Rose] Well this is an experiment. But I’ve been struggling massively with WordPress
#
GWG [Rose]: I can understand that
#
GWG Can I entice you with a cool feature?
#
[Rose] Unlikely, not for this project anyway
#
GWG Oh well.
#
GWG https://david.shanske.com/location/de/be/berlin/
[chrisaldrich] and jamietanna joined the channel
#
jamietanna [Rose] I've done it before, but it wasn't a complex site, so not sure if I'll be able to help much?
#
[Rose] I just managed it with exitwp, I think.
#
jamietanna woop!
#
[Rose] Took some digging around and deleting some lines in the XML
#
[Rose] But importing things from the DB didn’t work, which is the standard Jekyll importer
#
jamietanna oh that's a pain - but you managed to at least get it all?
#
jamietanna Back to the Micropub for syndication - how would that work re access tokens? When the app sends a Micropub request to i.e. post a note, would the Micropub server send the access token through to the bridge that syndicates to Twitter? If so, how would it know which IndieAuth server to verify the token against?
#
jacky I think this is _all_ up to you tbh!
#
jacky like I was still fleshing this out and I was thinking this might be a good case for AutoAuth
[pfefferle] joined the channel
#
jamietanna[m] Hmm I need to look into AutoAuth again
#
jamietanna[m] And see if maybe there's anything in oauth2 that we can use
#
jamietanna[m] I'm interested in looking into this as a thing as I've thought about it on and off for a while and would like to have an idea of how to solve it for a central service
#
jamietanna[m] I guess in the Micropub use case it doesn't have to be a user access token it could be a token issued by the Micropub server, which when redeemed at the micropub server (which could then be a basic IndieAuth server) would allow verifying the token's `me` as the user
#
jamietanna[m] Or maybe we don't need that - as the user is already known, their auth server would be too, so as long as the `me` is sent too, that should be fine? I'll work through some thoughts tomorrow
#
jacky yeah, many options
#
jacky It could also be a bit more 'loose' and you can make a 'unguessable' URL for posting