#GWGgRegor`: I just hate to roll my own interface when there is one already, but considering the new API doesn't yet have taxonomy support, which I need, I may put into place my thoughts on endpoints...
#shanersKartikPrabhu there's no way that i could open source iamshane.com to anyone in any useful way, but it's important to me to open source software. thus, the rebuild / cleanup.
#npdotyanyone who advertises support webmentions, and does the recommended check to prevent webmention spam, could be used to request/attack another site
#npdotyI'm not sure the expiring endpoint makes a difference
#kylewm"acting as a auth-free proxy server" sounds a little more nefarious than sending a GET on someone else's behalf
#npdotythe attacker can in real time access your site, check the link header to get the webmention endpoint, and then use it
#KartikPrabhubut to DDOS the victim the attacker has to do that to as many attacks they're setting up
#npdotyright, but I think it only doubles the number of requests they have to make
#npdotythe real advantage of the attack is that you're getting the requests to come from so many different IP addresses, not that each machine in the botnet is making lots of requests
#KartikPrabhubut they have to setup a botnet that each uses the diff. IPs no?
#npdotyI think in this attack they can use a single IP address. with that IP address, they can contact each of our indieweb servers with webmention endpoints
#npdotyeach of our servers sees only one request from that IP address
#npdotyand then follows the webmention to the victim site
#npdotyslowing down the checking of the webmentions might help, but if the attack is large and sustained enough, then having the traffic spread out may not make a difference
#ben_thatmustbemeyeah, same here. I am up really early now though thanks to my wife having to be up early, so I get to work like an hour early and just work on my site
#cuibonoboif i were to do a search for `webmentions site:indiewebcamp.com/irc` and then under Google's 'Search Tools' adjust the search from 'Any Time' to 'Past year', i get *much* fewer results than expected
#cuibonoboi care about this because this channel tends to be a much higher bandwidth than i can hope to keep up with, but i would still like to somehow keep track of topics that interest me
aaronpk_ joined the channel
#crwhat HTTP header should server add. Last-Modified?
#crdonno why so many servers return Date: Tue, 30 Sep 2014 13:49:47 GMT - always
#cr"now" time instead of date of the doc last-modification
#ben_thatmustbemecweiske, indeed, but there needs to be some semblance of sanity there, you could trail with //////// and its valid, I'm willing to always have a trailing slash if its really a problem
#ben_thatmustbemei'll just normalize to always have a single trailing slash
#ben_thatmustbemeAn absolute URL must be a scheme, followed by ":", followed by either a scheme-relative URL, if scheme is a relative scheme, or scheme data otherwise, optionally followed by "?" and a query.
#ben_thatmustbemeA scheme-relative URL must be "//", optionally followed by userinfo and "@", followed by a host, optionally followed by ":" and a port, optionally followed by an absolute-path-relative URL.
#Loqishaners: kylewm left you a message 9 hours, 37 minutes ago: with your Settings table in Homesteading, how do you switch between localhost and production?
#barnabywalterscr: the representative h-card algorithm removes nameclashes, allowing domain -> profile mapping without the need for extra confusing URL syntax
#barnabywaltersShanehudson: shaners: I’d heard that too, about south america
#shanerskylewm: how do I switch what between localhost and production?
#ShaneHudsonAh could have been Brazil, my memory is awful
#crbarnabywalters: 'extra confusing URL syntax' = using a doc URI without a fragID for the thing it defines.
#ShaneHudsonHas anyone had experience with squarespace? I presume it can't be used for indieweb?
danlyke joined the channel
#ben_thatmustbemehuh, indieauth returns me no result if i use WITH a trailing slash indieauth fails
#ben_thatmustbemei tried to just put it back, i use whatever i'm given, trailing slash or no
#ben_thatmustbemei add http:// if neither http:// nor https:// is put on it
danlyke joined the channel
#ben_thatmustbemewhen i do that i get a code back, but the call to auth_endpoint returns an empty array
#barnabywalterscr: look at the use of URLs in public spaces (e.g. advertising). It’s typically a domain, maybe with a single path segment. Never a fragment identifier
#crwe're talking about identifying users now. not websites
#barnabywalterscr: we’re talking about URLs, and how people relate to them
#barnabywaltersactual, real people, who have no idea what a “fragment identifier” is or why they should care about pseudo-philosophical webarch reasons for it’s existance
#cweiskeben_thatmust, now I get no errors, but am also not logged into your site
#gRegor`!tell ShaneHudson I don't have experience with Squarespace, but my understanding is you have full control of the HTML, so you could use it for indieweb. Webmention would be tricky, of course. Unless we encouraged them to add support for it. :)
#ben_thatmustbemefirst off, if i understand things correctly, rel= isn't microformats markup, the microformats there just says its a url (me being pedantic)
#ben_thatmustbemeXFN 1.1 introduced the "me" rel value which is used to indicate profile equivalence and for identity-consolidation.
#ben_thatmustbemeit says nothing about a person being that thing, just that that link contains and equivalent profile
#gRegor`I was only parsing the mf, not mentioning the rel
#cras soon as one wants to cache, annotate, store i a graph-store, how do you know whether you mean https://waterpigs.co.uk/ the person, the web-document, or the website? by dismissing good URI-design as "complicated" you're inadvertently making things complicated
#crthe rel=me reusing a document/website URI for a person
#crhow do i disambiguate? i'll rather just not consume microformats data until they stop this silly nameclash
#crthe alternative is complicate implementations by using tons of named-graphs and annotating the named-graphs with contexts, so you can reuse the URI fore different things. but that's meh. too complicated..
tilgovi, gavinc and paulcp joined the channel
#ben_thatmustbemecr, rel=me does not me a person is equivalent to a website
#ben_thatmustbemexfn just described it as a link to yourself at a different url
#gRegor`cr: What is the use-case where you need to disambiguate something? I'm not understanding.
snarfed joined the channel
#gRegor`My personal website represents me online. Why wouldn't I link to it with rel=me?
#ben_thatmustbemei think its that he is using the body of the <a> tag as the name for the link
#ben_thatmustbemeso instead of a user Ben and a link labelled "twitter profile" it becomes a link title "Ben" as well
#ben_thatmustbemedavidmead, its a new post, it has to be the h-entry itself with a u-in-reply-to (if i understand what you mean)
#KevinMarks_URIs are just notation conventions used for databases, but URLs locate resources universally, and are thus useful for humans and computers alike
#davidmeadben_thatmustbeme, hmm. that’s what i thought. pity.
#ben_thatmustbemeit makes sense though, honestly, every reply could be replied to. if the only location was in the reply-thread of a post, I would have no way to reply to your comment specifically
#davidmeadben_thatmustbeme As the originating post is sent to Twitter, brid.gy (or similar) pulls back the replying tweet and displays as a reply to that post, I’d like to reply to that reply in the reply thread
mlncn joined the channel
#ben_thatmustbemeyou could reply-to both, that way its processed as a webmention internally to yourself and bridgy would still pick it up as a reply to the other reply
#KevinMarks_I think cr should stop using English, which is semiotically impure, and communicate only with people who speak lojban
#LoqiA reply thread (AKA reply chain) is a threaded list of replies, and replies to those replies, displayed under the original post, sometimes as part of a reply-context http://indiewebcamp.com/context-thread
#gRegor`Hm. That's not what I think of when I say context-thread. :)
#ben_thatmustbemei redirected it to reply-thread, since the usage had reply-thread all over
#davidmeadben_thatmustbeme grego` so maybe i’m still visualizing this “wrong” on my blog and need to think of a reply from Twitter like a new post on my site. my reply to it is a new post...
#gRegor`Ah, I see 'reply-chain' got renamed 'reply-thread'. Sounds good.
#davidmeadthe whole blog is not a post with replies attatched to it, but a series of linked replies to each other
#gRegor`"A reply thread (AKA reply chain) is a threaded list of replies, and replies to those replies, displayed under the original post, sometimes as part of a reply-context."
#ben_thatmustbemedavidmead, WordPress has a lot going for it, but for indieweb things its a lot of patchwork addons
#gRegor`"sometimes as part of a reply-context" doesn't make sense to me there.
#LoqiA context thread (AKA context chain) is a threaded list of posts, and notes those notes replied to, displayed above the reply post, making up the reply-context http://indiewebcamp.com/context-thread
#davidmead"context-thread" should be the whole thing. "reply-thread" is after the post. you need another term for before the post - the thing(s) that prompted it
#davidmeadthe term “reply” doesn’t make sense to me as descripbing something that came before
#ben_thatmustbemecontext-thread i would not put as the whole thing, so we really need any term for the whole thing?
#gRegor`davidmead: It is a bit confusing, until you thiink of it as "someone else's reply"
#ben_thatmustbemeit does, because my post is a reply, i want to my my reply in context, so i see the argument
#KevinMarks_Context doesn't just imply history though
#davidmeadexactly KevinMarks_ to me context is viewing the whole thing
#ben_thatmustbemethe parts of a written or spoken statement that precede or follow a specific word or passage, usually influencing its meaning or effect: I agree with davidmead & KevinMarks_
#KevinMarks_The challenge is deciding which path through the chain of replies is the context
#KevinMarks_We see this on twitter all the time, as each of us gets a different subset of the responses
#gRegor`history-thread and reply-thread make a lot of sense to me; they're pretty self-explanatory
#KevinMarks_There isn't a globally visible thread, that's part of the value of twitter and the open Web alike
#davidmeadso a “context-thread” is made up of “historical-thread” “post” “reply-thread”?
#ben_thatmustbemei've been trying to work that bit out on my site, eventually i want to pull in all replys to my posts, even if they only reply to a reply of mine that has one of my posts in its thread-history
#cweiskeben_thatmustbeme, could you check why I don't get logged in?
#Loqicweiske: ben_thatmustbeme left you a message 3 hours, 3 minutes ago: try logging in again to my site. I have some instrumentation now and have fixed an few small errors. might help
caseorganic, jet___ and adactio joined the channel
#ben_thatmustbemeindieauth.com shows that as the simple implementation, default to indieauth.com
tantek joined the channel
#ben_thatmustbemebut yes, i had that pointed out to me, so i fixed it
krendil, tantek__ and eburcat joined the channel
#ben_thatmustbemebtw, it is actually on my todo list to roll my own auth endpoint, just to break everyone's application who is assuming indieauth.com :)
#tantekben_thatmustbeme++ for making the cutting edge bleed :)
#tantek!tell aaronpk all of tantek_ and tantek___ and tantek_otp are leftover connections from ?beta Join - server might need rebooting to let go of those connections.
#tantek!tell annevk I'm ok with a "License(s):" header section at the top similar to "This version:" that just used the same language. If you want to change the language, make a specific request and I can follow-up with Mozlegal.
#ben_thatmustbemewow, he's pushing FOR RSS in place of Twitter? wrong direction there.
mlncn and loic_m_ joined the channel
#ben_thatmustbeme!tell KevinMarks I have my MP client set to send both syndicate-to= A, B and syndicate-to[]=A&syndicate-to[]=B so it should work for either implementation now.
#tantekis still catching up on logs and various confusions
#cuibonoboben_thatmustbeme: i've tried just now with a bare domain and with https, but still nothing
#tantekI'm confused about the reply-context confusion
#cuibonobotantek: nope. but then again, figuring out why google does anything is always a mystery
#ben_thatmustbemecuibonobo, what URL? your site listed in irc-people doesn't have an indie-auth endpoint
#tantekcuibonobo: FWIW I've been having trouble with google date-range search of my own site - they stopped indexing "everything" :(
#cuibonoboben_thatmustbeme: ah! i've never had to list the endpoint. i assume everybody else just falls back to indieauth.com if none is listed
#cuibonobotantek: ugh. that sucks. have you considered doing search via javascript or something? seems like you can't depend on outsourcing to Google anymore
#tantekyeah, it's quite annoying. I'm even using *their* PuSH hub which means they should have results for me within seconds
#tantekalmost caught up with logs - then just need to review all the *-context and *-thread hubbub
#cuibonoboregarding how Google even gets your page's date to begin with, i thought it would be related to Last-Modified headers but nay! the search bot just does a best guess at scraping the contents of your page. :s
#LoqiA reply context is the display of what a reply post is in reply to, including linking to that original post with in-reply-to markup, showing some amount of that original post like author name, icon, summary / ellipsed content, and datetime published http://indiewebcamp.com/reply-context
#tantekFWIW I dislike "history-thread" because "history" implies more comprehensiveness than what is actually displayed.
#tantekhistory implies *all* replies to the original post that were made *before* the current reply post are shown, which AFAIK no one does
#tantekeveryone that implements showing *previous* reply-contexts (both silos and indieweb) *only* recursively show the thread back to the original post - no other replies
#tantek!tell ben_thatmustbeme I'm not going to edit your changes to reply-thread / history-thread without first discussing with you and seeing if we can figure out what was confusing and debate which terms better reflect what is going. I updated /reply-context dfn/summary a bit - please take a look.
#emmaktantek: as a user, do you think a full reply history would be more useful than reply context?
#KevinMarks__hm, no way to get from ello's json to the post URL
#LoqiKevinMarks__: ben_thatmustbeme left you a message 31 minutes ago: I have my MP client set to send both syndicate-to= A, B and syndicate-to[]=A&syndicate-to[]=B so it should work for either implementation now.
#tantekemmak - in the example of Twitter, it's nice to be able to scroll to the top and see what tweet started the whole thing
#tantekthen if I want to see the whole reply *history*, I click on the permalink of the tweet that started the discussion, which then will display all the threads spawned
#tantekI should say, it will display all the *comment* threads
#gRegor`tantek: To make sure I'm understanding, "history" implies including replies tot he original post from third parties, that aren't in a direct chain with you?
#tantekthe stuff *above* a *reply* post is a reply-context
#KevinMarks__ah, so tantek is using "history" the way we were using "context" earlier
#gRegor`I think some confusion (for me) is your use of "reply-contexts" and "reply-thread". "everyone that implements showing *previous* reply-contexts (both silos and indieweb) *only* recursively show the thread back to the original post - no other replies. hence reply-thread"
#LoqiA reply thread (AKA reply chain) is a threaded list of replies, and replies to those replies, displayed under the original post, as part of the context-thread http://indiewebcamp.com/reply-thread
#gRegor`Calling them "comments" makes sense and I'm getting a better idea the terminology, though. Not sure how I forgot something so simple.
#Loqiannevk: tantek left you a message 1 hour, 16 minutes ago: I'm ok with a "License(s):" header section at the top similar to "This version:" that just used the same language. If you want to change the language, make a specific request and I can follow-up with Mozlegal.
#barnabywalterstantek: actually no I didn’t get that working, mainly because that would require adding the indie-config web component code to shrewdness and it’s not very polished at the mo (if it’s even published)
#barnabywaltersI do need to update the micropub fallback markup though, to <indie-action>
#Loqitantek meant to say: they're not showing replies underneathh, they're showing *comments* underneath
#barnabywaltersokay, shrewdness updated to show <indie-action> elements next to posts if you don’t have micropub enabled
#gRegor`Ok, but it's more than just direct comments, right? I mean, it's Lilly's comment, then Shane's comment to her, then Kartik's comment to Shane, etc.
#tantekbarnabywalters: but to make <indie-action> elements work you need to do all the web components stuff that voxpelli figured out
#barnabywaltersalso at least partially fixed the URL specificity which was causing multiple http+https versions of posts
#gRegor`I don't know if we need a term for that concept or not, but it strikes me as different than typical comments on a blog.
#barnabywalterstantek: well, they’ll work right now with the toolbelt
#tantekis voxpelli still around? because so far he may be the only who got <indie-action> web components *working* on his site
#barnabywaltersI can also potentially add the web component into shrewdness
#tantekbarnabywalters: of course they do :) the point was to get more folks trying what voxpelli got working
#tantekso we can see if a web component solution actually scales across different implementations etc.
#tantekgRegor`: the stuff below a post is just comments. not "different than typical comments on a blog".
#kylewmthe indie-config stuff was pretty non-trivial
#barnabywalters!tell voxpelli did you publish your indie-action webcomponent code anywhere? I’d love to add it to shrewdness for people who don’t have micropub enabled!
#barnabywaltershaven’t even tried implementing the other half yet
rknLA joined the channel
#tantekright, there's the <indie-action> half, and the registering the web+action: handler half
#tantekthe web+action: half others have gotten to work, e.g. aaronpk
#tantekbut the <indie-action> web component / iframe etc. half no one else has gotten working
#cuibonoboi think i get what gRegor` is saying. calling the entire tweet thread "comments" implies that all these tweets are commenting on the tweet at the top, but they're not.
gr0k joined the channel
#adactioThere's actually one other little thing we should be doing on the JavaScript side for <indie-action> and that's registering it as a new element (different to registering an action/handler):
#tantek!tell voxpelli could you provide the URL where you have (had?) <indie-action> markup plus web componenets support e.g. with reply and pay actions?
#gRegor`Perhaps /reply-thread could be renamed /reply-context-thread then, since it clarifies it's multiple reply-contexts, not replies (aka "comments")
#kylewmtantek: it’s there on the post permalink pages
#tantekgRegor`: from this discussion I'm convinced that the term "thread" is already overloaded and is thus the source of confusion
#gRegor`Definitely talk to ben_thatmustbeme about this, though. I think he has a better handle on it since he's actually implemented it.
#tantekin other news - no other comments / follow-ups re: "vouch" webmention protocol extension - does that mean everyone's convinced or just waiting for user-flow and protocol-flow diagrams? ;)
#tantekbret - that would be great. also ok to lazy evaluate and await /vouch to be filled out with more readable prose description that separate statements in IRC
#Loqitantek meant to say: bret - that would be great. also ok to lazy evaluate and await /vouch to be filled out with more readable prose description than separate statements in IRC