#dev 2024-03-29
2024-03-29 UTC
geoffo and [Joe_Crawford] joined the channel
# [Joe_Crawford] For years I've had a php error log on my personal site that was a steady stream of misc warnings and errors. Over the past months I've been attacking each of the bad actors and it's gone a solid 12 hours without an error. Obviously it's time to code some new stuff.
BinarySavior and jacky joined the channel
# [Joe_Crawford] Given that the majority of the code on my site is my own hand rolled theme, which includes short codes, custom templates, some classes that extend wordpress classes, an extension to DOMDocument, I’m the person to blame for all of it. There are some utilities and other non-wp stuff I moved into wp too.
sp1ff, vikanezrimaya, moose3337, [tantek], gRegorLove_, gRegor, jacky, [jeremycherfas] and AramZS joined the channel
[manton] joined the channel
# [manton] [snarfed] I’m experimenting with pulling Bluesky mentions into http://Micro.blog. It’s interesting to make it play nicely with Bridgy too. I’m now hitting the permalink for Bridgy in some cases to resolve a http://brid.gy/comment/bluesky/did:plc/… URL into an at:// URL (looking for p-uid). Don’t expect this will create any problems, just FYI.
# livebay Hello guys, I want to know how can I create headers file
# livebay I only tried Netlify syntax in their own setting, but now I want to upload all my files directly to my website folder using sftp
jacky, ttybitnik and mahboubine joined the channel
# Loqi It looks like we don't have a page for "headers file" yet. Would you like to create it? (Or just say "headers file is ____", a sentence describing the term)
[qubyte] joined the channel
jacky joined the channel
# livebay No sorry, I mean I only used their syntax in a Netlify .toml file before, but this time it's for a different site on pages.casa, and I don't know how to create hearders file myself (such as its file name...format.. and other) or where to put it
# [qubyte] Put it in your public directory (the one served by netlify). You can see some example configurations in their docs: https://docs.netlify.com/routing/headers/
# [qubyte] The path the rules apply to is on the first line. In this case it’s an exact match, but wildcards and placeholders can be used to apply to many paths. The second line is indented, and contains the header key left of the colon, and the value is everything on the right of the colon (including the semicolon at the end).
# livebay [qubyte]: Thank you very much, that helps a lot!
jacky and geoffo joined the channel
# sknebel https://www.openwall.com/lists/oss-security/2024/03/29/4 (TL;DR: backdoor in upstream of xz compression library, which infects package builds, when used with SSH produces vulnerable SSH servers)
geoffo, jacky and [schmarty] joined the channel
# [schmarty] wowow sknebel++
BloggingBitcoin and ttybitnik joined the channel
jonnybarnes joined the channel
# capjamesg [tantek] See https://github.com/capjamesg/indieweb-utils/blob/main/src/indieweb_utils/replies/context.py#L334 for my and [James_Van_Dyne]'s prior work on reply contexts.