#Loqiaaronpk: [eddie] left you a message 2 minutes ago: what's the difference between an itinerary on your site versus a p3k-trip? Is it past versus present? Mode of transport? Something else?
#aaronpkitinerary is the intent to do something, and the trip contains the real data after it happened, usually including the actual GPS data
#aaronpkitinerary has properties such as individual legs of the trip with flight number, etc.
#[eddie]Aaronpk: cool, I think I'm gonna experiment with using a trip baseline. Because as I've been thinking about it, a "past itinerary" doesn't make sense but a "future trip" does. It's kind of like my media checking workflow: interested, in progress, finished. Trips might have a "planned, in progress, finished" status as well. ? ? ?
#[eddie]I'll play around with that idea, sneak peeks at your mf2, and experiment.
#ben_thatmustbemeaaronpk: i would completely disagree with that statement, that is not how you started micropub https://indieweb.org/wiki/index.php?title=Micropub&oldid=5288 majority of that page is under brainstorming, search for the word "MUST" on both pages, even just look at the first paragraph, with micropub you brain dumped ideas and it read as people welcome to put in ideas, microsub reads more like a spec that isn't open and
#KartikPrabhuwhy does astronomy get such a bad rep! ;)
#aaronpkjust because i've learned about spec writing over the past few years and now use clearer terminology doesn't mean the spec isn't "open"
#aaronpkif I didn't want feedback/edits, I wouldn't have put it on the wiki
#ben_thatmustbemethats the point though, you are still writing a spec, i'm saying don't because others don't have the skill of writing a spec and its going to be really offputting
#KartikPrabhuben_thatmustbeme: we are of course welcome to add a brainstorming section to the "spec" since it is on the wiki
#aaronpkI added a "status" section which mentions specifically that this is an early draft looking for feedback, and also an empty "indieweb examples" section so it's clear there are no implementations yet
#ben_thatmustbemethe header section and putting yourself as editor makes it even worse though IMO
#ben_thatmustbemejust wonder if that shouldn't be pushed down and have like, a protocol summary, simple flow, indieweb examples, background, etc, all up front, put the entire spec in a brainstorming section. hell even just starting it as 'login / auth is identical to micropub' and getting all of the stuff out of the way. the idea is to have really simple descriptions now so people can go off and experiment with it, not spec it
#aaronpki can move the auth stuff down lower. i wanted it on the page so it was easier to find rather than digging around all the other wiki pages
[eddie] joined the channel
#[eddie]I think the spec is useful, but I agree that auth could be summarized as "same as Micropub" and then have a details section down lower. Because I'll admit I skimmed all of the south pretty lightly to get to the "new stuff"
#[eddie]martymcguire[m] just sent you an experimental webmention. lol. I create h-cite listen posts marked up with an experimental “u-listen-to” property. Not sure how that registers in webmention.io, but to test it out I sent one to this week’s This Week in IndieWeb (https://martymcgui.re/2017/04/08/165106/). I’m guessing it’ll end up as a “Mention”, but let me know if you see anything interesting, strange or bad with the webmention
#Loqi[Marty McGuire] This Week in the IndieWeb Audio Edition • April 1st - 7th, 2017
#martymcguire[m]in seriousness: i think it's an interesting way to indicating moving sites or accounts, but it also raises a lot of questions in my mind.
#ben_thatmustbemeagreed, i doubt there is a "simple" solution. I'm honestly more just concerned about the other side of it, how can i tell that a new identity is the correct one? So i store as many URLs for a person as i can and try to link it back together so i know identities. ideally i should be able to look if the rel-me's are all pointing to a new URL, i change to using that as the primary
#aaronpkHonestly for most of this I think we don't need a technical solution
#aaronpkpeople get new phone numbers and you figure it out
#ben_thatmustbemeand then you get the silly people who just post their new number publicly on facebook
#martymcguire[m][chrisaldrich]: my display handling is a pretty simple mapping of the content from webmention.io, which sends "listen" posts as "link"s.
#martymcguire[m]without fetching the content of the source URL myself, there's no easy way to ID it as a listen.
#martymcguire[m]i will likely need to start fetching my own context data for things wm.io identifies as "link"s
#sknebelor you could ask webmention.io to include all u-xxx classes in some field
#sknebel(as in, ask aaron or send him a pull request that does so ;))
#aaronpkyeah the approach i'm taking with webmention.io (which gets the data from xray) is to be vocabulary-aware rather than passing everything through blindly
#[eddie]It’s tough, with something more experimental like listens, it does seem useful that it fallsback to link
#[eddie]Because if nothing else, with a p-summary/e-content, at least if the post says “Eddie listened to X”, if it’s a link then most webmention displays would show it. If we transform it into a listen, then there’s no backwards compatibility
#[eddie]Although, I guess I also don’t know that I wasn to spam all of martymcguire[m]’s mentions with “Eddie listened to X” haha
#[chrisaldrich]martymcguire[m] I was just noticing that. Why is WordPress always such a bear. Looks like you're picking up context which should be outside of the piece too. I'm working on some themeing this morning, we'll see if I can tweak it.
#[chrisaldrich]eddie I haven't added the example just yet as I'm still working on it. Ultimately it's also an example of what all WordPress sites that use Post Kinds will show up as too...
#martymcguire[m][eddie]: i think webmention.io understands updates?
#martymcguire[m]of course, my site doesn't update wms in realtime, so you'll have to bug me to look at it.
#[eddie]I was discussing the pros versus cons of webmention.io refering to my post as a “listen” versus a “link”
#[eddie]as a link, it gets backwards compatibility. But that also means on each of your podcasts you’re gonna get a mention “Eddie listened to X”, where as with a listen you could aggregate it like likes with a number of facepile.
#aaronpkif there are enough examples of publishing this property i'll add it to webmention.io
#[chrisaldrich]I think that /listen posts can be useful in showing the popularity of a particular podcast as "social" proof in some sense. And in the near term, they can spur the question, "How does she do that?", and "How can I do that?" which further indieweb in general.
#[chrisaldrich]GWG, I think modifying it to stay in line with other current mf2 would be worthwhile
#[chrisaldrich]may be worth looking at other types like watch, read, etc. too.
[cleverdevil] joined the channel
#[chrisaldrich]eddie u- is for wrapping URLs while p- is for titles &c in general.
#[eddie]Yep ? But a podcast should generally be a URL, right?
#[chrisaldrich]It depends on where the URL shows up within the set up and that could be nested inside other markup which includes a u-url if I'm not mistaken
#[chrisaldrich]I essentially think of likes, reads, watches, listens, favorites as bookmarks of a specific type of content. That may make things easier conceptually.