sknebelgiven the recent wiki outage, should we setup a mirror for the mf-wiki too? (like the indieweb wiki content files are copied to the indieweb github org). or is at least someone maintaining an offline copy? (aaronpk?)
ZegnatFiling PRs is nice because you can discuss and review a change before committing it. While the wiki takes a commiting first and then reviewing the revision sort of flow.
ZegnatI wondered about putting the text copy of at least the mf2 parsing spec in the parsing spec github repo. That might also make it easier to link to specific points during issue discussion, and changes could be filed as PR.
barpthewire, nitot, [kevinmarks], [jeremycherfas] and [sebsel] joined the channel
ZegnatFor my implementation in php-mf2 I replaced all “textContent” requests in the spec with one and the same algo. The question being: was that right? For things like the very final step in u-* parsing, it might be better to stick with raw textContent.
chrisaldrich, adactio and tantek joined the channel
[jgmac1106]need a reverse parser where I can copy an APA citation from Google Scholar and have it spit out the correct mf2, so somebody fly around the earth like Superman and make thigns work backwards. Proper APA citation and h-cite markup is a bear
[jgmac1106]be really cool if you coudl get h-cite listed on the bottom of the citation modal in Google Scholar...but I am sure those companies pay big bucks to get there
[jgmac1106]@zegnat I may just try to map it out using a workflow of going to Google scholar>copying the BibTex and throwing that into a modal with a selection for citation style. AssumingI would just need to make the proper mf2 template for each style.
Zegnattantek: I think the consensus between sknebel, ancarda, and me, is that the theoretical problem of thundering herd is always going to exsist for something like readers. If everyone hosts their own reader, once you send a WebSub ping into the world that there is a new post, they are all going to wake up and come at you.
ZegnatBut there are several technical mitagations we could think of. Usual caching, of course. E.g. making your website resist DaringFireball/Slashdot. Another thing that would be interesting is to make readers not respond to a ping immidiately (thus staggering the load from the requester side), but you can never be 100% sure that every reader is doing that.
Zegnatancarda had the interesting idea of also not doing a simultaneous websub ping to everyone. If you yourself control the websub hub, you can send the ping staggered to e.g. 5 subscribers at the same time and spread the load even further.
[jgmac1106]These are images embedded in my posts, technically a repost but really just an image that I dig that is also openly licensed. Just pull it in from Flickr API using Alan Levine's tool. I think I will be able to maker an mf2 version
[jgmac1106]I think in my context yeah I would use u-feature as it it kind of the "hero" image of the page...especially if SM treats that like a twitter card I would add to my header