#@ringmasterContemplating herd mentality today, and how it affects our choice of breakfast cereal, among other things. Also, how eating a “salad” sounds healthy, until you realize it has more junk calories in it than a Big Mac. (twitter.com/_/status/991283064750903297)
#LoqiSince @kanyewest’s tweets have apparently made this topic unavoidable, some thoughts on the history of the parties’ switch on civil rights.
short tweet test.
[John], [unoabraham], snarfed, KartikPrabhu, eli_oat and kaushalmodi joined the channel
#kaushalmodisnarfed++ Thanks for quickly fixing the case of retweeting mentions #bridgy
#Loqisnarfed has 61 karma in this channel (383 overall)
KartikPrabhu, tantek and leg joined the channel
#tantekaaronpk: with minimal code for the additional variants, now ~25 lines of code for my single emoji heuristic function
#LoqiSince @kanyewest’s tweets have apparently made this topic unavoidable, some thoughts on the history of the parties’ switch on civil rights.
short tweet test.
#LoqiReply to Kevin M. Kruse: Since @kanyewest’s tweets have apparently made this topic unavoidable, some thoughts on the history of the parti...
#ZegnatI would have expected the content of the tweet you are replying to to be in the content property of the h-cite. Note within the content of your own h-entry.
#skippyfair; but not something I'm likely to fix soon.
#tantekagreed with Zegnat, the h-cite should be inside the h-entry but not inside your own e-content
#tantek(and on that emoji detection code, that's the PHP version, the JS version is not as thorough, so I'm going to keep it just serverside for now until I have a need to put it in CASSIS for client and server)
#skippyi am trying to present the contents of a tweet to which I am replying.
rhiaro joined the channel
#ZegnatWould it be hard to port it to CASSIS tantek? What are you using, is the PHP version published somewhere?
#tantekskippy, then those contents should go in the reply context in the h-cite, not in your own content
#tantekotherwise it will be consumed as a quoted tweet, not as a reply
#tantekwhich is now making me rethink how I markup replies in general when they're in-stream
#jeremycherfasVery leased to report that after several head-scratching hours, the fold all command in bbedit came to my rescue to find an errant closing div tag.
#tantekhaven't implemented it yet, but figured I'd write down current thinking first
[eddie] joined the channel
#skippyi'm new to all of this, but it seems weird to me to place e-content around only my own contnet, and not also the blockquote to which I am actually creating contnet.
#tantekskippy that's the difference between entry and content
#tantekthe purpose of the entry is to place it around both your own content and the blockquote or whatever else is the context for your own content
swentel joined the channel
#tantekperhaps that would be a good clarification to note explicitly in h-entry
#tantekassuming that's good for minimal in-stream reply context, then next I'll work on in-stream "normal" reply context, e.g. comments on github issues, replies to tweets etc.
AngeloGladding and [miklb] joined the channel
#[miklb]tantek yes, that is definitely worth documenting/clarifying. I’m not sure I’ve heard that explanation before. Makes perfect sense though.
#aaronpkI don't think I've given enough thought for how i want to show reply contexts in my reader yet
#sknebel"Introducing Personal Data Deletion Callback: providing a callback URL to receive a person’s request that the info an app received from Facebook be deleted". that's an interesting addition
#snarfedguess i'll have to try and see what happens, as usual
#tantek.comedited /reacji (+135) "/* Reply Context */ add permalink and dt-published to markup example since in-stream" (view diff)
#tantekaaronpk - wait I'm confused - I thought you were already reading replies from people in your reader, and the problem was some had reply-contexts and others didn't?
#tanteklooks for the screenshots others took of all the thumbs-ups in a row
#aaronpkyes it just shows the in-reply-to URL right now
#tantekI think I'll still markup the h-cite because it's not that much incremental work for a reader to use it if it is there
#tantekto optionally show more human readable text than just the URL
#aaronpki'll probably make it work like my website's reply contexts soon, but i still want to think through the differences between using the h-cite that's there vs fetching the in-reply-to URL and using the canonical content
#tantek(since that h-cite will auto-imply name and url properties)
#tantekand you could show that while lazy fetching the in-reply-to
#aaronpkalso "just use the h-cite" isn't a shure thing because of all the differences in how those end up looking in practice. e.g. posts with a name vs only a note, how long is the text content, is there a photo, etc
#tantekI mean use the h-cite properties in a design of your own
#tanteke.g if the h-cite has a name, then show that instead of just the u-in-reply-to, but still link it to the u-in-reply-to
#tanteksince you're already showing the reply to URL, that kind of incremental improvement should be fairly painless and design-neutral
#skippygrrrr.... Omnibear is still having token troubles. :(
#tantekanyway, hopefully when I get this working you'll be able to see it all (with h-cite p-name) in my h-feed and see how that would look
sebsel joined the channel
#skippyoh, speaking of photos: post-type-discovery says "If the post has a "photo" property with a valid URL,
#ZegnatThe IndieAuth Token Endpoint gets the code from Omnibear with + in it, and will use that to ask selfauth about validity, and selfauth has never issued a code with scopes including + signs
#aaronpkthe other thing about that... why are the scopes included in the string at all?
#ZegnatAnd scopes are `\x21\x23-\x5B\x5D-\x7E`, so they fit within there.
#aaronpki hope they are stored server-side as well, since otherwise an app developer could just change the list of scopes when exchanging the code for a token
#ZegnatBecause we are stateless, nothing is stored server-side
#aaronpkyeah i wonder how small of a library it takes to implement JWS
#aaronpkJWT has vocab about all the key names, JWS is the enclosure/signing format
#ZegnatBut this one function I wrote is pertty clean. It contains both a known message for checking (from static info, like your URL), and can optionally have extra variable data (e.g. scopes).
#ZegnatBut I didn’t consider that URL encoding has 2 ways to transform spaces ... so there it falls apart.
#ZegnatIf only it wasn’t handled as part of a URL, he.
#ZegnatI wonder what the URL spec says, so if Omnibear is doing anything wrong here by using + for encoding.
#ZegnatOr if maybe selfauth is already not encoding it correctly.
#ZegnatOdd that Quill works though, does it ask for only 1 scope?
#ZegnatOh. Or it uses %20 I guess. Argh. base64 encoding patch coming up.
#sknebelthe + thing is in formencoded post requests, so I think omnibear is right
#schmartyaaronpk: i'm moving more feeds into aperture but running into issues w/ sites that don't advertise their feeds correctly. should i be able to plug in a URL directly to a feed into Aperture?
#schmartyis there a way to skip the preview step and say "this is a feed please deal with it"?
#skippyZegnat: what's weird is that Omnibear + indieauth/token was working recently. no idea what changed where to trigger this problem.
#aaronpkschmarty: if the preview step doesn't find anything then it probably won't find anything later either
#aaronpkunless it's a timeout problem, chances are it's choking on the actual feed data somehow
#schmartyi am stumped, since XRay can find the feed okay.
#Zegnatskippy, I couldn’t say. Did you server infra change, which may have affected the decoding step? Did you start using different scopes? So many possibilities. But this change should save us all the future headaches
[kevinmarks] joined the channel
#[kevinmarks]There is newbase60 which a few of us use
#aaronpkschmarty: yeah i'll have to dig into that later
#ZegnatYeah, I would have used a different encoding if it was meant for people. But this is meant for machines only. The only extra requirement was for it to be URL safe, which the JWS is. And JWS is a standard with decent following
#Zegnatmerged to master, feel free to update, skippy!
#aaronpkyeah and using newbase60 would involve writing code to actually encode/decode the text, whereas this just is a simple string replace leveraging the exsting base64 encode/decode functions
#sknebelif even more people suggest encodings I'm changing it to base2 over an alphabet of O and 0... :P
#skippy[01-May-2018 21:35:22] WARNING: [pool www] child 5 said into stderr: "NOTICE: PHP message: PHP Notice: Undefined variable: input in /var/www/skippy.net/public/auth/index.php on line 147"
#ZegnatYes. The Micropub client needs a long-lived token that it sends along with the Micropub requests to the server :)
#sknebelyes, and the actions need the token, so when it makes the action it can prove to your site that its allowed
#ZegnatFor pure logins, short-lived tokens are used. So those are the only ones my website ever produces. And those never contain scopes.
#ZegnatFrom #-chat. Wow. That JSONFeed issue list looks like a real mess ... is anyone actually planning to push the JSONFeed spec to a v2? Or is it basically dead?
#ZegnatSlightly tempted to add the mf2 version of my h-card as a rel="alternate" type="application/json", and then complain about how feed servers (e.g. Aperture) think that is a feed! :P
#skippyWTF? The redirect with token is still not succeeding. POST to selfauth succeeds, but the token isnt beting collected? Cleared cache, restarted browser. I am confused!
#ZegnatFeel free to PR that, and link to this chat as the fact that I checked that piece of code, and maybe someone will merge it. I am on my way to bed
#Loqi[Tantek Çelik] h-entry is a simple, open format for episodic or datestamped content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open microformat standards suitable for embedding data in HTML.
...
#aaronpk[kevinmarks]: that won't help encoding text as newbase60, you need more code for that
#Loqi[skpy] Sorry to revive this old issue, but I'm not seeing any syndication targets in Omnibear. Both Quill and Indigenous for Android correctly show that my MP endpoint supports syndication to Twitter, but Omnibear provides nothing. I've tried setting "Cus...
#[manton][cleverdevil] A feed preview would be useful to debug broken feeds too. Micro.blog spends a lot of time parsing invalid feeds, then trying again, and again... So it's on the to-do list but (as you said) hasn't been a priority yet.
#[cleverdevil]Totally fair, you've been doing a great job filling out higher priority things in the platform.
#aaronpkGWG: do you have a micro.blog account and have you added your site's feed to it yet so that people there can subscribe to you? that would be step 1
#aaronpkare you getting webmentions to your site when people reply to your micro.blog posts?
#[manton]@GWG You're feed looks pretty good to me, except for the "Also on Twitter/Facebook" links, which ideally would be removed from the feed you have in Micro.blog.
#tantekaaronpk, interesting, so you'd like to see in-stream h-entry's have explicit u-syndication to show in the UI?
#tantekGWG< presumably the bar at the bottom that shows date time then f t links
#GWGSo, that is coming from my u-syndication, I assume
#[manton][aaronpk] How does one of his short posts appear?
#[manton]In the feed I'm looking at, the end of each post has `<span class="syn-text">Also on:</span>` and then u-syndication links. Doesn't seem quite enough info to do anything smart with that part of the post.
#GWG[manton] I would be happy to exclude them from the json feed and enbed them as json metadata. You have a filter for that.