#Loqi[tantek] I think yes (really need a "tweetstorm") and here's the two key reasons why:
1. **Lowest switching cost.** Tweetstormers would easily be able to switch to using the Known tweetstorm UI instead of their existing behavior on Twitter. Lowering that fri...
#Loqitweetstorm is a series of tweets, each replying to the previous, often each numbered so the sequence is clear, as a method of expressing a longer series of related thoughts as a single thread on Twitter https://indieweb.org/tweetstorm
#tantek.comedited /Falcon (+403) "/* Display Received Webmentions */ ways to view webmentions received" (view diff)
#aaronpktantek: the notes on the Instagram page have been updated since it first launched and it appears that the posts are discrete units now rather than each image having its own commetsn for example
#tanteksure, a collection is still a post / discrete unit itself that can have its own comments
#aaronpkBut the photos and videos in an Instagram post can't have their own comments
#tantekit's not a matter of what they can't have, it's a matter of what they can have
#tantekand I'm willing to be that that "can't have their own comments" is just a "there's no UI for them to have their comments". you can't actually determine that their data structure disallows comments
#tantekon the contrary, the existence of per-photo person-tags shows that there *do* exist per-photo properties in the data structure
#LoqiA gallery is a deliberately curated set of photos, that may itself be a post, or an archive view, or potentially dynamically created via tags https://indieweb.org/gallery
#schmartyReally interested in microcasts as a phenomenon.
#aaronpki actually really prefer short (<30 minute) podcasts in general
#aaronpkit's easier to commit to 20 minutes than 2 hours
#aaronpkalso actual radio has been doing essentially microcasts long before podcasts so it's kind of interesting to see it starting to turn back into that
#schmartyaaronpk: also curious what you use to make your percolator posts. I am looking forward to making some improvements to screech and am looking for feedback from users :)
#Ruxtononly feels that way because they're both short form content, the outcomes of both are very different imo
#tantekaaronpk: the IG multi-media post / OYG thing is perhaps an example of the challenge of building and running a PESOS service
#aaronpkMaybe, tho I think it's the same problem if I wanted to publish a mix of photos and videos and also build a reader that supports that
#tantekyou have to keep updating it whenever the silo adds features because there is an implication that the service will pass along whatever is on to the receiver
#tantekno the new content vs reader problem is very different
#tantekbecause we can design fallbacks so that existing readers still work / behave reasonably
[kevinmarks] joined the channel
#[kevinmarks]Instagram posts didn't have permalinks at all for a while.
[pfefferle], renem, KartikPrabhu, [xavierroy], sebsel and [kevinmarks] joined the channel
#LoqiReact (also called ReactJS) is an open source web framework created by Facebook that can be responsibly used (simultaneous client and server support) yet often abused for js;dr pages and sites https://indieweb.org/React
#barryfrost.comedited /Jekyll (+301) "/* IndieWeb Support */ Description of pull request to add Microformats to default Jekyll theme" (view diff)
gRegorLove and [xavierroy] joined the channel
#tantek[barryf]: looking at the diffs - I've never seen "hidden" used on an <a href> before - is that valid and customary practice somewhere?
#tantekalso the rel="me" links could be additional class="u-url" as well
#tantekand consider moving it higher up in the markup, perhaps right after the h-* that it applies to, just to make it more obvious which object the <a class="u-url" hidden ... > applies to
#tantekI was going to comment that on the commit but figured I'd just discuss it here :)
#[barryf]I was trying to ensure the <a> didn't break anyone's layout, just in case someone's stylesheet specifies it.
#aaronpkif you don't want people to use hidden <a> tags then yes
#tantekrather, should all u-url parsing do relative URL resolution? regardless of element or attribute it gets its value from?
#aaronpkyeah I think the u- prefix should be the indication that the value is a URL and should be resolved
#tantekthat's a pretty big change but it shouldn't break any existing working content, because such relative URLs outside of URL attributes don't work today anywa
#tantekthe argument for that is that dt-* parsing is also special in that regard
#Loqi[Zegnat] #10 When should u- values be normalised to absolute URLs?
#tantekdefinitely mention the use-case of wanting to use <data> for a relative URL instead of a hidden <a href> which is undesirable for all the usual semantics / screen reader etc. reasons
#aaronpkpretty sure i have some hidden <a> tags i've done this with on my site as well
#tantekwell then now that barryf's pull request is depending on that data u-url relative URL resolution, we ought to get at least one parser implementation to implement it
#Loqi[jonnybarnes] In the spirit of keeping things simple I’d have bridgy HEAD request the image linked to in `src`, if that can be POSSE’d then just abuse that. Even if a “better” valid image exists, in the `srcset`.
Then maybe we could reuse the code and d...
#Loqi[snarfed] sure! HEADing to check for size is easy. not all servers support it, sadly, but that's a separate question.
the main question here still seems whether and how to get the `srcset`'s image URLs into the parsed mf2 that bridgy and granary use interna...
#aaronpkhm i might know enough to do the PHP parser change
#aaronpk"if there is a video property and photo property and they each have only one value, then display as a video using the photo as the poster image"
#tantekevery post has a notion of h-entry with embedded h-card for the author
#tantekaaronpk - it's worth it to keep the simple cases simple for publishers
#tanteksince there are millions more of those than there are readers
#aaronpkwhat should a reader do if it encounters an h-entry with two photo and two video values?
#tantekand yes, building readers is hard, that's no surprise, and there are many other more important challenging problems for a reader far beyond any kind of parsing minutiae
#tantekthis is why I've put time into defining steps in Post Type Discovery
#tantekand also why we focus on real world cases instead of everything theoretically possible
#aaronpkmy point is it's not theoretical when building a reader because you have to make some decision about what to do, even if what to do is treat it as an error case
#tantekyes and such decisions should always be done by 1) what is out there today, 2) what is easiest to defensively code simply with less code
#tantekstep 1) should obviously be done per spec, in this case, per Post Type Discovery
#tantekif there's stuff missing from PTD on how to handle existing real world case, definitely file an issue for those with links to those real world cases
#aaronpkwell my immediate need is deciding how to translate all combinations of instagram multiposts into micropub
#aaronpksingle photo, single video, two photos, two videos, mix of photos and videos
#aaronpkthat sets a pretty high bar for accepting micropub requests for those
#tantekthat's the reality of the richness of what IG allows posting. they've raised the bar higher for the richness of their posts
[cleverdevil] joined the channel
#[cleverdevil]Okay, I'm exploring doing a sponsored open source plugin for Discourse to support Webmention (and potentially a few other things). My goal is to get DreamHost to pay to have it implemented. Are there any Ruby developers in the IndieWeb group that may be interested in working on such a project?
#[cleverdevil]I'd like to scope it out and get a little budget to see if I can get approval for such a project ?
#tantekperhaps start with who has written the Ruby libraries for webmention handling?
#tantekthey might be interested or know someone who is?
#tantekthough it may be more important to have experience writing webmention handling than Ruby experience per se
#tantekI for one would trust someone with multilingual programming experience that has webmention receiving implementing experience to be able to pick up the "rubyisms" fairly quickly
#snarfedpetermolnar may also have an existing srcset
#aaronpki'm designing the settings screen for OwnYourGram and it's getting kind of overwhelming
#aaronpkalso starting to think it might be useful to have a way for micropub clients and servers to know about what features are supported automatically
#aaronpkmore like capability negotiation, not content negotiation
#tantekbetter to try to see if you can design the interactions with fallbacks so that things "just work" with existing implementations, and if there's richer content, the implementations can upgrade and get it as they see fit
#tanteksuch "negotiation" protocols typically add a lot more complexity to all sides, fragility, bugs, etc.
#aaronpkwell i'm essentially making manual switches so people can choose what kind of requests to receive
#tantekconneg waas supposed to be simpler than arbitrary capability negotiation, and it's still kind of a joke on the web because nearly no one supports it or handles it well outside of obscure formats
#tantekaaronpk if I Bridgy Publish a multiphoto of say 8 photos, it only sends the first four to Twitter, and the first one to Flickr, and the first one to FB
#aaronpkah but that works because bridgy knows the limitations of the thing it's sending to
#tantekother direction (POSSE vs PESOS), but similar reasoning applies to OYG
#aaronpkin OYG's case, it doesn't know what limits the server has
#tantekdefault to single item, let people opt into collections
#tantekbecause as soon as people start adding per photo tags or add *one* video in the mix it will oddly fail
#aaronpkmy site supports multi-photos via micropub, but not collections via micropub. and micro.blog supports multi-photos via micropub as well, and has no concept of collections
snarfed joined the channel
#aaronpkmicro.blog also doesn't support person-tagging *at all* so that information is already lost anyway
#LoqiA multi-photo is like a photo post, except just with multiple adjacent photos, either in a series, or tiled / arranged in some layout https://indieweb.org/multiphoto
#tantekright, didn't need that one since it was only mentioned in a question in chat
#tantekor rather, always better to answer the " is " question with the proper capitalization since Loqi search will find it regardless of how you ask the next time, but links on the wiki require the proper capitalization
#gRegorLoveOops, I was mistaken. I thought Loqi search and wiki search weren't case sensitive, though.
#aaronpkoh right, XRay doesn't support instagram multi-photos yet either
snarfed joined the channel
#tantek.comedited /Instagram (+645) "/* Features */ collections, limitations, note stories support various tags/labels/stickers and pinning them to moving things" (view diff)
[barryf] and [chrisaldrich] joined the channel
#[barryf]cleverdevil: I've no Discourse experience but would be happy to help out, maybe in a supporting role.
#tantekaaronpk heads-up because it seems maybe you noted off the top of your head: swarm checkins limited to 7 photos, IG multiposts limited to 10 items