#dev 2024-09-05

2024-09-05 UTC
#
pcarrier does anybody care about brotli over zstd in any context other than HTTP anyway?
#
sebbu yes : compression of packages, including sources
#
sebbu for example, a few years (decade?) ago, packages were mostly in .tar.gz or .tar.bz2 everywhere
#
sebbu now we see tar.xz and tar.zst
#
pcarrier yeah, and now it's zstd afaict?
#
pcarrier that's my point, nobody wants brotli?
#
sebbu they could
#
sebbu and the lack of a recognizable header to the file format is a reason it's been avoided outside of http
#
sebbu and even when you save a http file, if you didn't decompress it, you might not recognize the file format anymore
#
sebbu or any file over http that has been compressed by brotli
#
pcarrier so you're arguing for zlib instead of deflate, but for brotli
#
pcarrier which wouldn't be backward-compatible, so it'd need a new identifier and it'd have to compete with zstd for adoption
#
sebbu deflate is recognizable
#
pcarrier in a way brotli isn't?
#
pcarrier that wasn't my understanding, but I'm no expert
lockywolf, srijan, zicklepop, sp1ff, [tantek], [qubyte], [schmarty], [Joe_Crawford], [benatwork], IWSlackGateway, [snarfed], [aciccarello] and [Jo] joined the channel
#
[Jo] has anyone else been having trouble with the spotify API?
kushal, cuibonobo, ramsey, ancarda, suki, [tantek], [snarfed], [qubyte], [schmarty], [Joe_Crawford], [aciccarello], [benatwork], IWSlackGateway, eb and jonnybarnes joined the channel
#
doesnm i'm making auth_endpoint(https://doesnm.p.psf.lt/auth.sh). After i press "Submit query" it should check signature and redirect to callback_url or something more?
#
doesnm in wiki i see another endpoint which should return json. It is auth endpoint or token endpoint?
[KevinMarks] joined the channel
#
[KevinMarks] One of the early RSS specs mandated a maximum of 15 entries, iirc
ttybitnik joined the channel
#
sebbu yes, binwalk is able to detect deflate streams
#
sebbu and brotli can't be recognized (by design)
#
aaronpk doesnm: Auth endpoint returns an authorization code in the redirect, then the client will exchange the authorization code at the token endpoint
#
doesnm so i should send password/etc via get? because post for exchange
#
aaronpk How you handle the user interacting to authenticate themselves is not part of the spec and you should follow general web best practices for any of that part
Loqi, [Jo]1, IWSlackGateway, [aciccarello], [KevinMarks], [Joe_Crawford], [benatwork], [snarfed], [schmarty], [tantek], ChrisFu, to2ds and voxpelli joined the channel
#
gRegor what is protected post
#
Loqi It looks like we don't have a page for "protected post" yet. Would you like to create it? (Or just say "protected post is ____", a sentence describing the term)
#
gRegor what is protected
#
Loqi protected is a type of account or post that requires at least signing-in to view, and typically only allows a specific set of people to view (like friends-only posts) and possibly interact with https://indieweb.org/protected
#
gRegor protected post is /protected
#
Loqi ok
AramZS, AramZS_, barnaby, ttybitnik, grufwub and rozenglass joined the channel