#[tantek]Looks like Twitter is downsizing my portrait images down to ~750px wide anyway (and my "medium" resolution is 960px wide) so I won't lose anything to Twitter by syndicating just my "medium" resolution images there
#[tantek]Similarly it's only displaying landscape images at ~770px wide. So in either case my 960px "medium" resolution is fine for Twitter.
#snarfed[tantek]: re u-photo on link w/bridgy publish...hmm! interesting. i see your u-bridgy-flickr-photo prototype. it's not supported yet. :P i'm open to it...but do you know of any other prior art for u-photo on <a>s? i wonder if there's a more general way to specify multiple alternative urls for a given u-photo. maybe srcset? https://github.com/snarfed/bridgy/issues/592
#Loqisnarfed: [tantek] left you a message 34 minutes ago: 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.
#Loqi[petermolnar] #592 responsive images with srcset
#[tantek]snarfed, the only prior art for u-photo on <a>s is what I've been doing until today π
#snarfedwould "use highest possible resolution" satisfy your use case?
#[tantek]I think if we can figure out how consuming code would like to get at different resolutions, then yes mf2 should parse it
iasai joined the channel
#[tantek]and then yes, use highest possible resolution would solve the use case for POSSEing images
#[tantek]presumably to all POSSE destinations though right? (which would be ok I guess unless I started to run into destination size limits)
#[tantek]I don't really feel good about just kicking the can down the road for handling srcset syntax
#[tantek]that is, I'd expect clients consuming mf2json to want something structured for the different image URLs and sizes, rather than a big string to parse
#[tantek]then you have to do your own logic to iterate through the srcset array and look at the "size" values and judge accordingly
#[tantek]not sure we can simplify the size values at all, they're already pretty minimal
#snarfedyup the latter. i don't really know anything about srcset though so my vote may not count a lot
#snarfedalmost all image data in bridgy/granary already looks like that structured latter option anyway. (AS1, AS2, all silo APIs, etc). mf2 is the exception
#[tantek]also I'm worried about the nontrivial amount of coding on both the publishing and consuming side to support srcset
#[tantek]like literally I don't know of any CMS that provides a UI for multiple resolutions and publishing srcset
#snarfedsure. i doubt any of them have alternatives either though, eg to do anything like your prototype. at least not exposed in UI
#[tantek]whereas linking a thumbnail (or other medium resolution) to a full resolution is a common (automatic) pattern I believe: user uploads full resolution, CMS downsizes it for "common" viewing pages
#snarfed(CDNs, galleries, etc may do it under the covers)
#snarfedah sure, thumbnails yes. mostly automatic, but yes those are in UIs
#[tantek]but usually just that - two levels, "normal" and high resolution when you click
#snarfedcool. i'm open to srcset or anything else to help there. not sure u-bridgy-*-photo is the best approach, seems much too narrow, but i'm open to discussion
#[tantek]that won't be parsed by an mf2 parser in any form of association
#[tantek]another approach is if anyone else thinks that a[class~="u-photo"]>img[alt]:only-child pattern is useful more broadly, then we could move that to mf2 parsing
#[tantek]yet I'm *very* hesitant to do so if I'm the only use-case
#[tantek]Yes the u-bridgy-*-photo approach is very narrow, but that also means it is very conservative, and precise, simple, testable, narrowly scoped for all the above
#snarfedsure. i just don't know that it helps inform any broader solution(s)
#[tantek]Anyway, there's a few options. add srcset to mf2 parsing, add a[class~="u-*"]>img[alt]:only-child to mf2 parsing, add u-bridgy-*-photo to Bridgy
#LoqiBridgy has 2 karma in this channel over the last year (4 in all channels)
iasai joined the channel
#ZegnatReading the conversation, nice work on the multiphoto with alt POSSE, [tantek]! :D
#ZegnatMy first feeling towards a[class~="u-*"]>img[alt]:only-child is a little sceptical. Feels like that would move away from the meaning of u-*. srcset sounds like the right point to work on imo
[tantek], iasai, jamietanna, [Rose], [pfefferle], jamietanna[m] and [kevinmarks] joined the channel
#jeremycherfasCan anyone recommend a tutorial for SimpleXML? I am having such trouble wrangling the beast that is the Overcast OPML as arrays that I am looking longingly at a simpler solution, but I have difficulty in grasping how to address nodes. Something that starts with basics would help.
#ZegnatUuh. Iβd recommend using DOMDocument instead, which takes away some weird edgecases that SimpleXML has (in my experience)
jgmac1106[m] and [grantcodes] joined the channel
#[grantcodes]!tell tantek: re your photo sizes with mf2 I ended up having to use data elements for my use case, which is slightly different. I know it's not best practice but lets parsers pick up the highest res images. Not tried it with alt attributes yet though
#jeremycherfasOK zegnat; is there a good place to learn about DOMDocument that you would recommend?
#ZegnatI am actually looking around if I find any good tutorials, jeremycherfas :)
#jeremycherfasThanks! In the meanwhile, I am going to go for a little walk to clear my head. Maybe I will come back with a solution to filleting my array.
#[jgmac1106][tantek] do you have good resources for doing details and summary correctly for accessibility. The WebAIM articles I keep reading mention bootstrap accordion..
#[jgmac1106]I am assuming same rules apply or do screen readers treet details and summary someway automatically?
eli_oat, snarfed, [aaronpk], [kevinmarks], [kimberlyhirsh], [grantcodes], [frank] and [cowglow] joined the channel
#[tantek]Jeremycherfas Zegnat I use DOMDocument Iβm pretty sure in my /Falcon PHP for accessing/updating my flat files storage
#Loqi[tantek]: [grantcodes] left you a message 3 hours, 14 minutes ago: re your photo sizes with mf2 I ended up having to use data elements for my use case, which is slightly different. I know it's not best practice but lets parsers pick up the highest res images. Not tried it with alt attributes yet though
#[tantek]Grantcodes yes consider getting alt to work in your setup, I have a feeling it may make you rethink how you publish photos
#LoqiIt looks like we don't have a page for "details" yet. Would you like to create it? (Or just say "details is ____", a sentence describing the term)
#[tantek][jgmac1106] havenβt found a lot of use for details summary myself, yet
#[tantek]Could you start a stub page with your existing IndieWeb use cases for it and example posts that use it?
[grantcodes] joined the channel
#[grantcodes]I don't know how much I'd actually want alts on my photos though to be honest, since I almost always publish photos with a name or content that usually describes the image. But my site will handle alts if they are sent via micropub
#jeremycherfasThanks, but here's the thing. I can actually parse the OPML fine, into a multidimensional array. And I can extract the data I want from it. What I am trying to do now is to extract only those elements that have changed since the last time I obtained the OPML.
#jeremycherfasHuh. I wonder how that got there. Thanks for that. I will go back and look at the code that generates the json.
#jeremycherfasI'm also pretty sure that the if() on l.15 is not working the way I want it to, now that I look, because the break just sends it back into the outer loop, whereas I want it to exit both loops.
#[tantek]cweiske, I'm curious what problems you have experienced with DOMDocument. I just checked and I've been using it just fine for over 9 years on my site (though perhaps my usage is quite simple).
#cweiskefor simple tasks, simplexml is much more suited. the domdocument api is much more complicated
#cweiskein simplexml you simply do a $doc->path->to->my->tag['attribute']
#cweiskeand fetching attribute values also requires manual iteration over $attributes, until you find the right one
#[tantek]yes I have found I have to write a bunch of code to use it
#cweiskeinstead of saying "get me the value for attribute with namx $x
#[tantek]I do need XPath though, for extracting various microformats properties when I don't know the exact path-to-my-tag because there is no such exact path
#cweiskeextracting microformats the prime example for needing domdocument
#cweiskewhile extracting values from "normal" xml with a defined tag structure is easier with simplexml
#jeremycherfasCweiske I don't know how it got there, but array_pop seems to get rid of it.
#jeremycherfasRight now, I need to get the more comp[licated part working. And actually, I know for a fact that I will never need the last element, because all I want to do is find the elements before needle is found.
#jeremycherfasCould also, I guess, instead of if() use do while element !=== $needle
[jgmac1106] joined the channel
#[jgmac1106][tantek] yeah will do going to be using it for rubrics, doing a session at IWC New Haven...going to be using nested h-entries and flexbox inside details and summary...right now only place I use it a ton is on my resume...will do a stub after I teah Accra how to get their notes and photos on wiki
#[tantek]thanks [jgmac1106], and especially for helping out with Accra! Was going to tweet about all the HWC this week (a record 11! including 10 cities, 3-4 which are new!) but then Twitter unhelpfully suspended my account
#jeremycherfasI was having problems with array_diff before, but now I see that might have been because there were null elements. I may go back to that, now that I know.
#[jgmac1106]here are the notes...want them to add to wiki....teaching how to sign in ...but I can't remember my password and work is blocking the password reset
iasai, [kimberlyhirsh], chrisaldrich and gRegorLove_ joined the channel
#jeremycherfas!tell [kevinmarks] I like your use of $shiny and $legacy, and with your help and cweiske's I may even have solved my problem without needing to compare the arrays. I'm just storing a crucial key value and using that.
#LoqiCweiske has 14 karma in this channel over the last year (23 in all channels)
jackjamieson, [eddie], KartikPrabhu, MylesBraithwaite, mattl and [davidmead] joined the channel
#[davidmead]This maybe a silly question but, if I add a field into a Known plugin, do I have somehow add it in the DB structure separately? Or does it it get added automatically when itβs used?
jimpick, [tantek], jackjami_, [Rose], barpthewire, [schmarty], gRegorLove_, [kevinmarks], KartikPrabhu, snarfed, iasai, [jgmac1106], [pfefferle], dougbeal|mb1 and [aaronpk] joined the channel