#microformats 2019-08-20

2019-08-20 UTC
ichoquo0Aigh9ie, IWSlackGateway, boboom, rf, [tantek] and [fluffy] joined the channel
# 06:34 
Zegnat Re URL normalisation in browsers: it is a weird world. If I go to https://tantek.com Firefox will not add the trailing slash, but if I then request the URL I am on (document.location.href) it will have the trailing slash. So the browser does not seem to expose the non-path variant
# 06:50 
Zegnat I feel like I am spiralling deep very quickly with the WhatWG URL Spec. But it seems like HTTP URLs when serialised to a string will always result in have a trailing slash on domains.
# 06:51 
Zegnat Which may be why document.location.href contains it, as that JS follows the WhatWG spec even if the browser UI does not
# 06:54 
Zegnat Probably also where IndieAuth gets it from. Special URLs (http & https included) always have non-empty paths: https://url.spec.whatwg.org/#concept-url-path
# 06:57 
Zegnat Alright, rabbithole documented, back to actual work
[KevinMarks], [prtksxna], [Serena], KartikPrabhu, [jgmac1106], sundayDiscord[m], perro, TallTed and [schmarty] joined the channel; sundayDiscord[m] left the channel
# 15:33 
[schmarty] feels like there are two kinds of normalization here
# 15:33 
[schmarty] normalization for HTTP the protocol and normalization for humans
# 15:35 
[schmarty] e.g. tantek's note above about expecting his username to be "tantek.com" without any path info. also note no protocol info at all, so http vs https is not in the mental model there.
jackjamieson, [KevinMarks], [jgmac1106], [jgarber], [fluffy], [tantek], [schmarty], KartikPrabhu, [Lewis_Cowles], mauz555, [tonz] and ivanDiscord[m] joined the channel