[KevinMarks]I have some html emails to parse in python. Do I use html5lib, or html.parser on the assumption that html emails are likely to conform to last century's html worldview?
[KevinMarks]I'm doing it in an AWS lambda, so overhead can matter (and I'm using python because it's general email parsing is mature and well debugged)
[Jamie_Tanna]How should `mp-slug` manipulate the generated post URL? If we usually have URLs as `/posts/2022/$random` would an `mp-slug=bar` would make the post URL `/posts/2022/bar` or `/bar`?
LoqiStatic site generators or SSGs are programs that take a set of flat text files on disk and transforms them into a set of static HTML files ready to be served by a standard web server, or some variation of this example https://indieweb.org/SSG
[campegg]capjamesg I read that SSG post a few days ago, and it doesn’t quite sit right with me. Personally, I’ve never come across anyone who tried selling them as “simple”… “simpler” maybe — not having to maintain server/CMS/database makes them simpler (erasier, more flexible, whatever) to host, I guess 🤷♂️
[campegg]I had the same sort of reaction to Kev’s recent indieweb post, too. Not sure if he’s trying to be deliberately provocative to generate traffic or if those are genuinely his positions (or possibly both?)
capjamesgMy SSG is complicated because it has a lot of code for incredibly niche things that almost nobody else would do. Those same niche things would complicate a dynamic site, too.
[campegg]Exactly — SSGs aren’t inherently “simple”… they can be just as complex (or complicated) as any other system. Just because their output is less hard to host doesn’t necessarily mean the underlying generator of that output is simple
[campegg]As an aside, I liked you post about the Etherpad archive bot… I need to get better at articulating my logic when I’m building like you did there. At the moment, I tend to do a lot of it on the fly, which means a lot of going back and re-doing things later when I realize I’ve done something completely boneheaded
[KevinMarks]SSGs are simple to keep up, less simple to create posts in, that seems fair. The original Blogger was an SSG that FTP'd to your own hosting
LoqiIt looks like we don't have a page for "classless css" yet. Would you like to create it? (Or just say "classless css is ____", a sentence describing the term)
[snarfed]first step of sending wms to all HN and Reddit posts is discovering wm endpoints on all of their domains. that's been humming along, currently at 250k domains processed, 104 endpoints discovered
[manton][snarfed] Do you have an example of what the Webmention looks like from HN/Reddit posts? Curious if Micro.blog will be able to process them correctly. I assume there’s some kind of shim HTML/MF2 like Bridgy uses?
aaronpkoh interesting, sending the webmention with the source of the actual hackernews page is an interesting idea. no mf2 but it would be a "real" webmention
[manton]I think because Micro.blog is more interested in trying to assemble a conversation thread than keep track of incoming links, I’ll still ignore them if there’s no explicit in-reply-to.
[Jamie_Tanna]I notice that https://micropub.spec.indieweb.org doesn't make it explicit with an example - just to confirm, we'd expect `mp-syndicate-to` to be found in the JSON body at path `$.properties.mp-syndicate-to`, right?
@OpenMentions↩️ I'll go first - my website is powered by #WebMention which allows anyone with a blog, website, Twitter, or any other content type to use that outlet to make comments on other websites. (twitter.com/_/status/1561760333961854976)