#dev 2019-07-15

2019-07-15 UTC
KartikPrabhu, BenLubar, [fluffy], [tantek], [xavierroy], kanej[m]2, Lilz|BetaMe[m], lyon[m], cameronbrown[m], phynite[m], myfreeweb, plindner[m], JeffMaherVegas[m, pierreboc[m], vasa[m], Tianyi[m], M[AXEL]Darr[m], Nebulous[m], iiogama[m], mattl, Kongaloosh, jgmac1106[m], swedneckpermaweb, eddy[m], grantcodes[m], Swedneck_, carsonfarmer[m], fozzie[m], jenncloud[m], drshamoon[m], omz13[m], jee[m], Keegen[m], romaric[m], mikeal[m], drbh[m], Lolicon[m], andrewxhill[m], npfoss[m], discord[m], freethinkingaway and skippy joined the channel
[tonz] joined the channel
#
[tonz]
In WordPress all webmentions end up in the same moderation queue as local comments, so maybe tying it into your comment flow is an option.
[grantcodes] joined the channel
#
[grantcodes]
!tell jacky updating replies should already be technically possible with micropub updates on the `comment` property. But I think it would be much more complicated - both UI and tech wise - than editing most other micropub properties.
#
Loqi
Ok, I'll tell them that when I see them next
discord[m], swedneckpermaweb, Kongaloosh, freethinkingaway, drbh[m], jenncloud[m], eddy[m], fozzie[m], Keegen[m], romaric[m], Lolicon[m], grantcodes[m], jgmac1106[m], drshamoon[m], npfoss[m], andrewxhill[m], Swedneck_, mattl, jee[m], omz13[m], mikeal[m], carsonfarmer[m], Nebulous[m], lyon[m], iiogama[m], phynite[m], Tianyi[m], M[AXEL]Darr[m], plindner[m], vasa[m], JeffMaherVegas[m, Lilz|BetaMe[m], kanej[m]2, pierreboc[m], cameronbrown[m], myfreeweb, [tantek] and [jgmac1106] joined the channel
James|Colony[m], gxt and uDmThnVng[m] joined the channel
#
@petermolnar
↩️ @Tautvilas @Tautvilas #indieweb also has non-clumsy login-with-domain solution: https://indieweb.org/IndieAuth
(twitter.com/_/status/1150725473158205446)
gxt, eli_oat and [jgmac1106] joined the channel
#
sknebel
!tell [Rose] some mentions of a Reddit setup here: https://danq.me/2019/07/15/danq-ecosystem/
#
Loqi
Ok, I'll tell them that when I see them next
#
Loqi
[Dan Q] DanQ.me Ecosystem
[schmarty] and [Rose] joined the channel
#
[Rose]
Hello.
#
[schmarty]
o/ hello!
#
@LaravelDepot
http://murze.be: ★ How to add webmentions to a Laravel powered blog https://t.co/1cXADI2hcX
(twitter.com/_/status/1150781218612482048)
[kimberlyhirsh] joined the channel
#
sknebel
hi [Rose]! just wondered that I hadn't seen you in a while :D
#
@phpdeveloper
http://murze.be: ★ How to add webmentions to a Laravel powered blog: The comment section of this blog used to b...: https://fdlr.io/bv6
(twitter.com/_/status/1150782074896494592)
#
[schmarty]
unicode 😬
#
[Rose]
Hehe, broken ankle, parents visiting, hospital trips, not a lot of time has been available for writing code sadly.
#
[Rose]
(Plus the wrist muscles didn't like typing for quite some time. Now it's just my thumbs which dislike typing, and who needs spaces?)
#
sknebel
[Rose]: assumed something like this. Hope you're feeling better now overall
#
[schmarty]
!tell [mJordan] looks like your h-feed is working now! aaronpk's new "feed preview" feature on monocle has been really helpful to me when debugging html+mf2 feeds. https://monocle.p3k.io/preview?url=https://mjordan.codes/blog/
#
Loqi
Ok, I'll tell them that when I see them next
[mJordan] joined the channel
#
[mJordan]
[schmarty] sweet! I'm slowly figuring it out. Thanks for the tips 🙂
leg joined the channel
#
@luiscbrenes
http://murze.be: ★ How to add webmentions to a Laravel powered blog http://dlvr.it/R8S70D
(twitter.com/_/status/1150800966934904832)
[tantek] and [snarfed] joined the channel
#
[schmarty]
danq++ wowzers
#
Loqi
danq has 1 karma over the last year
#
jacky
!tell [grantcodes] wait do you mean using MY micropub server to modify the visibility of a reply I've replied? If so, that's interesting - my server wouldn't be able to handle that
#
Loqi
Ok, I'll tell them that when I see them next
#
Loqi
jacky: [grantcodes] left you a message 8 hours, 33 minutes ago: updating replies should already be technically possible with micropub updates on the `comment` property. But I think it would be much more complicated - both UI and tech wise - than editing most other micropub properties.
[grantcodes] joined the channel
#
[grantcodes]
Well I think you should be able to update your content and moderate comments using the existing API.
#
[grantcodes]
But it would probably be difficult. Especially if you're not storing everything in pure mf2
#
[grantcodes]
*mf2 json
gRegorLove and dougbeal|mb1 joined the channel
#
gRegorLove
Some Bridgy URLs (likes, it appears) are redirecting to the twitter.com URL, e.g. https://brid-gy.appspot.com/like/twitter/gRegorLove/1148751489394851840/37519892
#
[snarfed]
gRegorLove yes! all ideally. i added that a bit ago, intentionally. is it causing a problem?
[benatwork] joined the channel
#
gRegorLove
Ah, I follow meta redirects I think
#
aaronpk
oh no lol
#
gRegorLove
Hm, maybe not.
#
[snarfed]
"I" meaning your wm receiver?
#
gRegorLove
Yeah. I think I spoke too soon though. I'll dig into it more.
#
[snarfed]
lots of discussion on whether this is ok, and whether wm receivers should follow meta redirects, in the IRC log links in that commit. https://chat.indieweb.org/dev/2019-04-11#t1555004634348000 , and esp https://chat.indieweb.org/dev/2019-04-16#t1555440757959400
#
Loqi
[snarfed] i have a narrow niche use case for the proxy html+mf2 pages that bridge services like bridgy and bridgy fed render for silo posts
#
[snarfed]
specifically, aaronpk said "i'm not sure about the meta redirect question," "but a JS redirect seems like a safe alternative," which i foolishly ignored
#
[tantek]
Lolwut (out of context reaction)
[KevinMarks] joined the channel
#
[tantek]
let's not make WM receivers follow meta redirects please
[aarongustafson] joined the channel
#
aaronpk
oh boy, bets on whether google even looked at all the fragmention work? https://github.com/bokand/ScrollToTextFragment
#
Loqi
[bokand] ScrollToTextFragment: Proposal to allow specifying a text snippet in a URL fragment
#
aaronpk
ooh hey they did link to it in the "related work" section!
#
Loqi
[snarfed] #253 support HTML meta http-equiv=refresh redirects
#
[snarfed]
hmm. the language there is "MUST fetch the target URL (and follow redirects [FETCH])"
#
[snarfed]
and the language for receiving is "MUST perform an HTTP GET request on source, following any HTTP redirects"
#
[snarfed]
so "HTTP" is the distinction btw discovery and receivers, and is meant to be deliberate?
#
[snarfed]
might be worth elaborating, but you and aaronpk know that balance in specs better than me
[fluffy] and leg joined the channel
#
[tantek]
snarfed, short answer, if you follow the [FETCH] ref, it provides more precision around how to handle HTTP redirects
#
[tantek]
I believe the language for receiving should have also said "follow redirects [FETCH])
#
[tantek]
which both end up being "handle HTTP redirects as defined more precisely by Fetch"
#
[tantek]
either way, no mention of any meta tags
#
[tantek]
probably worth adding to an FAQ
#
[tantek]
what is webmention FAQ
#
Loqi
The Webmention FAQ is for documenting frequently asked questions about Webmention and their answers https://indieweb.org/Webmention-faq
#
[snarfed]
thanks! sounds good
#
[tantek]
aaronpk, do you think https://github.com/snarfed/bridgy/issues/253 is worth opening an issue on the Webmention spec for? Just to clarify or at least put in the FAQ (which doesn't currently mention the meta tag)
#
Loqi
[snarfed] #253 support HTML meta http-equiv=refresh redirects
#
gRegorLove
ended up being a cron issue, not following meta redirects
[KevinMarks] joined the channel
#
[snarfed]
gRegorLove++
#
Loqi
gRegorLove has 13 karma in this channel over the last year (83 in all channels)
#
@mentallion
How to add webmentions to a Laravel powered blog #News http://dlvr.it/R8T54N #php #laravel https://t.co/YOh5eYzzYM
(twitter.com/_/status/1150896605337227264)
#
GWG
I have many things to think about.
#
GWG
I feel the desire to talk about some Indieweb concept right now
[benatwork] joined the channel
#
GWG
I am still thinking about h-feed
#
GWG
Reading tantek's commentary on determining the primary h-feed
[snarfed] joined the channel
#
GWG
Is there any grounds to change it from you can optionally use h-feed to we recommend you use h-feed?
#
GWG
I am just wondering what the criteria is for recommending people make my consumption easier
#
[snarfed]
it's a wiki, just go ahead and edit
#
GWG
I know
#
GWG
I was just asking for feedback
#
GWG
Should it be a recommendation? I think optional suggests it isn't widely adopted as a thing
#
GWG
I would like to improve h-feed
#
GWG
When did Firefox remove native RSS support? Probably should be on that page too
#
GWG
December.
#
[tantek]
"easier for consumers" is problematic wording
#
[tantek]
"consumer" usually means a person *consuming* some capitalist good or service / experience
#
GWG
To make your intent more explicit?
#
[tantek]
in that regard, the statement is inaccurate and doesn't convey what you intend
#
GWG
The opposite of a publisher is?
#
[tantek]
try to use "consuming applications" instead as that should be sufficiently precise to convey the meaning you want
#
[tantek]
GWG, yes opposite of a publisher is a reader
#
[tantek]
which can refer to software or people, and in typical meaning (non-jargon), is interpreted as a human
#
[tantek]
so if you want the more obscure (tech jargon) meaning, you should use a more precise term / phrase
#
[tantek]
that's the first problem
#
GWG
Is the feed page a good page to discuss my issues or brainstorms on h-feed or elsewhere?
#
GWG
I always wonder if I should write on my site first
#
[tantek]
sure! /feed#Brainstorming subsections, go for it
#
[tantek]
I mean yes if you feel like it
#
[tantek]
either is ok, don't feel obligated either way
#
[tantek]
even if we fix that phrase to: "easier for consuming applications" it still has a problem
#
GWG
I am still contemplating what we discussed at IWS about better feeds
#
GWG
Yes?
#
[tantek]
which is that it fails to actually provide a self-interest appeal to the person you want to take the action
#
[tantek]
why should a publisher care one second about making things "easier" for someone/something else?
#
GWG
I assume a publisher wants me to read their work
#
[tantek]
that's better than "easier"
#
[tantek]
there is benefit to the publisher, it's just that "easier for the consuming application" fails to convey that benefit
#
GWG
So the motivated self interest is better display in readers
#
[tantek]
yes, that's better than "easier"
#
[tantek]
"better display" is better than "easier for [the other guy]"
#
[tantek]
even better would be something more specific than "better display" because the next question is better display how?
#
GWG
Also, look at tantek.com...if i was less intent on consuming your site, I might have given up, for example
#
[tantek]
GWG, my site is not the best example for documentation because it is 1) a special case, 2) likely an edge case since I'm potentially experimenting with stuff, 3) very likely to change as I iterate given the feedback loop(s) in the community
#
GWG
On the other hand...if I really want to read different sites, I should be prepared for different publishing
#
[tantek]
GWG, one example specific advantage could be, give your feed a specific name by marking it up explicitly as an h-feed with its own p-name
#
GWG
And explicit author as opposed to individual ones
#
[tantek]
I don't think we have h-feed p-author worked out anywhere so no I wouldn't pitch that
#
[tantek]
or do we?
[fluffy] joined the channel
#
[tantek]
a-ha another one, give your feed a representative icon with the photo
#
GWG
The danger of implied over explicit is that I will misunderstand your intent
#
[tantek]
those are all good specific reasons to use explicit markup
#
GWG
I am not advocating for mandatory.
#
[tantek]
there is no implied feed name or icon for example
#
GWG
Yes
#
[tantek]
it's not mandatory and that's clear
#
GWG
And a feed doesn't need to be a set of posts
#
[tantek]
you can say, you should markup your feed explicitly with h-feed so that you can explicitly express at least a name and icon for the feed, and the author for the feed as a whole
#
[tantek]
something like that
#
GWG
I think we established recently that people have feeds of h-cards and h-events
#
GWG
So I probably should note that while it is traditionally posts, it doesn't have to be
#
GWG
We have enough publishers of that I should document
#
GWG
Also should add an example of a marked up h-feed
#
GWG
With all those properties on the h-feed page
#
[tantek]
while it may make sense to try to note exceptions in a definition or summary, it tends to be both confusing and counterproductive to understanding
#
[tantek]
it's better for a definition to capture typical meaning / use, and then further description to broaden that as necessary