LoqigRegor: Zegnat left you a message 3 days, 6 hours ago: I filed a PR for using the newer TypeScript parser, do have a looksy. I think if we want to clean up the JS microformats.io version it would be swell to bring this along. https://github.com/microformats/microformats-parser-website-node/pull/5
@miklbTumblr iOS app is woefully too aggressive with caching. Had to restart the app to see my posts from this morning. Also not a fan of it not detecting and auto-hyperlinking full URLs. I really need to write some HTML and markup the microformats... https://tmblr.co/Z3GGbyd5Rehvau00 (twitter.com/_/status/1604900150740193290)
[will]bah, all of the *.microformats.io servers have the same CORS issue. We'll have to update those individually. They seem to be still running on Heroku... did someone upgrade those to a paid heroku plan since the free plans went away recently? I know [shaners] had originally set that all up, but was looking to hand it off some time ago. Who manages it now?
[will]btw, I bought microformats.dev a few years ago in case we wanted to get off of the .io ccTLD, and since it made sense for library development like this
[will]sounds good. I think we should move mf2compare to microformats.io/compare, and then we can setup CORS headers to just allow microformats.io / microformats.dev .
Zegnat[jacky]: when I check jacky.wtf/about locally I see bday working. So that it the old node parser not supporting something that the new typescript parser does. IPA is still empty, but is empty in the PHP parser too
gRegorThe u-sound on the <audio> element isn't finding a src attribute, so it's finding the textContent (empty) and normalizing that with the current URL, so that's why that parses as "https://jacky.wtf/about"
Zegnat[jacky]: did you mean to redeploy the main branch to Heroku, or the next branch to test the swap of the parser? I think you did the former. So the merged PR is, AFAIK, not actually visible for anyone anywhere