#dev 2020-12-16
2020-12-16 UTC
[manton] joined the channel
# 
[manton] @lahacker Just to be clarify, I didn’t meant to imply that the Blog Archive Format was deprecated. Just that I based the GitHub support on the same basic structure. I’d still love to see people support Blog Archive Format! I think it can be useful to have a single file to back up or move around.
[eddie] joined the channel
# 
superkuh epub'ish.
JackyAlcin[m], [chrisaldrich], geoffo, jjuran, [jgmac1106], hirusi, [Emma_Humphries] and ShadowKyogre joined the channel; ShadowKyogre left the channel
# lahacker !tell manton the example.bar in https://www.manton.org/2017/11/24/blog-archive-format.html can't be found
swentel, [Ana_Rodrigues], [jgmac1106], KartikPrabhu, hirusi, ShadowKyogre, geoffo and [KevinMarks] joined the channel; ShadowKyogre left the channel
# 
@e3d5_fr ↩️ https://indieauth.spec.indieweb.org/ ? Mais le problème est toujours là :
- Demander une URL d'authentification c'est complexe, ça ne fonctionne pas en pratique
- La plupart des gens ne veulent pas créer une auth sur un service tiers, donc rien ne fonctionnera sans volonté des gros (twitter.com/_/status/1339226135868166144)
# @e3d5_fr ↩️ Tout ce qu'on peut faire c'est éventuellement continuer à proposer les boutons pertinents comme aujourd'hui, et mettre *en plus* un truc genre indieauth en bas. Sauf que pour l'essentiel des services en ligne, cette option "en plus" c'est l'option de trop, inutilisée (twitter.com/_/status/1339226376210100225)
[schmarty], schmudde, [jgmac1106], jolvera, hirusi, swentel, fjf, [chrisaldrich], [calumryan], [Emma_Humphries], [tantek], [KevinMarks] and KartikPrabhu joined the channel; ShadowKyogre left the channel
# 
[schmarty] aaronpk these SSRF resources you just added to /IndieAuth 😱
# [schmarty] i kind of love how this all falls out from different libs and tools (or in PHP's case, different parts of the same damn language) using different URL parsing algorithms.
# [schmarty] like a classic case of: you should only have one URL parser for frak's sake!
# [schmarty] right and curl doesn't expose its URL parsing i guess so you won't defer to it
# [schmarty] meanwhile curl declared wontfix on the whitespace issue so 😭 😭 😭
# [schmarty] like i guess a workaround is to use a strong parsing library to parse the URL, validate the URL, and then _rebuild_ the URL from those parsed and validated parts before passing to anything that fetches.
[snarfed] joined the channel
# 
@wirehead2501 maybe teaching sand to do math was a mistake (twitter.com/_/status/933225268990197760)
ShadowKyogre and [Ana_Rodrigues] joined the channel
# lahacker i really want to just implement a default "safe mode" in my URL parser that raises UncoolURL at anything even remotely uncool
# lahacker just live with it and see what kind/class of URLs i'd be prevented from using.. like 99.99% of URLs are pretty decent, supporting that long tail of the spec is just not worth it
gxt joined the channel
# lahacker i guess "cool" URLs were ones that don't change.. maybe "IllegibleURL" or heck just "DangerousURL"
# lahacker heh well my "parser" is just a shiny wrapper around Python's urllib but the idea would be to perform some kind of sanity checks before handing it off
chrisaldrich joined the channel
# lahacker feels like the URL equivalent of POSH
[Emma_Humphries], strugee, gRegorLove_ and [snarfed] joined the channel; ShadowKyogre left the channel
[KevinMarks] joined the channel
# 
[KevinMarks] This is an interesting idea - I wonder if it could work for private posts https://css-tricks.com/learning-to-simplify/
# 
gRegorLove_ oh noo
# gRegorLove_ Neat browser extension idea, though