#petermolnar!tell snarfed I've merged your changes into mine in https://github.com/petermolnar/webmention-tools but I don't think my additional lookups are needed for the main branch; if you have time to check them though, and you think it would worth having only one of these, please tell me
#tantekvoxpelli: if you find anything that can be improved with mf2 parsing (with backcompat) of "classic" WordPress sites or themes, please make a note of it!
#tantekmaybe even file an issue if you has a specific suggestion
#voxpellitantek: can't think of anything missing in the parse, feels like one would have to try it in some IndieWeb clients to see for sure
#tanteke.g. if you have two different tables to update
#tantekyou have to your own "locking" (transaction)
#tantekso they're not inconsistently updated by two different processes
#tanteklike a "posts" table and a "media" table :P
#aaronpkthe only similarity this problem has with a database is if i was storing all my post data in a single column
#aaronpkwhich means a potential file based solution to this is to separate out my syndication URLs into different files so that I can write more than one at a time without clobbering them
#aaronpkyeah i don't know how i want to solve this
KevinMarks joined the channel
#tantekdo you have different syndication processes? why?
#tantekseems like one "background" syndication process would be enough
#aaronpkwell what happened here was: 1) I posted from a micropub client that told my website to syndicate to facebook. That returns immediately so the client thinks it's "done". then 2) the client then syndicates it to a couple other places, and makes a micropub "edit" request to update the post to add the new syndication URLs that it created. 3) the micropub server finishes posting to facebook, and then
#aaronpk"updates" the post itself, clobbering the edit
#aaronpki suppose i could make my micropub endpoint refresh the file from disk after it finishes its own syndication before writing the syndication URL
#tantekseems like the micropub server needs to use a request queue, and process them fifo
#tantekeach request needs to be handled atomically, with all file edits completed / closed, and zero state kept between (file has to be re-opened, re-read between requests)
#aaronpkthis doesn't solve the underlying problem, i still have to run only one background process
#aaronpkbut this refreshing thing would be a good idea regardless
#tantekright, typical way this is solved is to have one *storage* process that everything else talks to, and only that storage process gets to read/write to the files
#gRegorLoveWe're nestled between the bay and the start of the mountains, so there's a lot of forests and hiking. It's gorgeous here. Quite a few breweries that I understand are good (not a beer fan myself), we have a nice waterfront park and boardwalk. Quite a few music venues, an improv theater (Ryan Stiles from Whose Line Is It Anyway?)
#gRegorLoveSan Juan Islands are across the bay, so a ferry ride away. I need to explore them more.
#gRegorLoveDepending on your level of interest in LinuxFest, you could skip some of it and make a long weekend in SEA. I probably wouldn't be opposed to driving down there.
#voxpelliI like the idea of a plugin, less likely for newcomers to mess up the classes when they hack their blog themes to look one way or another
#pfefferlevoxpelli hentry on the article as default?
#voxpellipfefferle: default could probably be the aggressive mode, and point people who feels like their theme gets broken to toggle the compatibility mode to scale back
#GWGThe existing plugin could use a refresh though
#GWGI think tantek's suggestion it transfer to the Indieweb repository is a good idea. It is like the Indieweb plugin in that it is a community need
#LoqiXRay is an open source API that returns structured data for a URL by parsing microformats and following other indieweb algorithms, and is part of the p3k suite of applications https://indieweb.org/XRay
#loqi.meedited /tinbox (+413) "tantek added "add to http://microformats.org/wiki/h-feed new "Backward Compatibility" section with subsections "Publisher Compatibility" and "Parser Compatibility", documenting classic hAtom "hfeed" classes for publisher compat, and the corollary for" (view diff)
#Loqih-feed is a microformats2 draft for marking up a stream or feed of h-entry posts, like complete posts on a home page or archive pages, or summaries or other brief lists of posts.
h-feed is the microformats2 update to hAtom's "hfeed".
Per CC0, to th...