#meta 2020-01-26
2020-01-26 UTC
# 
@bixtweets I’ve changed my mind: I no longer want RSS readers from which you can reply to blog posts via webmention. It completely violates my contention that the social media has too little friction; it’s not a flaw an indieweb blogosphere software ecosystem ... https://bix.blog/2020/01/25/ive-changed-my.html (twitter.com/_/status/1221246451864547329)
# 
@vincentlistens Migrating my blog from Jekyll to Eleventy is going well. I finally have all the #indieweb functionality working. In to the home stretch now. I will have to make tweaks to my Indieweb server to accommodate the new build but otherwise happy!
https://vincentp.me/notes/2020/01/26/16 (twitter.com/_/status/1221275323846873090)
thesage1014Disco joined the channel
# 
@brianwisti ↩️ @ForTheJim but I'm really tempted by the idea of static site as application. Could make a lot of IndieWeb stuff on my list *much* easier. (twitter.com/_/status/1221307488798044160)
[Michael_Beckwit and [Marlin_Forbes] joined the channel
# 
@JamieTanna ↩️ It can also make some of it harder, too! My site is a static Hugo site, but for some of the IndieWeb stuff I either need to add client-side JS or write separate services that can run to ie send Webmentions. It definitely works, but is a bit more work as… https://www.jvt.me/mf2/2020/01/bpq5i/ (twitter.com/_/status/1221354767559090176)
# @brianwisti ↩️ Been following your experiences tying indieweb together with a Hugo site. Been pondering gatsby + some serverless, but will likely just throw a microservice next to the current site. (twitter.com/_/status/1221358030463201285)
[KevinMarks], [jgmac1106], Naptra, [tantek] and [David_Bryant] joined the channel
# 
@jgmac1106 ↩️ I was supposed (picked up client work, need the scratch) to finish up my case studies in between break, using innovation systems as a lens for #IndieWeb and #ds106 but want to do an authoethnography as we define agentive apprenticeship, (https://quickthoughts.jgregorymcverry.com/s/fNjwy) (twitter.com/_/status/1221435426776502272)
[jeremycherfas], [jgmac1106], aaronpk, [LewisCowles], [Michael_Beckwit, Nuve, [tantek] and [schmarty] joined the channel
# 
[schmarty] !tell aaronpk: got an issue w/ sharing yesterday's HWC NYC photo on https://events.indieweb.org/2020/01/indieweb-meetup-nyc-3Ss2mFU4CVfj - maybe stacked image proxy URL issues?
# [schmarty] oops punctuation
# [schmarty] oh, maybe it's okay. thanks, Loqi.
[KevinMarks] joined the channel
# [schmarty] probably not without rewriting the imageproxy 😞
# 
willnorris Hmm, interesting. Never tried that
# [schmarty] aaronpk: any way for me to manually update the photo URL on events.indieweb.org?
# [schmarty] lol i'd have to rewrite that post to dodge my image proxying 😛
# [schmarty] it's a weird case to be sure
# [schmarty] haha 😅
# [schmarty] thanks! looks great!
# [schmarty] i mean, it loaded great. i've definitely taken better photos. 😆
# [schmarty] i think as long as there's a working history that seems reasonable.
[AlisonW] and [fluffy] joined the channel
[snarfed] joined the channel
# willnorris recursive image proxying seems to work fine for me: https://imageproxy.willnorris.com/fv/https:/imageproxy.willnorris.com/200x/https:/willnorris.com/2013/12/small-things.jpg
# willnorris imageproxy always treat the first path segment as the options, and everything after that is the URL... it doesn't try to parse anything after that
# willnorris I think that's my nginx config that's stripping the double slashes. shouldn't matter, I don't think
# willnorris err, no not nginx. This is now running Google Cloud Run, so maybe they're canonicalizing the URL
# willnorris when I was running behind nginx, I do remember it doing the same
# 
aaronpk schmarty's doesn't use signatures so his is able to handle nested ones fine too https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://imageproxy.willnorris.com/fv/https:/imageproxy.willnorris.com/200x/https:/willnorris.com/2013/12/small-things.jpg
# willnorris okay, then it's almost certainly the signature verification that's failing... I'm getting the same error as you (https://imageproxy.willnorris.com/1240x0,sEN6q_64JgZcsj-Ah4HuooRg9IE6CdRHcKuBMdYsfBm0=/https:/res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https:/media.martymcgui.re/90/ac/63/84/4d6f56754094ad8373dcba649e54f210450514b33522e223def0f60f.jpg)
# willnorris and I do suspect it may have something to do with the double slashes, though I'm not completely sure.
# willnorris okay, I got it working on my instance, and it didn't require any code changes... https://imageproxy.willnorris.com/1240x0,selj-PBjr6SIn7-n3HdaDymV_fJFbiG5bBVAhBZi9iyw=/https:/res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https:/media.martymcgui.re/90/ac/63/84/4d6f56754094ad8373dcba649e54f210450514b33522e223def0f60f.jpg
# willnorris aaronpk: what are you using to generate your signatures?
# willnorris the included imageproxy-sign command, or some of your own code?
# aaronpk stolen from your php example https://github.com/aaronpk/Meetable/blob/master/app/Event.php#L46
# willnorris this is likely an issue with the option canonicalization (https://github.com/willnorris/imageproxy/blob/master/docs/url-signing.md#signing-options)
# willnorris hmm...
# willnorris okay, definitely a result of the forced canonicalization that is happening inside of Go's net/url library. I had worked around it in most places, but this is a new one
gRegorLove joined the channel
[KevinMarks] and mblaney joined the channel