#[tw2113_Slack_]<p>This is in reply to <a href="https://boffosocko.com/2020/11/03/55780525/" target="_blank" rel="noreferrer noopener" class="u-in-reply-to">https://boffosocko.com/2020/11/03/55780525/</a></p>
#Loqi[Chris Aldrich] Can’t wait to see this tomorrow!
#[tw2113_Slack_]i may need to recompile so the rel tag gets "in-reply-to" as well
gRegorLove, nickodd, [chrisaldrich], stevestreza, jbove, ludovicchabant, dietricha, peterrother, mattl, mitchell, danyao, themaxdavitt, willnorris, craftyphotons__, cjav_dev, jimpick, voxpelli, kitt, jmac, shakeel, genehack, skalnik, myfreeweb, schmudde, dhanesh and vika_nezrimaya joined the channel
#nolithhello. I'm having some troubles with google indexing. searching stuff on my website it always links to either the tag page containing my h-entry or the homepage. It never points to the permalink. And this is a problem because, especially the homepage, will likely no longer contain the indexed content because of pagination. Is there a way to affect indexing in order to better position
ShinyCyril and [Raphael_Luckom] joined the channel
#aaronpkI suppose you could tell google to not index the feed pages
#nolithgood point. I could exclude tag feeds with a robots.txt as well as all the paginated version of the homepage. (it's a static site, so they all have unique paths).
#aaronpkI forget the tag but there's a meta tag you can use too which might be easier than robots.txt
#aaronpkand I thought there was one that told it to not index the page but still follow links from it
#nolith!tell [manton] I wrote a tiny proxy into my micropub server that can serve my RSS feed hosted on GitLab pages. With this hack I was able to make it work with micro.blog. But I'm not happy with the result, I'm planning to implement a proper syndication based on micro.blog API
#petermolnarI'm really not a big fan of Dave Winer but in this specific case, he seems to be correct about the fragility of HTTPS, though it's a reverse direction: not because of forgot-to-renew certificates, but because of how root certificates are agreed upon.
#petermolnarinterestingly enough the root certificate problem was not mentioned by Scott Helme
KartikPrabhu joined the channel
#ZegnatI think the root cert problem may not come up too often, because new players do not easily join the field (case in point: onboarding time for Lets Encrypt :P)
#petermolnarthat only makes it even more impacting
#petermolnarI still have an ancient android version on a device of mine, 2.3.something, which can't deal with SNI either; that was also a breaking change
#[snarfed]lahacker: instagram turned off its API for non-commercial uses a while ago, so bridgy has been scraping it since then to provide backfeed. not ideal, but 🤷♂️
#[snarfed]it’s taken (of course) a decent amount of updating since then, chasing changes, evading blocking, etc. their most recent bot detection is pretty aggressive, not sure if/when i’ll manage to get around it
#[snarfed]bridgy also has to fetch all of the individual media permalinks to get comments, likes, etc. looks like that bibliogram page doesn’t. so 10-20x load (oversimplification) for even the same amount of usage 😭
[KevinMarks] joined the channel
#ZegnatYou can open the individual media permalinks in bibliogram. But it does not seem to show comments, I thought it did. Hmm.
[jgarber], ShinyCyril, geoffo and [chrisaldrich] joined the channel