#dev 2021-04-03

2021-04-03 UTC
Jaybear, alex_, [chrisaldrich], [KevinMarks], samwilson, [tantek], chrisaldrich and tomlarkworthy joined the channel
#
tomlarkworthy but the indieauth.com server is ALSO an oauth provider, with its own set of client_id etc. right.
KartikPrabhu joined the channel
#
beko Huh… got a Bridgy job hanging in the queue again. This time publishing to Mastodon. It seems to have made it to the media post 36m ago and nothing ever since.
#
aaronpk tomlarkworthy: IndieAuth.com (but not indielogin.com) is an IndieAuth provider and can issue access tokens
#
aaronpk thats why I split out the indielogin.com part into its own project that is only the relmeauth and IndieAuth client part
shoesNsocks1, dhanesh, [chrisaldrich], KartikPrabhu and [snarfed] joined the channel
#
[snarfed] hrm, sorry beko! that publish request died, not sure why, i’ll look into it. feel free to retry though!
#
[snarfed] (it’s not still running. bridgy publish requests don’t run in the background, ie not longer than the HTTP requests that trigger them)
#
[snarfed] and in general retrying bridgy publish requests is safe and idempotent and won’t duplicate posts in silos
[scojjac], shoesNsocks, [tantek], [fluffy] and alex11 joined the channel
#
beko !tell [snarfed] I see. Was confused because it [still] says "Processing"
#
Loqi Ok, I'll tell them that when I see them next
prof_milki joined the channel
#
prof_milki Is there an attribution license/requirement to the IndieAuth logo? I made a little auth_endpoint extension for my repositories (https://fossil.include-once.org/fossil-skins/ext/auth) with a semi-lookalike img.
#
[tantek] good q prof_milki. I'm not seeing the IndieAuth logo on the wiki at all (e.g. https://indieweb.org/IndieAuth ) nor do I see the answer in the FAQ on that page. Perhaps we can nudge aaronpk to add them to that page 🙂
#
beko prof_milki: you may like https://pfefferle.dev/openwebicons/
#
[tantek] there was an informal discussion about TLS and older devices / software in #indieweb-chat that reminded me of some of my reasons for keeping both http: and https: support on my site
#
[tantek] restating here in case there are others who may agree (or disagree!)
#
[tantek] the problem of old(er) devices is not just TLS support (or lack thereof) but of lack of support for new certs
#
[tantek] (it's literally one of the reasons why I'm fairly strongly on the side of allow both http: and https: access to my site)
#
[tantek] IMO this is both an environmental (keep devices out of landfills) and a global equity (allow cheap/free devices to keep working) issue
#
[tantek] the trade-offs with "login" based features are more complicated (and I don't have a good answer to that yet; personally all the "login" like features on my site do require https)
#
[tantek] should these (environmental & equity) concerns be documented on https://indieweb.org/HTTPS#Level_3_security, or is this more of a personal opinion and I should do a blog post instead (or at least first)? what do people think?
#
[tantek] [end of chat restating]
dckc, KartikPrabhu, RG, [KevinMarks] and [chrisaldrich] joined the channel
#
jacky I never considered that
#
jacky I can see some people still fighting to keep things HTTPS only on the vein of privacy but I think I can do the both approach
PauloPinto joined the channel
#
[tantek] snarfed, this looks like it may be a Bridgy Publish bug errantly posting a photo in a tweet when it shouldn't
#
[tantek] note the only 'photo' properties are inside h-cards in the h-entry here: https://pin13.net/mf2/?url=https://paulopinto.org/2021/04/why-i-am-a-bad-correspondent/
#
Loqi [Paulo Pinto] Why I Am a Bad Correspondent
#
[tantek] and yet Bridgy Published a photo on the tweet: https://twitter.com/w3bk3rn3l/status/1378311784696848393
#
@w3bk3rn3l Why I Am a Bad Correspondent: https://paulopinto.org/?p=2432 https://pbs.twimg.com/media/EyC_Q30WEAEiWzK.png (twitter.com/_/status/1378311784696848393)
#
aaronpk my first suspicion was going to be an errant author h-card in the html markup, but the markup actually looks good
#
[tantek] I was also going to guess a theme/markup problem, and yeah, that's why I posted the pin13 link
#
aaronpk 👍
ppinto joined the channel
#
aaronpk false alarm, it was posted with a different theme than we are seeing now
#
ppinto Problem happens with Independent Publisher theme but not with IW26
#
ppinto so, i'll stick with IW26
#
ppinto sorry for that
#
aaronpk so it is very likely a rogue microformat around your author info in the independent publisher theme
#
ppinto yeah, it must be. I find IW26 a better aesthetic choce, so it won't be a problem anymore
#
ppinto SenPress is also nice but syndication icons do not appear correctly
#
[tantek] ppinto you may also be interested in the #indieweb-wordpress channel where there's more frequent discussion of these and related problems specific to WordPress
#
ppinto yes tantek. I was trying to join via web interface but it isn't working for me. I will switch to indieweb-wordpress. Thanks.
ppinto left the channel
#
[tantek] great, no worries, and hopefully the problems have been resolved for now!
[scojjac], [KevinMarks] and Seirdy joined the channel