#aaronpki'm starting to think I need a few different names
#aaronpkif you search google news for "aaron parecki" it's full of articles about Uber and ride sharing, because I took a bunch of photos of cabs in portland and posted them on flickr with a CC license and people use them in articles all the time
KevinMarks, tbbrown, mlncn, wolftune, KevinMarks_, tantek, snarfed and goodoo joined the channel
#snarfedaaronpk: i don't know exactly what quill sent to the endpoint, but looks like it was a query, and this endpoint responds to both config and syndicate-to queries with {"syndicate-to":[]}
#GWGI just keep stalling on the idea. The only way I can think of to make it work is to use a global variable to have plugins register syndication targets for Micropub, the same way Core registers post types and other things.
#snarfedGWG: i thought we agreed on using the 'micropub_syndicate-to' filter? that's what the plugin has done for a long time now
#snarfedhow about you get it working with even just one posse plugin, see how that goes, then we tackle this if we still think it's necessary?
#GWGI started to look at Bridgy Publish for WordPress, which is just a wrapper around the Bridgy Publish service, but I was stopped by the fact people expect it to just work and it needs proper theme markup.
#GWGNot a problem for me, but it seems like there is something I should do in that plugin to help.
#snarfedmaybe start by just getting it working for you first
#GWGI decided to fix another project that is broken first. My location support plugin.
#GWGI want to see if I can get it working again for IWC LA.
#GWGI did some major UI changes, but didn't quite finish them.
#GWGI also am speaking to pfefferle about finalizing Webmention 3.0.
#GWGsnarfed: Have you considered coming down to LA? You are on my list of people whose hand I would like to shake.
#snarfedGWG: aww likewise! not this time, but maybe someday
#GWGsnarfed: Either way, I tend to jump around a lot on projects. When I get stalled, I tend to put something aside for a while.
#GWGAnd I admit I have trouble focusing on one aspect of a problem because professionally, I'm never given enough time to do one thing. I'm always having to do twenty things simultaneously.
#GWGSo you'll see me either drilling down to the smallest detail trying to plan everything out for when I get to it, or working on something.
#sebilasseMoin moin, 25 tickets for IWC Berlin are gone already but less people put their names in the wiki - they will receive a mail next week, however make sure to enter your name - "Hello - my URL is" https://indieweb.org/2016/Berlin
goodoo joined the channel
#sknebelsebilasse: I think it's normal that quite a few people aren't in the wiki, and to be expected
#sknebeleven if the changes required to get indieauth to work are tiny, its still "busywork" in some sense
#sknebel(I've had somebody ask me "why should I do that just because your wiki doesn't work like any other website" and they have a point, if they don't use anything else indieweb yet ;))
#sebilasseCheck the logs from yesterday - we COULD use an ordinary e.g. "login with twitter" button as an alternative. And that Auth flow could teach and tell the user how not only to be "me on twitter" but me - I'll tell you:
#sebilasse2. After auth, Wiki checks if there is a rel="me" link - if not it urges user to create one [as necessary "step 1"]
#sebilasse3. Wiki checks if that rel="me" has a link back - if not it urges user to create one [as necessary "step 2"],
#sebilasse[redaktor could simply have a confirmation UI to add this link to your profile, see prerequisites]
#sebilasse4. We can now proceed with IndieAuth or selfhosted or whatever...
#sebilasseI am working on it but it is work to make it most modular - basically IndieAuth is the wrapper containing
#sebilassethe supported 4 OAuth1 and 3 OAuth2 flows.
#sebilasseYou could "start" it with either a SILO or your domain and it's optional allowing as well anonymous login via https://commentpara.de (hoster cweiske.de attends BER) or an alternative etc. ...
AndChat|566325 and gko joined the channel
#sknebelhm, not sure if I get the difference, but we can talk about that at the camp. IMHO having people log on to the wiki is nice, but not that important. the wiki is quite public as well...
#[tantek]Or maybe on /like posts as a beware sort of thing? I do think it's a valid design question - do people expect everything they "like" to then have a permalink which is pushed to all their followers / subscribers?
sebilasse joined the channel
#aaronpkI designed my site to have a permalink for each like, but intentionally do not show those on my home page
awolf, sebilasse and CaptainCalliope_ joined the channel
#sknebelsimilar for likes/bookmarks and other interactions IMHO
#sknebele.g. what I bookmark and when is a quite detailed view into what I'm doing and interested in right now -> a full stream of my bookmarks is not something I want to be public
anarchivist and snarfed joined the channel
#aaronpksknebel: interesting. all my bookmarks are public, (not on my home page tho), so i'm guessing we bookmark things for different reasons
#sknebelthinking about it, the timing data is a big issue -> a queryable database of all my bookmarks without data when it was created feels less "dangerous" to me than a stream
#sknebelbecause "I once looked into X" is a lot less specific than the order and thought processes that might show up in a stream
#sknebelso public bookmark posts for me are probably going to be selected reccommendations "this is interesting and you might want to look at it" and "here is a collection of all things I found interesting for X, after the fact"
#sknebeland another data point re likes: reddit hides them by default, but you expose the pages showing everything you upvoted/downvoted
#sknebel(which probably is even more granular and common than liking)
tantek, tbbrown, KartikPrabhu and dkm_ joined the channel