[tantek]GWG there are interesting points raised, and I'm not sure whether to discuss here in dev or in #microformats because the issues get to the heart of well designed minimal vocabulary development
[tantek]the challenges are broader than "just" status, and github issues are not well designed for higher level design discussions (github issues are good for fine grained issues, but solving that way can result in lack of higher level coherency)
[tantek]1. productivity use-cases (which I know [jgmac1106] is eager to somehow figure out / use), like you're on to-do list, next-actions, completed actions, perhaps some forms of personal project management in general
[tantek]2. consuming media, reading/watching/listening to books/video/audio of various sorts, whether starting, in-progress / partial progress, or completion
[tantek]4. possibly overlapping with passive experience use-cases such as /sleep as well. How is a two hour nap post different than a two hour watched a movie post?
[tantek]overall point being: separate vocabulary for each and every one of those will likely result in unnecessary bloat of property terms, many of which will look a lot like each other, and when you have many things which are similar it just presents confusion to new people. Why do AAA and AAB seem to specify the same thing just for different specific experiences?
[tantek]6. travel - when you "experience" a flight, train, subway ride, that's similar to having watched a movie, with start and end times etc., but with likely different start and end locations
[tantek]7. amusement park attractions / rides. whether going on a roller coaster which has the same start/end location, yet apparent start/end times (perhaps fixed / expected duration?), or on a park-themed form of transport like Disney's Monorail (which may or may not be same start/end location), these seem to resemble /travel posts yet be somewhat different (perhaps in intent?)
[tantek]other amusement park rides are more like a "movie" in that you stay in literally the same place and experience something "around" you (maybe 3D or nD with various other effects like mist and smoke)
[tantek]so my point is that all this media related posts discussion spans everything from productivity posts, to eating, to travel, to amusement park rides
Loqiwant is a rare post type on the indieweb, where the author posts something (acquisition) or experience (book to read, movie to watch, venue to checkin, food/dish they'd like to try) they want get or do https://indieweb.org/want
[jgmac1106]I get that and I think folks want to think on status of media post types, but yes if those same future, start, finished properties could work on an h-event
[tantek]whereas what's right (or at least better) is understanding / documenting use-cases first from purely a user perspective (why do you want to publish? what would a consuming application do that is special?) and then analysis of related use-cases (noting that my 1-7 above), and only after some reasonable modeling of that, perhaps based on prototypes, discussing how the plumbing (e.g. vocab) *might* work
gRegorLoveI understand my own desire to post "want to read..., reading..., finished reading" posts, and how I might filter those locally, but that doesn't strictly require more than a tag since it's just local.
[jgmac1106]dt-start, dt-end I think would work for almost all the use cases tantek pointed out above...the want to me doesn't fit as it is not time bound....dt-future or something
[tantek]you need to come up with a consuming use-case that is special to that particular kind of post. if you can't, that's a good indicator that you really should not put in the effort to design any sort of plumbing for that kind of post
gRegorLoveGWG: sticking with the /read example, you could build those recommendations by parsing the read-of. The status portion wouldn't be necessary, right?
LoqiA book is a written work typically longer than an article, on the indieweb, there are examples of publishing whole books on IndieWeb sites, and publishing lists of books https://indieweb.org/book
[tantek]what if you have the option between reading a book and watching the movie version of a book (not hypothetical, actually had this option in a couple of highschool and college classes)
[jgmac1106]I think there is a ton of prior art of people tracking their bookshelves, doing goodreads, etc..wellI I am gona step out trying to see if I can publish a checkin post before my layover is over
LoqiA library in this context typically refers to a software library, and sometimes to a physical library, like a personal library that an independent may use to collect books they have read https://indieweb.org/library
LoqiIt looks like we don't have a page for "bookshelf" yet. Would you like to create it?_e (Or just say "bookshelf is ____", a sentence describing the term)
LoqiTo read or reading is the act of viewing and interpreting posts or other documents; on the IndieWeb, a read post expresses that something has been read, like a book or section thereof https://indieweb.org/read
[tantek]one way to document consuming use-cases is to document *existing* consuming use-cases that do something *special to that kin of "post"* and document that special thing with *screenshots*
[tantek]anyway without documenting these use-cases in a persistent organized form (see /wikify) then your use-case conversations will just keep going round and around without making any progress towards understanding the problem(s) better
[jgmac1106]I really don't think it is that confusing, people want to mark read, watch, and listen posts with todo, started, and finished as folks are used to tracking this in GoodReads, Plex, and trak.tv
[tantek]ever-expanding, e.g. /sleep is a type of /metrics post which is a form of passive /exercise that happens to be stationery unless you're on a sleeper car on a train or plane in which case your sleep has different start and end locations
gRegorLove[jgmac1106], marking posts with those things doesn't necessarily require a special mf2 property, though. We're looking for special consuming use-cases and examples of them in the wild to document it first... then maybe a new property might come out of that.
[tantek]such real world cases is what tends to drive the design towards multiple properties to represent different aspects, that may (or may not) make sense when combined, since some combinations do already pre-exist, and trying to come up with a discrete taxonomy that attempts to separate them (especially hierarchically) ignores the messiness of actual human actions
LoqiA watch is a semi-passive type of post used to publish that you have watched a video (movie, TV, film), or a live show (theater, concert) https://indieweb.org/watch
[jgmac1106]just load the map. I can put in the exact address and nomatim will tell me I need extra information..the only way to get "extra" information is just strip everything down to Chicago, IL
[jgmac1106]think I will try mapbox, no way am i typing in every address for a checkin...me building a checkin was a stretch goal anyway since I got stuck in airport
[snarfed]"what do consumers need to do that's special?" is a great q. i feel like i fully own my to-read, in progress, and read list, but it has zero mf2, and I'm totally fine with that, since I'm the only consumer.
[tantek]Really trying to resist the trap of attempting a grand theory of human intention, action, and experience to model all the variants of kinds of posts we discussed earlier.
Loqicweiske: [eddie] left you a message 6 days, 15 hours ago: regarding multiple micropub endpoints, there are a couple things. Omnibear *could* add multiple endpoint support. You could also add multiple "destinations" into your endpoint, and one destination could forward it somewhere else. I'm not sure if Omnibear support destinations, but again, that could be requested.
sknebelyeah, I don't think treating sending/receiving differently is a "trend" - since they share little to no functionality, it's how it's mostly done
sknebel(on the other hand, the "user feature" "webmention support" often means both, so distributing it as one thing, e.g. as a plugin, still can make sense (and e.g. allow to turn receiving off), even if the underlying code is distinct
[chrisaldrich], mapkyca__, placer14[m], Ja3ood[m], jeremych_, gnunicorn[m], gorhgorh[m]1, Tianyi[m], [mrkrndvs], neverstopeating[ and [jgmac1106] joined the channel
[tantek]sknebel, I have mixed feelings about calling "webmention support" a "user feature". It does help awareness of an open W3C standard that users should make sure their tools & services support, yet it doesn't speak to how the user benefits
[jgmac1106], [Zegnat] and [jgarber] joined the channel
[tantek]I *think* the user feature(s) is/are something like: "posting responses" (user version of "sending webmentions support", and something like "peer to peer comments" ("receiving webmentions and displaying them support")
[jgmac1106]Random idea.. If folks did have preferred pronouns in their h-card coukd you use self identified gender to weight discovery in feeds... Show me posts from thpse who self identify by....
[jgarber]Took me forever to get around to this PR, but if there are any Rubyists with some spare time… Would you mind giving a look at this PR on the webmention-client-ruby gem? I’d be most grateful for your constructive feedback.
sknebel[tantek]: that's why I choose the "" around it - and in practice, right now, its probably protocol-specific... E.g. an activitypub plugin for some CMS could probably also provide P2P commenting
[benatwork], [jk], [tmiller], eli_oat, [cleverdevil], [schmarty], [gRegorLove], M[AXEL]Darr[m], [tantek], macerbi[m]1 and [Jamey_Sharp] joined the channel
[Jamey_Sharp]HTML question: I have something that almost works entirely without JavaScript and I'm trying to eliminate the last bit. Is there any way, without using JavaScript, to get a click event to set the `src` attribute of an `iframe`? Using `<a target="name of iframe">` will navigate the iframe the same way that setting `src` would, but it doesn't actually change the value of `src`. 😢
[Jamey_Sharp]no, that works in the sense that the link target opens in the iframe, but it doesn't do what I need because the `iframe src` attribute doesn't change.
[Jamey_Sharp]I was using hidden radio buttons and `<label for>` to handle the interactivity but I _also_ need to change which page is loaded in an `iframe`. I handled that by loading _all_ the pages in separate iframes and using CSS to make only one of them visible, but then browsers want to load all those pages ASAP, which is Not Ideal
mapkyca__, eli_oat, leg, BenLubar, jgmac1106, mblaney and [Jamey_Sharp] joined the channel
[Jamey_Sharp]I've deployed a version of http://reader.minilop.net which doesn't make your browser load all post contents up front, but does require a tiny bit of javascript. With javascript off, it still kinda works but the navigation doesn't update to reflect which post you're reading. Something to keep playing with...
KartikPrabhu, valuemachine, [tantek] and [schmarty] joined the channel
@AaronGustafson↩️ I’m sure it’s not a shocker given my focus, but I went with a blog post as it’s more interesting. JS-only features:
1. Read aloud
2. Save offline
3. Navigation highlight (which I need to switch to `aria-current`)
4. Webmention updates on load
5. Live webmention streaming (twitter.com/_/status/1144744006661758976)
@AaronGustafson↩️ All features are, of course, gated by feature availability, so it’s considerably more nuanced:
* Read aloud requires SpeechSynthesis
* Save offline requires Cache API
* Webmention updates requires `template` & `array.filter()`
* Webmention streaming requires WebSockets
* etc. (twitter.com/_/status/1144744905715007488)
@chipotlecoyote↩️ Local font hosting (that's the really easy one). Local accounts, maybe w/IndieAuth. GoAccess for analytics initially, moving to Fathom, maybe, when usage justified it. (twitter.com/_/status/1144753514863742976)