#microformats 2022-02-02

2022-02-02 UTC
cygnoir[d], jacky, [jgmac1106], darkkirb, [fluffy], [chrisaldrich], [Aaron_Klemm], [benatwork], ur5us, [chrisaldrich]1, [benatwork]1, [schmarty], hoenir, aaronpk[d], Myst[d], mossymaker[d], MarkJR84[d], sarahd[d], grantcodes[d], marksuth[d], KartikPrabhu, [jackjamieson], phae, [aciccarello], bg2, zachburau[d], angelo, Seirdy, P1000[d], Christian_Olivie, [manton], hans63us[d], Ramon[d], corenominal[d], capjamesg[d], sayanarijit[d], daiyi[d], Zegnat[d], GWG, klez, barpthewire_, m5zs7k, saptaks_znc, rektide, ben_thatmustbeme, Saphire, sebbu, willnorris, yolk, Kaja, aaronpk, jamietanna, sknebel, aspenmayer[d], balupton[d], [tw2113_Slack_], Seb[d], rattroupe[d], [KevinMarks], IWSlackGateway, Jeremiah[d], Zegnat, JSharp, [jeremycherfas] and gRegor joined the channel
[tonz], jacky and KartikPrabhu joined the channel
#
[tantek]
capjamesg[d] your updated page is getting some views ^ πŸ˜‚
#
capjamesg[d]
Yes πŸ˜‚
#
[tantek]
You could reply saying hi thank you and that was your first MDN update and feedback & suggestions welcome!
KartikPrabhu and Asaf_Agranat[d] joined the channel
#
[tantek]
aaronpk have we considered adding IndieAuth login to the microformats wiki also? would there be a way to preserve existing user/pw logins while allowing new IndieAuth logins?
#
[tantek]
if we're able to make that work, I can think of a few more MediaWiki wikis that would likely also adopt a similar setup
#
aaronpk
i suspect any time that was brought up in the past i said we would have to wait until the upgrade to revisit it :)
#
aaronpk
but now that that's done, we can discuss :D
#
[tantek]
πŸ˜„
#
[tantek]
I figure especially with capjamesg[d]'s success in setting up a new MediaWiki with IndieAuth, it feels like time
antrdnv[d] joined the channel
#
GWG
aaronpk: How many accounts does the microformats wiki have?
#
[tantek]
GWG, lots have been created & banned due to spam holes of the past
#
[tantek]
at this point it's too much work to moderate any new "public" wiki that an individual or small group would setup
#
[tantek]
hence the iteration on getting IndieAuth sign-in working for MediaWikis in general, and getting it adopted by more wikis (so it can become a "normal" thing for any new MediaWiki)
#
aaronpk
I do think if we expect it to be used by other mediawikis it makes more sense to build the whole indieauth bit into the plugin itself
#
aaronpk
that would remove the setup step capjamesg[d] had to do with Vouch-Proxy
#
[tantek]
definitely
#
aaronpk
the main advantage of vouch-proxy is that you can share the login across a bunch of different subdomains, which is useful for indieweb.org
#
sknebel
(also, it goes through indielogin and thus doesnt just do indieauth, right?)
#
aaronpk
but then that also brings up the question of whether it should be just indieauth, or also support relmeauth to twitter/etc, which then adds the additional setup step of getting api keys
#
aaronpk
correct, vouch-proxy doesn't do indieauth itself, it does oauth/oidc to a single configured provider
#
sknebel
which is indielogin, which gives us indieauth and relmeauth?
#
[tantek]
ok that's non confusing at all lol
#
aaronpk
it's a bunch of building blocks
#
[tantek]
"share the login across a bunch of different subdomains" is super useful yeah
#
[tantek]
"bunch of building blocks" sounds familiar πŸ˜‚
#
aaronpk
but yeah frankly i wouldn't recommend the indieweb wiki setup as is for other mediawikis
ur5us and gRegor joined the channel
#
capjamesg[d]
Love this discussion!
#
capjamesg[d]
I am so happy that Vouch Proxy supports indieauth. But the documentation for actually getting set up was quite crowded.
#
capjamesg[d]
Not on the indie auth part, the vouch proxy installation and setup part.
#
capjamesg[d]
A custom extension might be wonderful.
#
capjamesg[d]
I think a mediawiki plugin might make adoption a bit easier to those who haven’t used the IndieWeb wiki much.
#
GWG
Would it be a IndieAuth plugin or a websignin plugin?
#
aaronpk
the problem with full web sign-in is needing API keys, and at this point really only github is easy to get api keys from
#
sknebel
yeah, thats a whole other can of worms
#
GWG
aaronpk: What about just the pgp key, I meant
#
aaronpk
i should check the stats to see how much usage pgp actually gets
#
Loqi
totally
#
aaronpk
wow pgp is 3x indieauth on indieauth.com
#
aaronpk
but github is 10x pgp
jacky, barpthewire_, ben_thatmustbeme, IWSlackGateway, rattroupe[d], Zegnat, [KevinMarks], sebbu, Seb[d], gRegor, Jeremiah[d], darkkirb, corenominal[d], aspenmayer[d], [tw2113_Slack_], aaronpk, [fluffy], sknebel, [Aaron_Klemm], ur5us, yolk, hans63us[d], balupton[d], [tonz], [jgmac1106], klez, GWG, KartikPrabhu, [schmarty], hoenir, Myst[d], aaronpk[d], mossymaker[d], MarkJR84[d], sarahd[d], Kaja, willnorris, daiyi[d], antrdnv[d], capjamesg[d], rektide, Ramon[d], sayanarijit[d], Christian_Olivie, Seirdy, P1000[d], [jackjamieson], m5zs7k, Zegnat[d] and JSharp joined the channel
#
[tantek]
That's GitHub via web sign-in right?
[aciccarello], angelo, [manton], phae and saptaks_znc joined the channel
#
[tantek]
Feels like a data graphic of some kind would be useful here
#
[tantek]
What's the time period for those stats aaronpk? Daily? Past year?
sebbu joined the channel
#
aaronpk
that was past 2 years
Saphire and jacky joined the channel
#
[schmarty]
haha i love the PGP option but i am also pretty much always signed into github so i just use that when i use indieauth.com πŸ˜…
#
[schmarty]
1-click vs click, copy, paste into command line script, type GPG password, return to browser, paste, click
#
aaronpk
oh the trick is to set up a hot key to sign the text in place :)
#
aaronpk
pgptools on the mac can do it, it shows up in the "services" menu when you select any text in any app
#
aaronpk
oops i mean gpgtools
#
jacky
oh that's nifty
#
jacky
I was actually coming in to say that I kind of wish that https://microformats.org/wiki/microformats2-parsing had either a micro-glossary or was re-worded a bit to be less sparse in some parts
#
Loqi
Tantek Γ‡elik
#
jacky
but oddly enough, the structure lightly resembles pseudo code which makes it good for a scan
#
jacky
but not for a deep dive
#
jacky
actually wait
#
jacky
this line
#
jacky
> if that child element itself has a microformat ("h-*" or backcompat roots) and is a property element, add it into the array of values for that property
#
jacky
how does it determine which one to use
#
jacky
like if I have a <a href="/foo" class="u-author h-card u-url">Footster</a>, the properties there would be `u-author` and `u-url`
#
jacky
is `url` implictily ignored?
#
jacky
unless "else use the parsed property value per p-*,u-*,dt-* parsing respectively" means "use the property element as the value to be added to the property class that was found"
#
jacky
actually those are two separate things (which I kinda blame on the formatting of this page)
#
jacky
heh lucky that y'all got xpath
#
jacky
gotta this using a manual tree walker
#
sknebel
I personally find that easier than xpath :D
#
sknebel
also, multiple property classes on an element mean all of them get parsed
#
sknebel
properties never get implicitly ignored
#
sknebel
i.e. the "is a property element, ..." implies "do this for each property"
#
jacky
I think I'm confused b/c of this phrase "add it into the array of values for that property "
#
jacky
because in my head, that means with "u-author h-card u-url", I'd be adding it (the parsed h-card) to the 'author' and 'url' properties of its parent, which is _wrong_ to me
#
sknebel
thats correct
#
sknebel
I dont think that specific example would make sense very often, but thats how it works
#
jacky
woah okay
#
jacky
that's really mindblowing to me
#
jacky
but it's probably b/c my example is very not likely when it's been semantically written
#
sknebel
nested elements really work the same as any other property value
#
sknebel
i.e. "u-url u-uid" is a common pattern, resolves in two properties with the value
#
jacky
oh yeah, you're right
#
sknebel
if that happens to be a h-* root instead of a plain u- value, it doesnt care
#
jacky
I guess now what's tripping me up is resolving one's "value"
#
sknebel
that depends on the parent property type
#
jacky
oh wait
#
jacky
yup mind's officially blown
#
jacky
b/c tbh it makes _perfect_ sense now (the value changes depending on who's looking at the property)
#
jacky
but I totally took that for granted, lol
#
sknebel
so it probably makes sense to parse the child once, and then for each property its "assigned" to calculate the value that fits for the case
#
jacky
thanks sknebel++
#
Loqi
sknebel has 3 karma in this channel over the last year (35 in all channels)
#
jacky
that's exactly how I'm going to do it :)
#
sknebel
(technically for each property type, but without measuring I can't tell you if thats actually faster in practice to make that distinction. the python parser does it that way, but not everything is python and I don't remember if that was done that way as a result of profiling or not)
#
sknebel
since usually there's only 1-2 properties
#
sknebel
so, I'm off to bed now, but happy to help tomorrow if theres other questions
#
jacky
totally
#
jacky
thank you so much
#
jacky
this was a considerable road block for me :)
#
[tantek]
sknebel is correct
#
[tantek]
jacky, there's a challenging balance in specs between precision and conciseness to prevent ambiguity. shorter and fewer words usually means fewer places for unintended "bugs" in the prose to creep in
#
[tantek]
specs have their own "specese" (pronounced like legalese) as a result
#
jacky
Tbh in retrospect, that makes sense
#
jacky
I could have imagined this being a bit tricky to implement the first few times around
#
jacky
I think potentially some inline examples _could_ help
#
jacky
but that's what the test suite is for, I guess
ur5us joined the channel