#microformats 2022-12-19

2022-12-19 UTC
[iambismark], ur5us, aaronpk, sp1ff`, ur5us_ and tiim joined the channel
#
@t
upgraded my @BBEdit to v14. Thanks https://Barebones.com for a smooth & solid text editor for decades. Its HTML validator checks a/area/link rel for XFN values like rel=me (since 9.6.2). Are there #microformats2 Clippings? Perhaps a holidays project,... https://tantek.com/t5NR1
(twitter.com/_/status/1604776792254185472)
#
[tantek]
if anyone is interested in collaborating, there's some prior notes on https://microformats.org/wiki/editors
#
Loqi
[preview] Joe Dakroub
[fluffy], [arush], [marksuth], [denschub] and tiim joined the channel
#
IWDiscordRelay
<j​acky#7226> I'll merge and eyeball this deploy in about 14 minutes (10:30 EST) https://github.com/microformats/microformats-parser-website-node/pull/5#pullrequestreview-1223061467
#
Zegnat
Nice one [jacky]! I will rebase my other PR so it will be without conflicts again
#
Zegnat
(Done)
#
[jacky]
oh interesting, my birthday (or bday), ipa and sound values are all empty https://microformats-parser-node.herokuapp.com/?url=https%3A%2F%2Fjacky.wtf%2Fabout
#
[jacky]
hmm this is going to lead into a rabbit hole for me lol
#
[jacky]
but it _does_ make me want some sort of tool that run across the parsers and get a unified result
#
[jacky]
I _vaguely_ remember someone having that here
gRegor joined the channel
#
Loqi
gRegor: 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
#
[jacky]
willnorris++
#
Loqi
willnorris has 1 karma in this channel over the last year (2 in all channels)
#
[jacky]
hmm something about that does not work well with CORS
#
[jacky]
will make a note to file a report
#
gRegor
oh bummer
[will] joined the channel
#
[will]
yeah, looks to be broken. I'll try to dig into what's going on
#
[will]
oh, it's also trying to hit endpoints on my personal website that don't exist anymore. It should go to the *.microformats.io servers
#
@miklb
Tumblr 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?
#
aaronpk
yes they've been on a paid heroku plan for a few years
#
gRegor
They've mostly been on autopilot but recently we've been making more updates, team effort managing them
#
[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
#
aaronpk
oh nice
#
aaronpk
i'm up for that
#
[will]
Happy to transfer it over to someone if we are managing these domains centrally
#
[will]
or I'm also happy to pay for it and just point DNS in the right direction
#
aaronpk
we've been paying for the domain and heroku from the indieweb open collective, so happy to do that
#
aaronpk
the .io is already registered through 2026 so we can make a migration plan to the .dev
#
[will]
I just added your gmail account to the domain, so you should be able to manage it at https://domains.google.com/registrar/microformats.dev
#
aaronpk
cool, that works. let's see if heroku lets me add multiple domains to an app
#
[will]
hah, nice!
#
aaronpk
ok i'll do the rest of them in a bit
#
[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 .
#
[will]
I'll send PRs for those later today
#
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
#
gRegor
I think you might want to use u-ipa on the <source> elements inside the <audio>, presuming you want the parsed value to be the URLs
#
gRegor
The 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"
#
gRegor
Aside: that audio doesn't play for me in Firefox or Chrome
#
gRegor
"Couldn't show page" when I try to open the .wav URL directly
#
[jacky]
oof lots of failures from me 🙂
#
[jacky]
will make notes of things to file and fix
barnaby joined the channel
#
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
ur5us_, [manton] and pablo1 joined the channel