#gRegorLovewhat's the websub feed Loqi subscribes to for indieweb mentions? I'd like to figure out why my mentions to gregorlove.superfeedr.com don't show up
#tantekthis update was inspired / forced by your $ request
#tantekwherein you had to separately type in-reply to tantek.com and then start your note with @tantek. whereas you should be able to start your note with @tantek.com and Quill should automatically turn that into a reply-to tantek.com
#[manton]The Micro.blog replies start with aaronpk and the Brid.gy ones don't. Which makes sense... But I was just kind of thinking about the inconsistency and whether Micro.blog should remove that first @-username from the content.
#petermolnaralthough there is truth in the notion that it might just be simpler to use json
#sknebelI'm not a fan of nested objects/lists of objects in TOML syntax
#sknebeland yes, familarity is also important if it's for humans to touch
#sknebelthere are a few attempts at further tying down the details of JSON, one of those might be interesting, assuming there's adequate parser support (subset of JSON is nice as a concept, but if the parser isn't enforcing it because you use a normal JSON parser you loose some benefits again)
#sknebelsome of the unclear bits in JSON are quite ugly
#sknebelsee having to put 64-bit numbers in strings to make sure they get across or the recent couchDB security fail due to differing handling of duplicate keys
#ZegnatIs the ECMA JSON standard also unclear? I know there were complaints about json.org as a spec, but thought that was why the ECMA doc was made?
#ZegnatI wonder if strictyaml still allows arrays as dictionary keys. That is a YAML feature that I have never understood. Not listed as a thing they remove.
deathrow1 joined the channel
#sknebelZegnat: ECMA neither addresses duplicate keys nor does it specify how parsers are supposed to treat numbers in edge cases
#sknebel(for reference, the couchDB bug: https://justi.cz/security/2017/11/14/couchdb-rce-npm.html - the part of the system that validates permissions and the one enforcing it handled duplicate keys differently, so you could tell the second one you're an administrator without the first one stopping you)
tantek joined the channel
#ZegnatHmm, I wonder if I could teach XRay to parse Tumblr blogs
#ZegnatEven on own domains with custom HTML themes, it looks like Tumblr may be injecting some SCRIPT tags at the top of the HTML. So they are recognisable.
#Zegnatfiles that under interesting thoughts for later
[pfefferle], KevinMarks, jjuran, tantek and KartikPrabhu joined the channel
#GWGsnarfed, I just added a lot of icons. Khurt wanted untappd.
tantek joined the channel
#GWGBasically, scripted adding new ones. Going to do the same to rel me
#aaronpk[eddie]: I think many formats are accepted but iso8601 is the best
#Loqiaaronpk: [eddie] left you a message 1 hour, 17 minutes ago: When compass says “before - specify a full timestamp” how is a full timestamp formatted?
#Loqiaaronpk: [eddie] left you a message 35 minutes ago: Nevermind. I realized its the same as the ‘localtime’ attribute returned in the geocode
#tantekthat is, still accepting it as user-entry as part of a reply (and setting user expectation that it is a reply to a specific person), but then just moving that part of the content to the reply-context
#gRegorLoveI show the display name in the reply-context, not the @-name. Not doing multi-replies, though.
#gRegorLoveWell, I guess Twitter is doing the multi-reply for me, but on my site I only show the reply-context for the tweet I'm replying to.
tbbrown joined the channel
#GWGHow do I decide if I've done enough for a major version bump?
#ZegnatI like semver. BC are major bumps, else not. But I see multiple projects who then start shoving feature updates on those same major bump updates, which in my mind just needlessly delays the features from launching. Because they want a major bump to feel like something meaningful and big. Which IMHO semver isn’t about.
#ZegnatI don't think it is part of the mf2 spec. Instead I think it is up to the consumer to find the right parsed object. Much like how you might have to sort through multiple h-card on a page to find the one with the matching u-url.
#KartikPrabhufragment handling could be an "extra" feature of some parser
#ZegnatSo a consumer would walk through all h-entry objects and check for a u-url that includes the fragment.
#ZegnatWhere consumer is something consuming the mf2 parser output
#KartikPrabhuif a consumer already knows that the relevant information is in some fragment of the page, it would be more efficient to not parse the entire page
#gRegorLoveGWG, chrisaldrich: Tangent - Know where the h-as-reply is coming from in Chris' page there? That should be removed from IndieWeb plugins afaik
#ZegnatKartikPrabhu if the consumer knows beforehand it can do what xray does and only supply the specified part of the DOM to the mf2 parser.
#gRegorLoveI don't know how XRay is doing it, but I suspect it might be null because the vcard isn't on the same element as that fragment ID? It's a child of it.
#ZegnatIIRC xray parses the DOM looking for the element with the specified ID and then gives that element and all its children to the mf2 parser. Thus only parsing part of the page or fetched.
#ZegnatThe way mf2 parsing is currently implemented: yes.
#aaronpkIt seems like that'd be a good feature for libraries to implement but it's not part of the parsing spec
#gRegorLoveAs it is now, I don't think fragment handling would go into php-mf2, unless the spec is updated. Otherwise it might be good for a helper lib, like Barnaby's php-mf-cleaner.
#gRegorLoveNot opposed to it being in the parsing spec, but that's a discussion for #microformats
#ZegnatI personally also think it is good that it isn't in the parsing spec. Mf2 parsing is now only concerned with turning HTML into objects. Not where the HTML is coming from, what subpart of it that needs to be read, or even if the HTML is valid.