2014-12-29 UTC
KartikPrabhu and tantek joined the channel
elf-pavlik, michielbdejong, mlncn and tantek joined the channel
# 01:41 tantek.com edited /HTTPS (+74) "emphasize *today* for obtain, don't need any vapor here diluting the effectiveness/actionability of this section. move Let's Encrypt to possible future" (
view diff )
# 01:45 tantek I'm not a hug fan of announcements >6 months before supposed ship dates.
# 01:45 Loqi tantek meant to say: I'm not a huge fan of announcements >6 months before supposed ship dates.
mdik_, clintpatty, KevinMarks, agaric, Acidnerd, KartikPrabhu and KevinMarks_ joined the channel
# 03:39 asdofindia If there are href="" links on a page, it'll refer to the current URL from inside the browser. But it's not good, right?
# 03:46 KevinMarks_ !tell Tantek Facebook's present continuous "likes" is coherent, but also serves them as they like to imply that liking a brand is ongoing permission for it to post to your feed
# 03:46 Loqi Ok, I'll tell him that when I see him next
# 03:48 KevinMarks_ !tell ben_thatmust I have an Android notify app built for twitter that I'd like to add webmention support to - let's collaborate
# 03:48 Loqi Ok, I'll tell them that when I see them next
# 03:49 KevinMarks_ Asdofindia: it's not terrible. If you want to force a refresh use hrefj"
j12t joined the channel
# 03:56 GWG KevinMarks_: Can I ask about this Android thing?
# 03:58 KevinMarks_ Twitter android client has logged us all out, and fails when we try to log in again
# 03:59 GWG KevinMarks_: I meant... I have an Android notify app built for twitter that I'd like to add webmention support to - let's collaborate
# 03:59 GWG I was curious about what the Android notify webmention thing
# 04:05 KevinMarks_ Ah, I have an app called flowpast that turns selected tweets into android notifications
# 04:06 KevinMarks_ I need to update it for lollipop and would love to add webmention support
# 04:06 GWG KevinMarks_: You've inspired me to update the wiki
# 04:08 ben_thatmust KevinMarks_: that would be great. I was just going to try to see what I can do with phonegap though, i don't know what it supports/doesn't support
# 04:08 ben_thatmust obviously indie-auth will have to be all done on its own as there isn't a URL to redirect to
KartikPrabhu joined the channel
# 04:09 ben_thatmust I just got a Moto360 as a gift too, so i would love to add android wear support
# 04:10 GWG I got an LG G Watch refurbbed cheap. But I still don't like it as much as the Pebble
# 04:18 ben_thatmust I'll dig in to it KevinMarks_ I may be looking at starting from scratch with phonegap first, hopefully get it working on lots of other platforms too
crystal_, KartikPrabhu and wolftune joined the channel
KartikPrabhu and tantek joined the channel
KevinMarks_ joined the channel
# 05:42 Loqi tantek: KevinMarks_ left you a message 1 hour, 55 minutes ago: Facebook's present continuous "likes" is coherent, but also serves them as they like to imply that liking a brand is ongoing permission for it to post to your feed
# 05:44 tantek that actually makes sense as "liking a brand" is essentially a proxy for "following a brand"
# 05:44 tantek and thus having their posts show up in your "reader" view (AKA news feed) makes sense
# 05:45 tantek that's interesting as "favors" implies relative to something else
# 05:47 tantek Right, Flickr diluted the meaning of "favorite". Or perhaps IE did.
# 05:47 tantek favorite in common parlance implies above other choices
# 05:49 tantek it's odd that "favorite" became a toggle, as it's "normal" meaning is favorite among a set
# 05:51 tantek in common terms, you have *a* favorite color, *a* favorite movie, etc.
# 05:59 tantek they might as well have called the feature "Besties"
snarfed joined the channel
# 06:03 tantek wow how did you find that post asdofindia! That's an old one!
KartikPrabhu joined the channel
# 06:08 tantek alright I'm going back to actual useful design iterations - not sure this favorite semantics tangent has any indieweb relevance
# 06:12 tantek only if you're doing it towards building something
# 06:13 KevinMarks_ Fair. Android changed a star in contacts to the word "favourites" in the latest version
# 06:14 tantek it (favorite people) is a dumb patch of a bad UI anyway (contacts). the right answer is to go straight to people-centric comms as blogged. citation in /comms
# 06:15 tantek no need for a contacts app when you can arrange your contacts by their faces in home screen pages and folders
# 06:16 tantek all the mobile "contacts" default app UIs are badly polished 1990s turds
# 06:21 tantek even Apple's "Contacts" just looks like bad Lotus Notes or PalmOS from back in the day
# 06:23 snarfed KevinMarks: just fyi, the twitter app on my phone is working fine. it hasn't logged me out
KartikPrabhu and KevinMarks__ joined the channel
# 06:39 kylewm more lovely UX from android twitter app... it's asking me "Authorize SNS to use your account?"
KevinMarks_, KevinMarks__ and KartikPrabhu joined the channel
# 06:57 KevinMarks__ Interesting snarfed. It happened to a lot of people - apparently they have servers with clocks set to 2015 breaking auth
# 06:59 snarfed KevinMarks__: wow. you think they have production servers with *three days* worth of clock skew? hard to believe
j12t joined the channel
KartikPrabhu, musigny, eburcat, daf, mlncn-agaric, tantek, kerosene_, friedcell, KartikPrabhu1, eschnou, danlyke, michielbdejong, prtksxna and petermolnar joined the channel
j12t, Sebastien-L, stream7, dns53, friedcell1, csarven and Kopfstein joined the channel
mapkyca joined the channel
# 12:32 hugoroyd so, i'm now on the extra-info branch
# 12:32 hugoroyd which just had Pages/Callback.php | 2 +-
# 12:37 hugoroyd mapkyca: it works this time
# 12:44 mapkyca ahh... didn't check this window - glad it's working for you now! (new flickr plugin just captures the nsid from the api, so it's a small change)
Sebastien-L joined the channel
# 12:45 mapkyca updated the importer to catch the error - basically it wasn't handling the old style syndication structure very well.
# 12:45 hugoroyd thanks for the plugin
# 12:45 hugoroyd i also fixed the video typo :)
# 12:46 hugoroyd if you like fixing bugs, this one is quite annoying :)
# 12:55 mapkyca I can see that! I'm sure this is'll be on the todo list somewhere, but the fix may be a migration script... essentially a find and replace on the database. :/
prtksxna joined the channel
# 12:55 hugoroyd mapkyca: yeah that's what i thought :-)
# 12:55 hugoroyd do you know how to use mongo a little bit?
# 13:08 mapkyca A very little (although I'm on mongo myself), my thoughts is that this could be done at the object level (see comments on the bug)
# 13:09 hugoroyd mapkyca: this could be a test for the export functionality of known ;-)
# 13:15 mapkyca @hugoroyd true, that'd be one approach. For that matter, a find and replace on a JSON dump might be somewhat easier to accomplish...
# 13:21 hugoroyd mapkyca: yeah i'm trying to figure out how to get to edit that dump ^^
# 13:22 hugoroyd i only get "bson"
# 13:30 mapkyca hmm... I get a zip with plain text json... admittedly in separate files. Might need some script-fu...
davidmead, Sebastien-L, KartikPrabhu, prtksxna and veselosky joined the channel
# 15:14 ben_thatmustbeme hmm realized i should just have a feed of recent webmentions, then IFTTT can notify me of changes
# 15:30 aaronpk and then one step better than polling using PuSH to notify consumers that the feed has been updated
snarfed joined the channel
KevinMarks and prtksxna joined the channel
gRegor` joined the channel
# 16:31 aaronpk ok yeah definitely that is the next clustering of notifications
# 16:31 aaronpk when a single post sends webmentions to multiple pages on the domain
eburcat joined the channel
# 16:38 aaronpk davidmead: interesting. ownyourgram sends your instagram caption as the "content" field which is meant to be the body of the post, not the title
# 16:39 aaronpk so it must be Known deciding to save it in the title instead
# 16:39 aaronpk ownyourgram also sends a "category" field with the hashtags in your photos, so Known could be looking for that as well
# 16:40 davidmead good to know. maybe I can bring that up to @benwerd, or post it as an isuue on github
# 16:42 davidmead could the #hashtag be parsed to the “content” and leave the rest in the “title”?
# 16:43 aaronpk sure, but that may not always make sense for everyone
# 16:43 aaronpk for example I have several friends who type really long captions on instagram, way too long for a title
# 16:44 aaronpk in that case it may make more sense to use the hashtags as the title and the caption as the content
# 16:44 davidmead i’m trying to think ahead. the hashtags can be clicked when in the content of a Known post to show just those posts. this setup at the moment destroys this
# 16:45 davidmead it creates links out of them when it finds it in the body/caption
# 16:46 aaronpk i was assuming it was like wordpress where posts get a separate list of tags
# 16:47 davidmead no. i’m off to grab some lunch. love to chat more this afternoon. feel free to comment on the post @aaronpk :-)
davidmead, wolftune, gavinc, myfreeweb, j12t, tantek, KartikPrabhu and friedcell joined the channel
mlncn-agaric joined the channel
# 17:47 tantek looks like I set aside 'f' as shortener shortcode character for favorites/likes
# 17:48 tantek likes will have a very different presentation / interaction than any of my existing post types thus it makes sense that they get a very explicit different post kind internally.
# 17:48 ben_thatmustbeme hmm, need to figure out a way to get my google health data (steps per day) to output some other way than manually
# 17:49 aaronpk tantek: I discovered why you are seeing a lot of favorites on twitter.com/aaronpk/favorites that are not on my site
# 17:49 aaronpk Twitter displays favorites in tweet order, not sorted by date I favorited them
# 17:50 aaronpk so when I favorited three old tweets from my site, they actually show up way down in my list on twitter
# 17:50 tantek that's not as useful, and certainly isn't user-centric (the date order you favorited would be you-centric, which for your profile/favorites makes sense)
# 17:51 aaronpk I suspect there was some sort of technical reason for doing that
# 17:51 aaronpk since favorites don't get their own tweet ID, whereas RTs do
benwerd joined the channel
# 17:53 tantek strange that they don't store it, since they do transmit it via the API
# 17:54 gRegor` Twitter favorites have been like that at least a year
# 17:54 aaronpk I also don't see the date the user favorited a tweet returned in the API
# 17:54 tantek the act of favoriting, since Bridgy sees it, then sends it on, and you see it in dated lists e.g. on Adactio's posts, when people faved his POSSE tweet for a post.
# 17:55 tantek therefore the information does exist, they are simply not storing it
# 17:55 aaronpk bridgy is reading the list of favorites of a tweet from the HTML page
# 17:55 gRegor` Yeah, Twitter favorites aren't delivered in the API
# 17:56 gRegor` as far as I remember what snarfed has said
# 17:56 aaronpk gRegor`: they are, but they are just a list of the tweets, not a list of "favorite" actions
asdofindia joined the channel
KevinMarks joined the channel
# 18:01 tantek how often is Bridgy checking twitter for favorites?
# 18:03 tantek in checking adactio's site for faves, I found this
snarfed, stream7_, KevinMarks and frontwards joined the channel
# 18:18 tantek thus the time of favoriting is known, even if only via the time when webmention received from Bridgy
Erkan_Yilmaz joined the channel
mlncn-agaric joined the channel
# 18:25 tantek that's an abject lesson in *too* featured an API
# 18:25 tantek the API being one where both yyyy and YYYY are included when 99.9999% of the time you only want yyyy
# 18:25 tantek perfect example of why you should NOT implement more than what is needed by real world use-cases
# 18:26 tantek as opposed to what someone put in another standard ISO-8601
# 18:26 tantek KevinMarks: that's a different argument, and only applies to me since I don't know anyone else that uses dayofyear
# 18:29 KevinMarks it is one of those hard things - you want datetime stuff abstracted for you, yet abstractions leak
# 18:29 friedcell we use iso year & week for data tables in db :)
gRegor`_ joined the channel
# 18:29 friedcell had this problem last year when we still had no users (shipped in january)
michel_v joined the channel
# 18:30 friedcell we're partitioning incoming data into weeks and iso weeks are standardized
# 18:30 tantek a huge source of infrequent errors, which are the worst
# 18:31 tantek if you're looking for week-level partitioning, allow me to suggest you use 5-day weeks, as specified in newcal.org
# 18:31 friedcell it doesn't really matter - dates come in in any timezone, get isocalendar() and decide where to look for data
# 18:31 friedcell pythons isocalendar() on date objects makes this easy
# 18:31 tantek it does matter - the less "obviously" inspectable the data, the more prone it is to bugs
# 18:32 KevinMarks it's all incommensurable somewhere. 5-day weeks stutter on leapyears
# 18:32 tantek KevinMarks: they do not. the leap day is added at the end
# 18:33 tantek the alighnment of January 1st is alwasy maintained
# 18:33 KevinMarks can we just adjust the solar system so that the earth, moon and sun's orbits are integer multiples?
# 18:33 friedcell we use table inheritance
# 18:33 friedcell so you could just get the data from the parent table
# 18:34 friedcell if you number weeks the most common numbering is iso weeks
# 18:34 friedcell it's somewhat confusing, but not nearly as confusing as timezones & summer times…
# 18:35 tantek iso weeks were a design error and worth ignoring as legac
# 18:35 Loqi tantek meant to say: iso weeks were a design error and worth ignoring as legacy
# 18:35 tantek as the compromise of year alignment was an error
# 18:36 friedcell the 5 day week is also kinda confusing
# 18:36 friedcell dates in march and after will be in different weeks depending on year/leap year
# 18:36 friedcell not sure that's better in any way
# 18:36 tantek no - in newcal, the leap day is at the end of the year
# 18:37 tantek thus no it is not true that dates in march and after will be in different weeks depending on year/leap year
# 18:40 friedcell tantek: slow net, finally managed to open link. interesting, but was talking about conversion from gregorian to newcal
benwerd joined the channel
# 18:46 tantek KevinMarks: I have not yet explored proleptic newcal but there is no reason they shouldn't work as well as (or better than) proleptic Gregorian.
# 18:47 friedcell not saying iso year/week are practical for every day use, but neither is UTC for everyone - it's just a way of storing data in a way that all buckets are the same and every point translates to a single point in what users use
# 18:49 tantek.com edited /like (+2065) "/* Brainstorming */ add mark up a simple favorite of an indieweb post, an indieweb article, collapsed sequential favorites" (
view diff )
# 18:49 KevinMarks a good heuristic is round-tripping conversions and then testing a long range of them
# 18:50 tantek it's not just a matter of practical or not, it's a matter of how fragile the encoding, how often it results in cognitive dissonance when inspecting data to verify it, which means eventual corruption is far more likely. in that regard (data fidelity longevity) iso weeks are horrible and should be abandoned.
# 18:52 tantek aaronpk, others working on "like" posts - I've expanded my design of "like" posts from notification, text only, hypertext, to now sample markup for that hypertext.
# 18:52 aaronpk excellent, that is the same markup that I'm using
# 18:53 tantek note how the h-cite one simply extends the existing <a class='u-like-of' href> without using a new container for the h-cite
# 18:53 tantek which should make it easier for consuming code
# 18:54 aaronpk the consuming code doesn't care about the html elements used though
# 18:54 aaronpk it will see the "like-of" property as an "h-cite" object instead of a plain string
# 18:55 friedcell tantek: since most ppl use gregorian any nongregorian storage will result in cognitive dissonance
# 18:56 tantek friedcell - correct. hence I have opted for dayofyear (which is ISO8601 as well, yet properly year aligned) storage as a transition.
# 18:56 KevinMarks for some definitions of most (when's the Chinese new year again?)
# 18:56 tantek as well as the use of the new concept of bims
# 18:56 friedcell KevinMarks: most of my users :)
# 18:56 tantek bims are different enough from any Gregorian concepts to minimize dissonance
# 18:56 friedcell tantek: was looking at daily tables but that seemed like overkill
# 18:57 friedcell postgreSQL exports checks in ddl so where each date fits is obvious + I have everything set up so you can just use the root data table for selects and insert which renders anything "inside" that an implementation detail
# 18:58 aaronpk snarfed: out of curiosity why don't you have a photo in the IRC logs?
# 18:58 snarfed aaronpk: i'm being obnoxious and stubborn and want it to pull from my site's h-card :P
# 18:58 tantek snarfed - is there an issue filed for that against the IRC log generators in github?
# 18:59 aaronpk plz file an issue and it will probably magically happen
# 18:59 friedcell in any case, gotta run.
# 18:59 aaronpk that seems like a smallish task for when I need something small to work on
# 18:59 tantek GWG - you happened to resist in the same way that snarfed did
# 19:00 GWG I'm not being obnoxious and stubborn. I'm procrastinating.
# 19:03 GWG Along with fixing other people's icons on my site.
# 19:04 tantek GWG - do you have a Twitter icon? You could use that in the interim
# 19:04 tantek out of procrastination - why reopen a decision you already made?
# 19:05 tantek or rather, why not re-use a decision you already made until you have time to make a better one?
# 19:05 snarfed (woo, good irc notif message for native like. glad that worked.)
# 19:05 aaronpk except it's wrong, I liked that post, not a post that linked to that
eschnou joined the channel
# 19:11 KevinMarks hm, I suppose I should change my santa hat twitter icon back in deference to the US xmas season being over
shiflett joined the channel
# 19:14 KevinMarks hah. that's another day of year bucketing format - US holiday expected
# 19:19 aaronpk omg the url shortener at pin13.net is getting spammed like crazy
# 19:19 aaronpk i just made 2 shorturls on it and realized the IDs were separated by like 70 even though I made them within minutes of each other
reidab and dorian joined the channel
# 20:00 tantek now that I've figured out the presentation / design / markup that I want for "like" posts, the rest is coding it. but first lunch.
# 20:01 tantek (note the use of implied p-name for all the h-entrys)
# 20:01 aaronpk I'm confused about the "u-like-of h-cite". I thought you couldn't use an h-* on a property unless it was p-*
# 20:01 tantek (to keep the markup extra minimal - thus finding a use case for h-entry implied p-name that we never had before)
# 20:01 aaronpk it's a parsing level question though, doesn't change the way I consume it
# 20:02 tantek aaronpk - as spec'd you can put h-* on any property element
# 20:03 tantek specifically: "if that child element itself has a microformat ("h-*" or backcompat roots) and is a property element,"
# 20:03 tantek a "property element" being any of the "parse a child element for properties (p-*,u-*,dt-*,e-*)" in the previous step
# 20:03 aaronpk okay. the result is the same whether it's "p-like-of h-cite" and "u-like-of h-cite" though right?
# 20:04 tantek because u-* and p-* get their *value* differently
# 20:04 tantek does it get the URL for the u-like-of or not?
# 20:05 aaronpk did you expect it to have two values? one being the h-cite object and the other being the URL?
# 20:08 tantek aaronpk - all property elements with embedded microformats have the value and the object
hadleybeeman joined the channel
# 20:09 aaronpk I don't understand what you expect the parsed result to look like
# 20:09 tantek ah I see what is wrong, this: "value": "Aaron Parecki's \n article \"A Little Twitter Developer History\""
# 20:09 tantek should be this: "value": "http:\/\/aaronparecki.com\/..."
# 20:09 aaronpk also in practice I have found very little use of the "value" property in general, since it usually ends up having unexpected results
# 20:10 tantek it is the flat value you can use if you don't care about the nested object
j12t joined the channel
# 20:12 aaronpk okay so the parsers aren't returning the correct value for that?
# 20:13 tantek right - I see where the misinterpretation of the spec occured and am fixing
# 20:14 kylewm huh, does this mean reply-contexts should also be "u-reply-to h-cite"? so that the value is the in-reply-to URL?
# 20:14 tantek wow that was subtle find. I knew what I meant when I wrote the spec, and it sounds like every implementer interpreted it consistently among themselves, but differently than what I thought I specd!
# 20:14 Loqi kylewm meant to say: huh, does this mean reply-contexts should also be "u-in-reply-to h-cite"? so that the value is the in-reply-to URL?
colintedford joined the channel
# 20:16 aaronpk funny. well as a consumer, I have never used the "value" of those
# 20:16 tantek aaronpk - because apparently the "value" was broken!
# 20:17 tantek whereas the point was you could / should have been able to!
# 20:17 tantek the point is that adding more embedded markup / structuring shouldn't screw up the existing property
# 20:17 aaronpk in every consumer I've had to check if a property such as "like-of" is a plain string or a nested object
# 20:18 aaronpk if it's a nested object, then I pretty much assume there is a "url" property and find that
# 20:18 tantek and if it's a nested object, you should be able to simply get the "value" of that object
# 20:18 kylewm I don't think that is true if the reply context is complex, though right?
# 20:18 tantek you should only go into the nested object if you specifically care about *that* nested object
# 20:19 tantek kylewm the goal is to make the simple cases simple to publish *and* consume
# 20:19 tantek you're right that a more extensive reply context could be more complicated to both publish and consume
# 20:19 tantek but let's at least get the simple cases working simply on both sides
# 20:19 KartikPrabhu wait, so is i have <div class="u-in-reply-to h-cite"> lots of stuff <a class="u-url"></a> </div> then the value of the outermost u-in-reply-to should be the u-url of the embedded h-cite?
# 20:21 aaronpk you wouldn't nest an <a> inside another <a> would you?
# 20:21 tantek broken code examples will lead to bad reasoning
# 20:23 tantek this whole conversation started with a use-case
# 20:24 KartikPrabhu p-* does not usually have "value" attribute in it, so why add it only when an embedded object exists?
# 20:24 tantek because it's only necessary when an embedded object exists
# 20:24 tantek to avoid burdening the consumer with having to understand the embedded object
tantek joined the channel
# 20:27 kylewm so my problem is that now aaronpk has to handle three cases "in-reply-to" is a string, an object with a "url" property, or an object with just a "value"
KartikPrabhu joined the channel
# 20:27 aaronpk snarfed: okay I *actually* fixed the notification text now :)
# 20:27 tantek kylewm the general model is that it simplifies consumers of *any* microformat property to string or object with "value"
# 20:28 tantek the object with a "url" property step is something context/meaning/object specific that is being added
# 20:29 KartikPrabhu but from the pov of someone parsing replies it is still the 3 options kylewm mentioned. you now have to check 3 things
# 20:29 tantek KartikPrabhu: you have always had to check for those 2 things, on every microformat property
# 20:30 aaronpk I guess what I'm struggling with is when I would be able to safely assume the "value" property has something usable
# 20:31 tantek you should assume if you get an object where you expected a string, that you should just get the "value" out of that object
# 20:31 aaronpk I can't think of an example when that has happened
dorian joined the channel
# 20:32 aaronpk if I encounter an h-card, I am likely expecting it
# 20:32 tantek but if all you want is a string name to show for a p-author
# 20:32 tantek KartikPrabhu: you don't - you shouldn't have to
# 20:32 tantek aaronpk - there are plenty of text string only use cases
# 20:33 aaronpk i'm just saying I have never had that happen to me
# 20:33 tantek the point is that *any* property can have a h-x-something embedded on it
# 20:33 aaronpk I think what KartikPrabhu is saying is how do you know if the "value" property is something created intentionally by the author or the automatically implied value which may not be what the author expected to appear there
# 20:33 tantek so *any* property you are retrieving and expecting a string for, if you don't get a string (i.e. it's an object), you have to go get the "value" from that object
# 20:34 aaronpk I have had this same thing happen when trying to use the "name" of h-entrys, where the implied name parsing often generates unexpected and ugly results
# 20:34 tantek the "value" property is always intentional by use of the p-* u-* etc. class
# 20:34 tantek aaronpk - that sounds like examples of bad h-entrys that need explicit p-name properties
# 20:35 aaronpk the problem is as a consumer I can't tell whether the value was implied or explicit
# 20:35 tantek right that's a problem for tools like indiewebfiy.me to help fix
# 20:35 tantek aaronpk you shouldn't have to - that's the point
# 20:36 aaronpk or I have to just completely ignore the "name" property since it may be ugly
# 20:37 aaronpk but as a consumer I can't expect that everyone has correctly formatted h-entrys
# 20:38 tantek it's a simple enough publisher thing to fix / get right that it shouldn't be your problem
# 20:38 aaronpk no, if I could expect properly formatted hentrys then I wouldn't need code that checks for things and then tells them to go to indiewebify
# 20:39 aaronpk what you're saying is I need to code some knowledge of what is a valid h-entry and reject things that don't pass
# 20:39 tantek well we're back what are you actual real world needs for "code that checks for things" then
# 20:39 aaronpk which means I can't just blindly expect h-entrys I encounter are valid
# 20:40 tantek no, you need to document real world examples of things you think are ugly
# 20:40 tantek patching a symptom is not necessarily the best approach
# 20:40 kylewm making me think I need to turn off my logic for detecting auto-generated names
# 20:42 tantek (though it could be argued I should separate the name explicitly from the published)
# 20:42 kylewm sorry, what I mean to say is it detects names that are not an explicit title
# 20:43 aaronpk I have two links where an h-entry has an implied name and *no* content property
# 20:43 tantek kylewm that's not the most discoverable way to capture something :P
# 20:44 tantek on that page, with the concrete real world examples that you have
# 20:45 tantek but you're talking about a publisher issue, not a consumer issue
# 20:45 tantek if you've found links with bad h-entrys that's an h-entry issue
# 20:45 aaronpk no I'm talking about as a consumer, what do I do when I counter that
# 20:45 tantek consuming them, e.g. for comments, is just one use-case of that
# 20:45 tantek aaronpk - no - see above where I said "patching a symptom is not necessarily the best approach"
# 20:46 tantek investigating what went wrong is more important
# 20:46 tantek we can't figure that out until we analyze the real world examples which we can't do until you document them
# 20:48 aaronpk so now I don't know if it's a problem with trying to return an mf2 result from mf1 or what
# 20:48 tantek aaronpk - then that's even more interesting! hence why you need to document them!
# 20:49 tantek right - document them so you don't have to be the only one analyzing them
# 20:49 tantek since h-entrys are what you are having a problem with
# 20:52 kylewm snarfed: hey what feed reader do you use with twitter-atom?
tilgovi joined the channel
# 20:55 tantek aaronpk sounds like perhaps the default wordpress core hentry with broken themes (that lack the rest of the hentry properties) is the source of the problem
# 20:55 tantek hmm - perhaps mf1 backcompat parsing should not get any implied properties.
# 20:56 tantek (since no mf1 authors ever expect implied properties to happen)
# 20:56 Loqi tantek meant to say: (since no mf1 authors ever expected implied properties to happen)
# 20:56 tantek much better than you having to patch your code!
# 21:00 kylewm those themes are broken even in mf1 aren't they? (should have entry-title)
# 21:00 tantek kylewm: yes that is what I meant by "broken themes (that lack the rest of the hentry properties) is the source of the problem"
# 21:03 kylewm skipping implied properties for backcompat doesn't seem like it fixes the actual problem then. just side steps it
# 21:04 tantek kylewm: I disagree - "actual problem" is determined by what's documented.
# 21:04 kylewm using mf1 as a heuristic for "probably badly marked up"
# 21:04 tantek that's not the heuristic at all (strawman :P )
# 21:04 tantek the conclusion is: no mf1 authors ever expected implied properties to happen
# 21:05 tantek thus perhaps we should take that into consideration
benwerd joined the channel
# 21:09 voxpelli aaronpk: or you want something that's marked up in a way that an app can parse? that's tricky when a site uses my Disqus-like WebMentions
# 21:09 tantek aaronpk - sounds good - stub the wiki page with them!
# 21:09 aaronpk voxpelli: well presumably they're coming from some service so you could always provide the /mention-app with that URL
# 21:10 voxpelli aaronpk: yeah, I'm thinking of exposing the mentions as h-entries and perhaps RSS at an endpoint one can point to
# 21:11 voxpelli and ideally there would be some markup one could add to the original site to enable discovery of that other page – perhaps a simple rel-alternate or something
# 21:12 Loqi Ok, I'll tell him that when I see him next
# 21:13 tantek !tell barnabywalters nvm aaronpk added you. And welcome back!
# 21:13 Loqi Ok, I'll tell him that when I see him next
# 21:15 aaronpk that will result in a single h-entry with multiple urls?
# 21:15 tantek oops that was not the markup I had in my head
# 21:16 tantek lost when typing and didn't see it when reviewing
eburcat joined the channel
# 21:19 tantek.com edited /like (+62) "/* markup for hypertext design */ fix multiple in-stream sequential like posts markup - was intended to be multiple h-entrys, and use p instead of div" (
view diff )
uranther joined the channel
# 21:20 aaronpk the only problem I see with the new markup is that the second two entries have a name of just "aaronpk's photo" instead of "likes aaronpk's photo"
# 21:21 aaronpk (also there's a space that looks out of place ( 23:45) instead of (23:45)
# 21:21 tantek I could use an abbr to make an explicit p-name with "likes" in it
# 21:22 aaronpk i guess I don't really care that much because as a consumer I do my own thing as soon as I see it has a like-of property, and pretty much ditch the rest of the properties
# 21:22 tantek yeah darn the extra spaces from trying to make markup look easier to read
# 21:22 aaronpk but for consumers not looking for "like-of" it would be nice if the name had something that made more sense
# 21:22 tantek aaonpk - I figured, however it is still good to provide good p-name fallback for any h-entry
# 21:25 aaronpk so the reason I wanted to see what other people do on their /mentions-feed is I am considering making that page entirely third-person text, the only place on my site where third-person text would appear
KevinMarks_ joined the channel
# 21:26 tantek.com edited /like (+143) "/* markup for hypertext design */ use explicit p-name for cleaner result in simple h-entry readers, and abbr for expanded standalone p-names for second and later likes in a sequence" (
view diff )
# 21:27 tantek aaronpk updated now with explicit p-name and abbr for explicit "likes " on each h-entry
# 21:27 tantek also the space " " time problem should be fixed ;)
# 21:28 aaronpk tantek: now that you're doing explicit p-name you don't have the problem of the extra space
# 21:29 aaronpk there's no content for the h-entrys now, just a name
# 21:29 tantek it is likely that consumers of the h-entry will display the published time separately anyway, thus including it in the p-name would look bad in those consumers
# 21:30 aaronpk that's a good example of an h-entry that is intended to not have a content property (or value)
# 21:30 tantek the p-name is sufficient for anyone doing display to use it anywhere the need to display *something*
# 21:30 tantek as previously documented on comment presentation
# 21:32 aaronpk KevinMarks_: yes I've seen that problem on other sites from bridgy WMs
# 21:33 aaronpk but I thought that problem was actually from the wordpress WM plugin
# 21:35 voxpelli I'm pondering how to present a "like" in a mentions feed, aaronpk
# 21:35 voxpelli Because one post can both comment on one post on my site and like another
# 21:36 voxpelli So the "like" status is in the relation to a specific post rather than in the post itself :P
# 21:36 aaronpk I don't think I've seen any "like" posts that are anything but a like
# 21:36 kylewm KevinMarks_: aaronpk: well that's a faithful reproduction of how bridgy presents the like ("X favorited this" and "favorited this" appear separately). so maybe an issue that needs to be fixd in bridgy
# 21:37 aaronpk kylewm: maybe the bridgy favorites should drop the content property
# 21:38 aaronpk consumers not looking for "like-of" would then just use the "name" which would say "X favorited this"
# 21:38 voxpelli KevinMarks_: Yeah, I so need to fix that issue, adding support for likes will get a long way in that
# 21:38 snarfed if someone is confident they can get the bridgy markup and content right so that it displays nicely in default comment presentations, ie that don't do anything special for likes etc, i'll *happily* merge a PR
# 21:39 snarfed (markup is very much not my thing, so i'm unlikely to do it myself)
# 21:40 snarfed voxpelli: ah, i assumed these examples were more recent. if it's better now then great!
# 21:40 aaronpk kylewm: snarfed: yeah looking at this again now that tantek wrote up his markup example, i'm pretty sure dropping the "content" would be the correct thing to do
# 21:40 snarfed aaronpk: hrm. does that assume consumers detect and handle like-of, etc?
# 21:41 aaronpk if you don't look at like-of you'd just see the "name"
# 21:43 voxpelli aaronpk: any ideas on how to in a mentions feed handle a page mentioning multiple of your pages?
# 21:44 aaronpk I was thinking something along the lines of "... commented on a post that linked to _____, _____ and ____"
# 21:46 voxpelli Yeah, something like: "Post X liked Z and replied to A, B and C "
# 21:47 aaronpk well a post is never going to be a like *and* something else
# 21:48 voxpelli are you sure? on Twitter it's pretty usual that someone both likes and retweets somethings
# 21:48 aaronpk a like might mention another page though, like the bridgy notifications of "X liked a post that linked to Y"
# 21:49 voxpelli is it written anywhere in the wiki that a post can only be a single kind of interaction?
# 21:50 aaronpk just saying that "like" posts will only be a like, and not a like *plus* some other type
# 21:51 voxpelli ok, so just a single type of interaction (+ possibly mentioning/linking to something else), but possibly be such an interaction for many targets
gRegor` and tilgovi joined the channel
# 22:05 aaronpk the first link there seems to have dropped the "like-of" property
# 22:06 voxpelli I think one could represent a like, reply + reshare as that as just a reshare with a comment
# 22:07 kylewm yeah I noticed that too; most of acegiak's posts were "liked and reposted" but now just "reposted"
# 22:07 voxpelli But it poses the question what interaction to pick if multiple are available. Or one can just do what tantek suggested earlier I guess – and point out that they should fix it.
crystal and wolftune joined the channel
# 23:02 aaronpk benwerd: I've got a funny problem if you have a minute
# 23:02 aaronpk I don't know how the routing thingy works in Known, but for some reason that get() function is running even when I make a POST request
# 23:08 benwerd (I'm wondering if something is causing a redirect, eg on the HTTPS check)
# 23:09 benwerd Is this on a local installation / somewhere else?
# 23:10 aaronpk I don't think so, I was just seeing a plain http response with the contents of the get method
# 23:10 aaronpk somewhere else, was working with anomalily on setting it up on her site
# 23:12 aaronpk I installed it on a subdomain of mine and it worked fine
# 23:17 aaronpk doubtful, it's a relatively simple shared hosting provider
# 23:19 benwerd wondering if they have a freaky mod_rewrite implementation or ...
# 23:23 aaronpk I got as far as identifying what was happening, but didn't know enough about Known to track down the problem further
benwerd joined the channel
# 23:33 aaronpk any idea why that POST would fail but other POSTs work?
veselosky, tilgovi and Reykjavik joined the channel