#dev 2021-08-20

2021-08-20 UTC
Seirdy and KartikPrabhu joined the channel
#
[tantek]
snarfed++ good read
#
Loqi
snarfed has 23 karma in this channel over the last year (47 in all channels)
jacky joined the channel
#
@webology
@easyaspython would django-webmention be a good fit for a website like Django Packages? I haven't looked the protocol for a while, but I keep stumbling on websites that use webmentions and I was curious.
(twitter.com/_/status/1428523541243310080)
jacky, Seirdy, hendursa1, tetov-irc and nertzy joined the channel
#
capjamesg[d]
Quick question about the Micropub media endpoint test suite. The last step is " The URL exists and has the expected content type (image/jpeg)" My blog takes a few minutes for an image to show up since Jekyll needs to do its thing. Is there a way that the test suite could check for the image on request?
#
capjamesg[d]
Rather than doing it automatically.
#
capjamesg[d]
I can see the image the endpoint created. The test suite doesn't verify it though.
jacky and [manton] joined the channel
#
[manton]
[capjamesg] Not sure if this will help you, but if you’re writing your own Micropub endpoint anyway, one thing I do in Micro.blog: when an image is uploaded, I copy it to the web server right away rather than waiting to run it through Hugo first.
jacky joined the channel
#
sknebel
given it's not unlikely to cause problems if the image isnt there, I dont think thats something where the test suite should give leeway
#
sknebel
if the spec doesnt explicitly allow that case
#
sknebel
I guess it could have a "check again now" button for that case, you could open an issue about that
#
nolith
I have the same problem as capjamesg[d] I was thinking of moving my media into a dedicated hosting to speed up uploads, but I never found enough motivation on doing it
#
nolith
I think it boils down to https://micropub.spec.indieweb.org/#response-2 the medias endpoint do not allow you to return a 202 accepted like the micropub basic endpoint
#
sknebel
pretty much, yes. which would be a fine issue to raise against the spec
#
capjamesg[d]
sknebel In my case, the content and image will be available at pretty much the same time, give or take a few seconds.
#
capjamesg[d]
So to the end user whether or not the image is available straight away or after Jekyll builds and the post with which the image is associated there is not difference.
#
capjamesg[d]
I would love a "check again now" button on the test suite.
#
sknebel
it is relevant if the client expects your endpoint to conform to spec and actually serve the image
#
sknebel
e.g. because it wants to show a preview
#
nolith
sknebel: I'm opening an issue on the spec repo
#
sknebel
nolith++
#
Loqi
nolith has 3 karma in this channel over the last year (9 in all channels)
shoesNsocks1 joined the channel
#
nolith
sknebel: https://abisso.org/stream/2021/08/20/micropub-async-media/ I almost syndicated it twice. I forgot that I have github (via brid.gy) as part of my CI
#
Loqi
[Alessio Caiazza] Media endpoint should allow async processing
hendursaga, gRegor, ben_thatmustbeme and gRegorLove_ joined the channel
#
capjamesg[d]
nolith How did you respond via your website?
#
capjamesg[d]
Or did you respond on GitHub and have the response syndicate to your site?
#
sknebel
capjamesg[d]: through bridgy
#
capjamesg[d]
sknebel How do you create the original post that shows all the commits / issues etc.?
#
capjamesg[d]
I know that bridgy sends me webmentions with post contents. Do I need to create that first thread?
#
Loqi
[Alessio Caiazza] Media endpoint should allow async processing
#
Loqi
[Alessio Caiazza] Media endpoint should allow async processing
#
sknebel
sigh, Loqi
#
sknebel
^^^ bridgy if setup to publish to github sees the "reply" to the issue list and thus knows where to file the issue
#
sknebel
bridgy docs for details on how it works exactly
#
sknebel
(I hope I'm understanding your question correctly)
#
[snarfed]
thanks sknebel! I think you are
#
[snarfed]
capjamesg bridgy only sends you github comments and reactions, not original issues
jacky joined the channel
#
capjamesg[d]
sknebel Thanks!
#
capjamesg[d]
And thanks [snarfed]!
#
capjamesg[d]
Do I need to link to my GitHub profile in my h-card for bridgy to work?
#
capjamesg[d]
I got a " Could not find GitHub account for jamesg.blog. Check that your GitHub profile has jamesg.blog in its web site or link field, then try signing up again." message 😦
Rattroupe joined the channel
#
Rattroupe
"My blog takes a few minutes for an image to show up..." I have kind of a similar issue with my blog, bridge, and webmentions
#
Rattroupe
Bridgy won't accept a publish link if the article isn't there yet. So I have to push the article to my blog, then run the webmention process, then push it again
#
Rattroupe
I understand why it does that but it's annoying
#
sknebel
capjamesg[d]: might be http/https confusion on the link on github
#
[snarfed]
capjamesg the opposite, your GH profile (eg https://github.com/snarfed/ ) needs to link to your web site
#
[snarfed]
capjamesg oh, sorry, that's the error message from a publish attempt. That means you need to sign up for Bridgy GitHub on https://brid.gy/
#
[snarfed]
(you need to re-auth with every different silo you want to use)
#
[snarfed]
ah, looks like you are signed up. then yes, once your GH profile links to your web site, you'll want to re-auth
#
[snarfed]
unrelated, Bridgy is roughly halfway through a huge migration from webapp2 to Flask. Big project, but pretty straightforward, nothing too tricky or unusual. Contributions are welcome! https://github.com/snarfed/bridgy/issues/1037
#
Loqi
[snarfed] #1037 Port from webapp2 to Flask
jacky joined the channel
#
[schmarty]
snarfed++
#
Loqi
snarfed has 23 karma in this channel over the last year (47 in all channels)
KartikPrabhu and tetov-irc joined the channel
#
aaronpk
seriously considering making an IndieAuth PAM module for my servers to be able to SSH into them using IndieAuth...
#
GWG
That would be useful
[Gabriele_Girel] and westie[d] joined the channel