#dev 2022-10-06
2022-10-06 UTC
KartikPrabhu joined the channel
# KartikPrabhu Loqi: any chatter for me?
# [tantek]4 welcome back KartikPrabhu!
# KartikPrabhu hi
# KartikPrabhu yo barnaby
# [tantek]4 capjamesg, so I won't forget, can you file an issue asking to promote auto_url_summary from cassis-lab to cassis.js core based on your desire to re-use / port it?
# KartikPrabhu I'll take a Welc5 too
jacky and [fluffy] joined the channel
geoffo, jacky, [tw2113_Slack_] and maxwelljoslyn joined the channel
# maxwelljoslyn tantek
jacky joined the channel
jacky and tbbrown joined the channel
jacky joined the channel
mro, jacky and gxt joined the channel
# @zimmergren ↩️ I love the idea of webmentions. I'm not a CSS magician anymore, so obviously it needs some work - but this is pretty neat, and the engagement is clearer.
At the end of each post, it's pulling in any social mentions for that specific URL, mainly from Twitter (twitter.com/_/status/1577935451427639296)
# @zimmergren ↩️ I'm using native webmentions, pulling in social comments directly to the published posts.
I'm leaning into disabling disqus, but I have thousands of comments there that I really don't want to lose out on - so first figuring out a way to map those to the posts, too. (twitter.com/_/status/1577935030705348608)
jacky and gRegorLove_ joined the channel
# capjamesg [tantek] You can review my implementation here: https://github.com/capjamesg/indieweb-utils/pull/69/files
jacky, mro, gRegorLove__, tetov-irc, KartikPrabhu, barnaby, gRegor, geoffo and gRegorLove_ joined the channel
petermolnar joined the channel
# barnaby the archive.org wiki has a strong opinion and some background about ignoring robots.txt being fine https://wiki.archiveteam.org/index.php/Robots.txt
jacky joined the channel
Seirdy joined the channel
# [Murray]1 jamietanna++ was genuinely considering _yesterday_ whether I should build my own feed reader, because I've gotten fed up with the offerings that are out there. But maybe not... 😂
# [schmarty] i've been wondering if aaronpk would be open to community additions to Aperture :}
# [Murray]1 I just want something that can give me a list of links to the posts I have not yet read on someone's website 😂 And for that to work well on mobile devices. (And not arbitrarily decide to remove posts older than X, which is my issue with most services)
# [Murray]1 TheOIdReader works well for point 1, but I'm increasingly preferring to read blog posts on my phone, so that means I barely touch my RSS feeds anymore
# [Jamie_Tanna] I was thinking of building my own Micropub server cause I want to do people-first channels rather than feed-first (which I know as a concept we've talked about but not yet done) and even if it then just manipulated Aperture as a backend, I'd need to implement some of the stuff myself
# [Jamie_Tanna] *Microsub
# [Murray]1 well, guess I should take another look at Microsub options then. I do not have the will to get into building a back end for that; I was planning on going a very similar route to that article (feedparser + 11ty/Astro + an edge function) but even that seems too much now 😄
# [Murray]1 it's on the Microsub page by the looks of things
# [Murray]1 https://github.com/capjamesg/cinnamon
# [Murray]1 unless I'm getting things confused again
# [Jamie_Tanna] More about the bigger vision for what I want to build https://www.jvt.me/posts/2021/05/01/social-reader-features/
[ggirelli] joined the channel
# [tantek]4 capjamesg, interesting restructuring of the auto_url_summary code!
# [tantek]4 I think part of the reason I didn't break it down to smaller functions e.g. for github and social media the way you did is I was hoping that with all the code inline in one function, more overall patterns would emerge that could help rewrite from a giant if/else to something that looked things up in a static table
# [tantek]4 also part of the reason why I kept in cassis-lab, it felt like a total hack/prototype piece of code that I wouldn't want others re-using/copying because of it's unsustainable structure lol
# [tantek]4 linting fails?!? that seems like a very poor way to solve the problem
# [tantek]4 as in, breaking it up in to more functions obfuscates the hackishness
jacky joined the channel
# [tantek]4 I'd say that's actually *worse* for the eventual rewrite
# [tantek]4 I'm a fan of keeping hackishness of code transparent front & center so it shows up more obviously as something to more "globally" fix
# [tantek]4 rather than hiding the hackishness amongst a bunch of functions
# [tantek]4 coding style preference sure, however IMO it's a code-maintenance culture thing too, as well as a way to "signal" where something should/should not go
# [tantek]4 capjamesg, still thinking about it
# [tantek]4 I knew I had blogged about keeping ugly code ugly deliberately before: https://tantek.com/log/2005/11.html#d26t1820
petermolnar joined the channel
# [tantek]4 in the context of "hack should (or MUST in the RFC2119 sense if you prefer):"
# [tantek]4 "3. Be ugly. It's actually a *good thing* that a hack be visually ugly from a coding aesthetic point of view in the hopes that the ugliness will be a reminder that the hack *is* a hack, and should incite a tendency for people to a) minimize it's usage, and b) remove it's usage over time."
# [schmarty] IndieAuth.com does this as well
# jacky oh I did _not_ see that on https://indieauth.com/setup wow
jacky joined the channel
jacky joined the channel
gRegorLove_, gRegorLove__ and jacky joined the channel
petermolnar and jacky joined the channel
# [James_Van_Dyne] I think you’re better making it “private” functions and adding it into the list so you can type / have comments and so forth. It also allows you to pass / wrap the function if you need to
# [James_Van_Dyne] But yeah - lgtm
[manton] joined the channel
# [tantek]4 hmm, maybe that's a thing in Python but in general I'm not a fan of the "array of functions to call" method. that feels like it is "merely" obscuring the hackiness underneath a clean-ish looking layer
# [tantek]4 I'd still push for it to be purely data-driven and all the logic in one function, not split across functions
# [tantek]4 again, keeping all the logic in one function makes it easier to see it all at once and develop insights about more global optimizations / redesigns
jacky joined the channel
jacky joined the channel
# capjamesg Here's my combined solution: https://gist.github.com/capjamesg/486ab9e189d2ea12b1013598dd4a2445
# gRegor [tantek]4, were you waiting on Matt's ok to merge https://github.com/indieweb/rel-me/pull/7? It shouldn't change any of the RelMeAuth functionality
jacky and tetov-irc joined the channel
# [tantek]4 angelo, re: use-case, the (original) PHP version of this function is in live use on my site for my reply contexts https://indieweb.org/auto-url-summary#Tantek — you can check out the results in context on my home page composite stream, search for "In reply to" in the page https://tantek.com/
# [tantek]4 gRegor, perhaps. did you have a preference for how we move forward with what jamietanna asked about tests?
# [tantek]4 I don't have an opinion either way. I was asking only to see if we had a specific strategy in mind 🙂
jacky joined the channel
# gRegor Running `/vendor/bin/phpunit` works well. Composer scripts let you alias a more complex command, which I guess php-mf2 does: https://github.com/microformats/php-mf2/blob/main/composer.json#L32
# [tantek]4 Sounds good.
# [tantek]4 I think a week is enough time for a heads-up. If there's something he suggests reverting we can handle it then 🙂