astrojuanlu[m], zoglesby, voss[m], myfreeweb, grantcodes[m], Rixon and plindner[m] joined the channel
#[tantek]a single space separates the URL (which must end in an image format file extension like png jpg jpeg etc.) and the "(" that starts the alt text, and then eventually a ")" that closes the alt text
#[tantek]that single space can also be a single line-break
iasai, [jgmac1106], [aaronpk], snarfed, [tantek], barpthewire, cweiske, KartikPrabhu, [frank], [Rose], jeremych_, [kevinmarks] and [Franco_Scarpa] joined the channel
#[Franco_Scarpa]Hi! I'm a bit confused. My personal website is hosted on Netlify, so only static files. How can I implement webmentions?
[frank] and [jgmac1106] joined the channel
#[jgmac1106]franco scarpa there have been some tutorials on netlify webmentions. I will look for them
#sknebel[Franco_Scarpa]: by having the webmention endpoint somewhere that's not just static. If you don't want to run it yourself, there is webmention.io offering that as a (free) service (but netilify functions could be an option, or lots of other hosting options)
#[jgmac1106]you can use webmentions.io to receive and telegraph to send...displaying is a different issue...let me look around
#sknebelyou then can that have store data, and add them to your pages during the netlify build (and trigger a new build once a mention has come in)
#LoqiI’ve made a few changes here, but hopefully, most of them went unnoticed. As I mentioned before, I’ve been wanting to invest more in my own site and content again. With so much I want to tackle—implementing WebMentions, syndicating book reviews...
#[Franco_Scarpa]Thanks a lot! As soon as I can I will read these resources! Thank you very much!
eli_oat, [tantek], iasai, [kevinmarks] and swentel joined the channel
#@redsweaterOn the @Blogger front, unfortunately we can confirm that Google has shut down the API that allowed @MarsEdit to upload images. Many customers have indicated they want to keep using Blogger even with this limitation, so we will continue to support Blogger without image uploads. (twitter.com/_/status/1107993081117323264)
iasai, [Rose], [tantek], snarfed, jgmac1106, gRegorLove, chrisaldrich, eli_oat, [kevinmarks], [jgmac1106] and swentel joined the channel
#snarfed!tell arush hi! just fyi your computer has been fetching https://brid.gy/twitter/megarush1024 at ~1qps (ie every second) for the last hr or so. (looks like your personal computer, not web server.) totally ok! just fyi since i'm guessing it's not intentional. :P
#[tantek]now I just realized the larger challenge I have, which is that when I link to a higher resolution of the photo and use that for syndication with u-photo, that there's no way for Bridgy (or any microformats consumer) to understand that there's an alt on the img inside that u-photo link
#[tantek]i.e. if you parse that post with a mf2 parser, it doesn't retrieve the alt on the img inside the a href u-photo
eli_oat joined the channel
#[tantek]Problem statement: I want to syndicate the highest resolution of the photo I have, while only displaying the medium resolution by default on my home page and post permalink (clicking through gets you the highest resolution version)
#[tantek]this requires using u-photo on the link around the img tag instead of directly on the img tag itself
#[tantek]OR I give up on syndicating highest resolution for now, and simply be content with syndicating the medium resolution from the img tag
#[tantek]Might have to go with that as an interim. The only place it matters is my syndication to Flickr which I was kind of treating like a backup of the full resolution but now I can't
#KartikPrabhuusing u-photo on the link sounds fine no?
#[tantek]yes that's what I'm doing now, however then the 'alt' is not associated with the u-photo
#KartikPrabhuthat way all the places your post goes to FLickr or readers pick up the highest resolution. Readers can choose to down-size it if they like
#[tantek]correct. however the 'alt' is not picked up therefore does not make it to the Twitter POSSE copy
#[tantek]checks Bridgy docs to see if there's some way to customize which URL is syndicated to Flickr
#[tantek]ok I think I need the equivalent of p-bridgy-twitter-content but for Flickr like u-bridgy-flickr-photo
#[tantek]!tell snarfed is u-bridgy-flickr-photo a reasonable feature request for Bridgy Publish, like p-bridgy-twitter-content, but for a custom photo (e.g. higher resolution) for Flickr? Or is that violating "keep Bridgy simple"? Asking before I file an issue requesting it.