Loqijf2 is a working prototype of a simpler JSON serialization of microformats2 intended to be easier to consume than the standard Microformats JSON representation https://indieweb.org/jf2
jeremycherfasI don't particularly want to do it the way you did it, from the HTML; I'd rather use it as an opportunity to learn to use something else to do the job.
jeremycherfasThe problem for me is that because I have always worked at home, at least for the past 7 years, I have no extra time during the day and I think the next big thing I want to do on my site is implement responsive images with `srcset`.
jeremycherfasThe pizza photos were on Known. I'm talking about my main site. Sending anything to my own site would mean getting micropub beyond the very rudimentary stage it was at.
ZegnatUgh. I have been trying to avoid thinking about Micropub for a while, because I just know I will then end up building my own client from scratch again.
[LewisCowles]If anyone locally develops their site and wants to run software on a raspberry pi or single-board computer, or an intel NUC. It can be hard to test things like emails. I Just got github.com/CODESIGN2/mailhog-docker to support multiple arm architectures and 32-bit x86 in addition to armv7 and amd64. What has this got to do with the web and indieweb?
[LewisCowles]Many of us send emails. Testing that can be a pain. This allows you to simply update your config to point at wherever you are running mailhog and get full e2e email tests
[LewisCowles]I think adaptive fixed-width is progress, but it's a few steps back from some of the things we used to be able to achieve using flash; which I know is proprietary etc, but had some rich expressive qualities
jeremycherfasMaybe I'm misunderstanding. I thought the point was to let the bowser choose an image size so it wasn't downloading an unnecessarily large file only to downsample it.
[jgmac1106]indiemonster, indie crossing, webmentions vs zomboes, we need to roll out one of these games, indiemonseter was some geocaching so not a good social distance choice
[jgmac1106]yes that is the point, but to peter's point is a ton of work on the site mantainer whereas max-width=100% will work, IO step on my img down to 1280 and then use width=100%
petermolnarjeremycherfas: the funny bit is: no, no real overhead. Mobile resolution is often denser, than desktop resolution, meaning mobile would download the 2x, 3x picture anyway.
Zegnat!tell [jgmac1106] re: “indiemonster, indie crossing, webmentions vs zomboes, we need to roll out one of these game” do you imagine any of these need development? I could imagine signing up for an IndieWeb Game Jam
sknebelpetermolnar: so you just found that browsers don't really use the different variants and thus not worth the hassle of managing it? or other issues?
petermolnarsknebel: from my own tests, yes, that was the conclusion. In essence I don't want super resolution of my photos circulating/available, and the smaller resolutions don't make sense any more, because phone screens became quite dense.
ZegnatBrowsers do not stop downloading those halfway though, right? They may start rendering sooner, but are just as much a bandwidth bottleneck as any other big image
ZegnatBut agreed, if it turns out that browsers are not grabbing different images depending on network connection. Just go progressive JPG and a somewhat average image size for all visitors
jeremycherfasMy 100% width is 750px at max, I've toyed with breaking images out on either side of the text box, maybe 960, but on occasion that would crash into my sidebar, so I think I'll just leave things as they are. Many, but not all, are progressive jpgs, and those that aren't are PNGs, iirc.
ZegnatIt is a way of storing JPG so it can be rendered even before all data is in. So when you start downloading the file you can start displaying something and the more of the file you have downloaded the more detail you can fill in during rendering
[LewisCowles]file size is not their only consideration. I'm pretty sure low tech mag has an article about how algorithms affected their decisions. Either that or my brain has made it up. I feel confident of the former though
petermolnarthe argument is that these are similar in size, text in them is more readable, and they have better aesthetics; these are all reasonable points.
jeremycherfasI do most of my image manipulation in Acorn. That gives me the option to look at the original and the version side by side. Sometimes dithered PNG has a radically different colour palette, and then I go with jpg. But whereas I almost always do progressive jpg, I am not as careeful about interlaced png.
[tantek]For posting images, similarly I use 960px wide by default (for higher pixel density displays), and link to "full" resolution e.g. 1920x1440 for landscape.
[tantek]jeremycherfas yes it seemed reasonable, like at 2x pixel density that's 480 wide. and it's usually half the "full resolution" of 1920 which should mean fewer downsample artifacts
omz13Hello all. Work on building my own solution continues, and while the native format is microformat and the main API is micropub, I now seem to have a working WordPress/XML-RPC interface (as tested by MarsEdit successfully working with my test server). Mangling between microformats and what comes down that WordPress interface was somewhat of a challenge.
[tantek]welcome omz13! we also have the #indieweb-wordpress channel which you may find particularly helpful in getting setup with the right plugins etc., and any answers to challenges
[snarfed]yes! and sorry for that "k," i got channels mixed up. welcome omz! you're in good company w/wordpress here, GWG and i and others on it too. #indieweb-wordpress is a great place for it
TGiske, petermolnar and [prtksxna] joined the channel
[snarfed]feel free to sign up for readthedocs and look at granary there though! it still needs to be nudged to show the newly released 3.0 on https://granary.readthedocs.io/