#indiewebcamp 2015-01-02

2015-01-02 UTC
snarfed, j12t, sammachin, clintpatty, Erkan_Yilmaz, eburcat, KartikPrabhu, mdik_, nloadholtes, tantek, npdoty, gRegor`, prtksxna and mdik joined the channel
#
GWG
I need some ideas on categories/tags
prtksxna, tantek and mlncn joined the channel
#
tantek
good evening #indiewebcamp!
#
GWG
Good evening, tantek
#
tantek
what the heck was TVTag?
#
tantek
http://tvtag.com/ - Effective January 1st, tvtag is offline. Thanks for tagging along! If you're interested in requesting a copy of your data, please email your username in the subject line to datarequest@tvtag.com.
#
tantek
first /site-death of 2015?
onewheelskyward and KartikPrabhu joined the channel
#
tantek
hmm - apparently I had TBI for my "all entries for a day of a certain type" code.
#
bear
well it still needs some plumbing work, but I have my micropub endpoint that allows me to create an article
#
bear
i'm counting it as a win for 2015-01-01 challenge :)
#
npdoty
demo paper with hcites automatically generated by citeproc: https://npdoty.name/pandoc-hcite/
#
@npdoty
Satisfying an #indieweb commitment, a demo "paper" showing generation of hCite markup via pandoc and citeproc: https://npdoty.name/pandoc-hcite/
(twitter.com/_/status/550898176195301376)
#
npdoty
yeah, thanks, Loqi
#
tantek
fixed
#
tantek
bear - sounds great! which micropub client were you able to use to post to your site?
#
bear
for right now a form I created
#
tantek
npdoty++ well done!
#
Loqi
npdoty has 8 karma
#
bear
that is what i'm working on now, getting more of the action items setup
nloadholtes joined the channel
#
bear
and I discover erros in my token endpoint...
#
tantek.com
edited /own_your_data (+374) "/* Tantek */ owning my favorites instead of Twitter"
(view diff)
#
@t
2010: notes on my site before Twitter 2013: @-replies 2015: faves before Twitter Join the #indieweb and #ownyourdata. (ttk.me t4Zx1)
(twitter.com/_/status/550924871661002752)
#
@lachlanhardy
RT @t: 2010: notes on my site before Twitter 2013: @-replies 2015: faves before Twitter Join the #indieweb and #ownyourdata. (ttk.me t4Zx1)
(twitter.com/_/status/550925110840799232)
KartikPrabhu joined the channel
#
bear
hmm, indieauth validate code now requires a state param...
#
aaronpk
bear: it does now when used for authorization
#
bear
yea, my helper lib wasn't passing it
#
bear
i'm trying to get my token endpoint to work with quill and saw the error message
#
aaronpk
previously it didn't but that's because it was only used for authentication
#
bear
cool - fixed that, now on to the others...
eburcat, friedcell and prtksxna joined the channel
#
bear
hmm, the quill post doesn't have a title field
KartikPrabhu and j12t joined the channel
#
tantek
!tell snarfed odd Bridgy Publish FB "like" bug - 404 when I try to curl Bridgy to like this post for me: curl -d 'source=http://tantek.com/2015/002/f2&target=http://brid.gy/publish/facebook&bridgy_omit_link=False' https://www.brid.gy/publish/webmention
#
Loqi
Ok, I'll tell them that when I see them next
eschnou joined the channel
#
tantek
!tell snarfed also how hard would it be for Bridgy Publish to hadle all the h-entrys on a page, e.g. http://tantek.com/2015/002/f
#
Loqi
Ok, I'll tell them that when I see them next
caseorganic and colintedford joined the channel
#
colintedford.com
edited /User:Colintedford.com (+381) "Moved "Improve sidebar" to "Done"; added desired footer content to "Wants"."
(view diff)
#
bear
so, quill seem to support "name" (which I gather is what I would call an article title)
#
bear
so quill seems to be for posting notes and not articles
#
bear
because the /new form shows a content field and a slug field
#
tantek
bear - I believe it posts several types of content
#
tantek
most recently aaronpk added posting "like" posts support to it
#
bear
oh - I only saw a link for "New Post" and am using that to test
#
aaronpk
yeah it doesn;t do articles
#
aaronpk
but it does notes, bookmarks and likes
#
bear
yep - I just setup articles as the first thing for my micropub endpoint and i'm having to adjust some things to use quill as a tester
#
bear
like how it uses x-www-form-urlencoded for everything
Sebastien-L joined the channel
#
bear
which is only an issue for my non-web-dev self and how I created my test forms :)
#
colintedford.com
edited /User:Colintedford.com (+379) "Moved "shortlinks" from "Wants" to "Working On" & expanded."
(view diff)
#
KartikPrabhu
Loqi: playback
#
Loqi
is done
#
KartikPrabhu
good for you Loqi
#
tantek
aaronpk: do you have POSSEing of FB likes working?
#
tantek
I only got one to work via Bridgy Publish, then the rest 404d
petermolnar and KartikPrabhu joined the channel
#
bear
ok, *now* I can say that I have a basic micropub endpoint running \o/
#
bear
just used quill to create a note
#
KartikPrabhu
maybe i should fix mine!
#
KartikPrabhu
bear++ for micropub endpoint
#
Loqi
bear has 52 karma
#
KartikPrabhu
bear: I might borrow Ninka for auth stuff
#
bear
it has served me well so far - it's a very small module
#
bear
I pushed a new version tonight to handle the state param that is needed for micropub auth code validation
#
tantek
bear++ awesome!!!
#
Loqi
bear has 53 karma
#
KartikPrabhu
i did catch the update. beats me writing my own auth-code
#
bear
the micropub fields seem fragile to me tho - but it may be that I haven't worked with it
#
KartikPrabhu
fyi I failed in my 2015-01-01 commitment. design reasons
#
bear
you can always make them your new IWC commitment :)
#
KartikPrabhu
bear: I have had the same feeling. what seems fragile?
#
bear
well, h=entry is the only solid part
#
bear
if it's an article or note then you have to look at the parameters to figure it out
#
bear
the field list for a bookmark is almost the same as an article
#
tantek
KartikPrabhu: your friend didn't want to launch their site?
#
KartikPrabhu
tantek: we didn't hacve the homepage design she wanted so... yeah
#
tantek
and not something simpler to start with either?
#
KartikPrabhu
bear: yeah it is a little work to get post types from micropub
#
KartikPrabhu
tantek: we do have most of the content ready but for artist portfolios one needs a dashing homepage
#
KartikPrabhu
mostly in context: here is her "clog" about new year's resolutions: http://tapastic.com/series/Clogs
#
KartikPrabhu
tapastic.com is a a silo for comics. I hope to get her off that an onto posting comics on her own site
#
KartikPrabhu
hopefully tapastic.com has a posting API for POSSE but not likely
#
bear
oof - 5am - /me waves to the good indieweb people!
stream7 and michielbdejong joined the channel
#
bear.im
edited /Micropub (+133) "add bear.im to examples"
(view diff)
#
bear.im
edited /micropub-endpoint (+64) "add bear.im to example list"
(view diff)
adactio and j12t joined the channel
#
colintedford.com
edited /User:Colintedford.com (+25) "Done: Add colophon & copyright info to footer."
(view diff)
#
@IndieHosters
RT @t: 2010: notes on my site before Twitter 2013: @-replies 2015: faves before Twitter Join the #indieweb and #ownyourdata. (ttk.me t4Zx1)
(twitter.com/_/status/550969233333829632)
friedcell, michielbdejong, eschnou and KartikPrabhu joined the channel
#
@ledouarec
RT @t: 2010: notes on my site before Twitter 2013: @-replies 2015: faves before Twitter Join the #indieweb and #ownyourdata. (ttk.me t4Zx1)
(twitter.com/_/status/550983815364349953)
ben_thatmust, eschnou, asdofindia, eburcat, prtksxna and fiatjaf joined the channel
#
@iamronen
@kirilind I'm all for #indieweb but a product for "people" (not "developers") can't use language like "log in from the console as root"
(twitter.com/_/status/551006348197265408)
KartikPrabhu, veselosky, friedcell, j12t and mlncn joined the channel
#
@danfowler
RT @t: 2010: notes on my site before Twitter 2013: @-replies 2015: faves before Twitter Join the #indieweb and #ownyourdata. (ttk.me t4Zx1)
(twitter.com/_/status/551016476501880832)
hober3, saurik, asdofindia, davidmead, mlncn, j12t, wont_on, Acidnerd1, wolftune, insomnike, nloadholtes and nloadholtes_ joined the channel
wolftune, Acidnerd and j12t joined the channel
#
aaronpk
good morning!
#
bear
morning!
#
aaronpk
congrats on getting a micropub endpoint working!
#
bear
so, my biggest hurdle in setting up my micropub endpoint... handling x-www-urlencoded POSTs
#
bear
thanks!
#
aaronpk
how was that a hurdle? that's just normal post requests
#
aaronpk
I thought every server-side environment handled that automatically without any extra work
#
aaronpk
except maybe node.js because they like to make things complicated :P
#
bear
I saw "url encoded" and started trying to parse the requested url
#
bear
but the parameters are not passed in via the url but as the body in urlencoded format
#
bear
sorry - x-www-form-urlencoded
#
aaronpk
huh, how was that not clear that it's just "normal" post requests?
#
bear
oh, sorry - not implying that the docs are *wrong*
#
bear
just that for me, a very much a non-web person, it was the toughest part
#
aaronpk
well they are if you thought you had to do anything fancy
#
bear
once I did a quick 'learn what POST urlencoded body" I was ok
#
bear
I saw "urlencoded" and thought it would be done as example.com?h=entry&content=foo
#
ben_thatmustbeme
good morning
#
bear
morning
#
aaronpk
ah hmm
#
bear
again, to a normal web dev without 20 yrs of Perl CGI in their brain... ;)
crystal_ joined the channel
#
bear
so the only real hiccup now for me is how the parameters are not consistent across all of the different types
#
aaronpk
not consistent?
#
bear
a Note doesn't list slug as a parameter - but anyone storing their items on the filesystem will need it and since name is also not listed, you can't create a slug from the name/title
#
ben_thatmustbeme
got my test setup of cordova working... next the fun begins :)
#
aaronpk
not everyone needs a slug
#
aaronpk
most of my notes don't have a slug for example
#
ben_thatmustbeme
i have slugs optional on everything
#
bear
sure, get that - just suggesting that a small set of them should be listed as being optional for all items
#
bear
slug, name, published for example
#
bear
again, just noting how I had to adjust when using Quill to test
#
aaronpk
hm ok. yeah the wiki page is mostly written as examples right now, not as a spec necessarily
#
bear
yea, I was trying to follow it as a spec :)
#
bear
and except for my webdev mistakes, it worked
#
bear
and the token-endpoint wiki page was awesome
#
aaronpk
also my goal with micropub is similar to microformats, where the spec itself is relatively small and just defines *how* requests are made. the actual vocabulary for creating notes vs photos vs checkins is a layer above that
#
bear
nods
#
aaronpk
like how microformats defines parsing rules, but the semantics of an h-entry vs h-card are up one layer
#
bear
yep, but if Quill is the "reference implementation" and I couldn't post an Article... again, not complaining just making the observation
#
aaronpk
I could add a "new article" interface to Quill, might be a good idea
#
aaronpk
I doubt anyone would use it for realsies, but would be good for testing
#
bear
yea, I will be adding a /post to my python flask utility so it's not a big concern
#
bear
I was noodling over the idea of having a GET to the micropub endpoint with h=??? return the list of fields that are required and optional
#
aaronpk
interesting
#
bear
then a micropub client would be able to discover what the target needs
#
aaronpk
what if it returned an HTML form that was marked up with microformats classes
#
aaronpk
that way you could just fill it out in a browser, or code could parse it into a JSON document if it wanted
#
bear
sure, I hadn't thought about the how just yet, just the idea
#
bear
having it return mf2 markup would make more sense - then I could use it as the html form for submission
#
bear
do the GET with the auth header and h=??? param and you get a functional form back
#
aaronpk
seems reasonable
#
aaronpk
although h=entry doesn't distinguish between an article vs note vs photo
#
bear
yea, that was a grumble by me last night :)
#
bear
I almost want to extend it to be h=entry/post
#
bear
or somesuch
#
bear
h=[entry,post]
#
aaronpk
this is why I want this part to be a layer on top of micropub rather than built in to the spec itself
#
aaronpk
cause it's much more fragile and will change often as new post types are added
#
bear
then we can have different implementations and let the best one bubble to the top
tantek joined the channel
#
bear
tho the entry[post,note,article] change is a big one for me to be honest
snarfed joined the channel
#
tantek
good morning #indiewebcamp!
#
tantek
reads logs
#
aaronpk
good morning tantek!
#
bear
morning!
mlncn joined the channel
#
tantek
re: micropub and slugs - is the slug not just part of the url paramter that is sent for creating a new post? or does the micropub endpoint return the URL?
#
aaronpk
there isn't a URL parameter for creating new posts
#
aaronpk
the micropub endpoint is expected to create the URL and return it in the Location header
#
snarfed
tantek: thanks for the report! i see the problem
#
Loqi
snarfed: tantek left you a message 9 hours, 25 minutes ago: odd Bridgy Publish FB "like" bug - 404 when I try to curl Bridgy to like this post for me: curl -d 'source=http://tantek.com/2015/002/f2&target=http://brid.gy/publish/facebook&bridgy_omit_link=False' https://www.brid.gy/publish/webmention
#
Loqi
snarfed: tantek left you a message 9 hours, 22 minutes ago: also how hard would it be for Bridgy Publish to hadle all the h-entrys on a page, e.g. http://tantek.com/2015/002/f
#
tantek
^^^ :D
#
tantek
aaronpk - I wonder if it makes sense for micropub to allow/do *both* - that is, accept a URL parameter (e.g. for both smarter micropub clients that "know" where the next post will be, and to request a slug), and then return the *actual* URL where the content was posted.
#
tantek
bear, I don't think it makes much sense for explicit entry, post, note, article.
#
aaronpk
accepting a URL for creating a post sounds like REST
#
tantek
aaronpk: nope. REST would be POSTING or PUTTING to the URL that *must* be where the data goes.
#
bear
agree with the URL param being to RESTful
#
tantek
this "url=" param would be more of a suggestion
#
bear
for me explicit in the post type is better - less ambiguity
#
tantek
it's not "RESTful" at all
#
tantek
it's part of the misconceived REST
#
tantek
or misunderstood
#
aaronpk
right now the url parameter is used for updating a post
eburcat joined the channel
#
tantek
bear - except you're reasoning about "less ambiguity" from plumbing prespective, which is the wrong place to start with such discussions
#
tantek
the UI is the right place to start
#
tantek
for example, article vs. note is already fairly clear in both UIs, and existing structured/titled vs. not entry-content
#
bear
not from plumbing at all - I could not figure out using Quill how to post an article - that was a UI issue
#
tantek
so there is no need fo rexplicit
#
tantek
but that's because Quill has/had no article posting feature
#
tantek
that has nothing to do with "less ambiguity"
#
aaronpk
what's the use case for the micropub client wanting to "suggest" a URL?
#
aaronpk
other than slug
#
tantek
bear, and another thing entry == post
#
tantek
aaronpk slug is the use-case yes
#
aaronpk
so are you just suggesting a different name for the parameter?
#
bear
always gets confused with post and note and such
#
tantek
I as suggesting re-using an existing property/param rather than coming up with a new one
eburcat_ joined the channel
#
aaronpk
I guess the issue I have with that is since url is used to refer to a specific post when updating, it seems confusing to use it as a "suggestion" when creating
#
bear
i'm only suggesting making slug optional for all of them (or even name)
#
bear
because the URL would require a lot of knowledge of now the plumbing works
#
bear
edits - not "all of them' but for post, note and article
#
tantek
these are good points
#
aaronpk
okay well it at least sounds like I should make a more spec-like section on /micropub that defines how authentication and parameters are passed, then we can split out the actual fields as a separate section
#
tantek
and a good reason to have a "just slug" param rather than shoehorn a use of "url" for it.
#
bear
aaronpk +1
#
bear
the spec would be where the formating of each param is listed also
#
bear
s/would/could/
#
Loqi
bear meant to say: the spec could be where the formating of each param is listed also
#
aaronpk
formatting?
#
tantek
bear - I still want to encourage you to not worry about explicit typing of posts
#
tantek
I think the better UIs will just let users pick various different things to post
#
bear
formatting == "published uses ISO8601 date/time"
#
aaronpk
I think the facebook and twitter UI do a good job of not-explicit post types
#
tantek
and the endpoint / server will post those as an h-entry accordingly, without any explicit post typing
#
tantek
precisely aaronpk
#
aaronpk
you just start typing into the box, and then you can also attach a photo if you want, etc
Kopfstein joined the channel
#
tantek
right
#
bear
yea, I get that, part of my "resistance" is that right now my plumbing makes that hard ;)
#
aaronpk
you should try the new PEX pipes
#
bear
PEX?
#
Loqi
yea!
#
aaronpk
they're more flexible and they won't crack when the water freezes
#
bear
hahaha
#
aaronpk
(sorry, literally a plumbing joke)
#
bear
no need to apologize - a very appropriate response
#
bear
will have to noodle on mapping post,article,note to his current file storage paradigm
#
bear
I may have to start using note-yyyymmddhhmmss.md
#
tantek
snarfed what did you think of my Bridgy Publish feature request for handling multiple h-entrys on the page?
#
snarfed
tantek: honestly i don't know. i suspect it would add a fair amount of complexity, at least to get the behavior "right" for all cases
#
tantek
it's not "just" a loop over the h-entrys on the page?
#
snarfed
…which i don't have to do, but i'd rather not have a bunch of undefined behavior at edges
#
snarfed
it might be, i just have a feeling it will result in surprises
#
snarfed
i'd need to think about it more
#
snarfed
e.g. if a new user accidentally plugs in a feed permalink, and bridgy happily goes and posts 20 new tweets for them
#
tantek
got it
#
snarfed
i detect when people put in their home page, and other obviously wrong inputs, but still
veselosky joined the channel
#
tantek
yes I was thinking of more scoped use-cases like http://tantek.com/2015/002/f
#
snarfed
feel free to file an issue so we can discuss though!
#
snarfed
definitely, i totally get your use case. it's just uncommon
#
tantek
snarfed, uncommon for now ;)
#
snarfed
i try not to predict the future too much :P
#
tantek
I see clustering of same-kind adjacent posts as natural step forward
#
aaronpk
me too. I try to create the future. Easier to predict that way.
#
tantek
which then implies a page for such clusterings
#
snarfed
definitely! clearly better ui. i just don't know that people would naturally want to *bridgy publish* those clusters instead of individually
#
snarfed
the clustering seems more appropriate to do afterward, purely as presentation
#
aaronpk
oh tantek that reminds me, no I never did get POSSE of likes to facebook working. I gave up on it after several attempts.
wolftune joined the channel
#
tantek
aaronpk - then you're using Bridgy Publish for that?
#
aaronpk
no, I just haven't liked anything on facbeook recently :)
#
aaronpk
actually there was one I think. I manually liked it after I posted the like on my site
#
tantek
aaronpk: my running group posts public photos on FB often and thus I'm trying to like those from my site instead of FB web UI
#
snarfed
manual posse ftw…until it hurts
eschnou joined the channel
#
snarfed
aaronpk: do you still think it's just the publish_actions part you need?
#
snarfed
if so, i'm happy to let you piggyback on bridgy's app id
#
aaronpk
snarfed: I was able to use publish_actions on my own account without approval
#
aaronpk
it was more issues around making sure the access token was usable and handling when it expires and such
#
aaronpk
and I was trying using the JS SDK cause that's what they want, and that made things strangely hard
#
aaronpk
I just got really frustrated and gave up. I might try to re-visit it later with the API approach instead of JS
#
snarfed
ahh js sdk
#
aaronpk
yeah the JS SDK is nice cause it'll handle the login prompt and refreshing the token pretty much seamlessly
#
tantek
snarfed: captured multi h-entrys bridgy publish feature request with use-case: https://github.com/snarfed/bridgy/issues/332
#
snarfed
tantek: saw it. thanks!
#
bear
hmm, is it best-practice for my micropub endpoint to return 400 for any request where the me param is not my domain?
#
snarfed
tantek: this could also be more motivation to implement sending wms automatically from tantek.com :P
#
tantek
snarfed - oh I know, I have it in my queue :)
#
aaronpk
bear: yes unless you want to allow other users to create or edit your posts
#
bear
yea, that was my thought also - ok for v1 i'll restrict it
#
aaronpk
other people fixing typos for example
#
aaronpk
but yeah probably you want to limit it to just you
#
bear
yea, i need to revisit that along with tightening up my vouch decision tree
#
bear
I need a whole new set of code for "ok, so this other domain wants to do X, do I allow it"
#
aaronpk
would also be useful for a multi-author site
#
bear
does returning 401 unauthorized make more sense for that
#
bear
instead of a generic 400
#
aaronpk
good point
#
tantek
I like the "let friends fix typos" use case
#
aaronpk
or letting friends add tags
#
aaronpk
or tagging people
#
tantek
nah - for that we already have tag replies
#
aaronpk
like instagram?
#
tantek
those friends should be posting their own tag reply posts in-reply-to your post
#
tantek
instagram does not allow others to add tags or tag people in your photos
#
aaronpk
flickr allows friends to add tags directly, right?
#
tantek
however it tracks (and shows on hover) *who* added what tags
#
tantek
thus acting more like tag replies with explicit attribution
#
aaronpk
okay well editing typos is at least a solid use case
mlncn joined the channel
#
tantek
editing typos seems minor enough to not necessarily want to do it as posting an "edit" reply post
#
tantek
though maybe not - people post pull requests to edit typos - that's kind of the same kind of silo thing (and takes many more steps)
#
aaronpk
typically pull requests for editing typos happens when the people don't know each other
#
aaronpk
it's more of a suggestion, "here I made you a thing, you can choose to accept it if you want"
#
aaronpk
I would be okay with letting friends edit my posts directly, but not just anyone who signed in via indieauth. I would want those to come in as "edit posts" where I could review and approve the edit
#
aaronpk
so I think both ways are useful
pauloppenheim, colintedford and KartikPrabhu joined the channel
#
tantek
makes sense
#
snarfed
oh man, fun. first unicode domain site i've come across organically, i think: http://с.новым.годом.рф/
tantek joined the channel
#
bear
why is quill doing a GET to my micropub endpoint just after it verifies the auth token?
tgbrun joined the channel
#
ben_thatmustbeme
bear, is that the thing of it looking up what places you can syndicate to?
#
aaronpk
it puts little syndication checkboxes in the form if it finds them
#
ben_thatmustbeme
i need to implement that
#
aaronpk
me too
#
aaronpk
mine don't actually do anything yet
#
aaronpk
I will be curious to hear your feedback on it once you implement it. I was originally planning on implementing it where my site is the thing that does the syndication
#
aaronpk
but now I'm reconsidering, and thinking about making the syndication happen in Quill, and it would go update the post with the syndication link after it's created
#
bear
oh - I see
#
bear
adds that to the growing todo list ;)
#
aaronpk
the main reason is because it means I can handle all the sign-in logic once in Quill, and also provide an interface for doing things like providing the shorter version of the text for twitter
#
ben_thatmustbeme
hmm, that would be interesting i suppose, but I like that I can handle syndication on my site without having to worry about the client doing anything
#
bear
I was just testing some of the cleanup refactoring I just did to my code and wondered why quill was triggering an exception
#
aaronpk
ben_thatmustbeme: yes it's a tradeoff for sure
#
ben_thatmustbeme
also, while i might give a client access to do MP posting on my site, i'm not going to give access to all of my various silos
#
aaronpk
it depends on how much you trust the client
tgbrun joined the channel
#
aaronpk
so I'm glad there are two ways of doing it
#
ben_thatmustbeme
hmm, i realized that for MP access via an app, i don't need to do anything extra other than the usual indieauth methods to log in, just have the redirect as some special handler myapp://
#
aaronpk
that's what my ios app does
#
ben_thatmustbeme
i'm going to work on one in cordova
#
ben_thatmustbeme
hopefully work across all
gavinc, KartikPrabhu and wolftune joined the channel
#
bear
does someone have a couple minutes to try and use quill to publish to https://bear.im ?
#
bear
I want to test that I have the security tight
#
aaronpk
hah sure
#
bear
thanks
#
aaronpk
hm how do I do that?
#
bear
you should be able to signout of quill on the web and then try to ... oh... yea, you query the domain for micropub *after* you signin
#
Loqi
it is probable
#
aaronpk
i have an idea
#
bear
you could take the auth code from your session and try to use that against mine
#
aaronpk
okay I got a token from your token endpoint for bear.pin13.net
#
bear
yea, I saw
#
aaronpk
I got a 403 forbidden response
#
bear
and you just got a 403 for post
#
bear
cool - that was what I wanted - thanks!
#
aaronpk
cool. not 401 unauthorized?
#
bear
yea, I went both ways on that
#
bear
once I do allow friends to post I'll make it 401
#
aaronpk
oh here's another thought...
#
aaronpk
hm I can't quite piece it together
#
bear
i'll make it 401 just to be cleaner
#
emmak
aaronpk: i got syndication-discovery working with quill
#
aaronpk
emmak++
#
Loqi
emmak has 9 karma
#
bear
emmak++
#
Loqi
emmak has 10 karma
#
emmak
i am syndicating to twitter and facebook through bridgy from my micropub endpoint, and it seems to work
#
aaronpk
oh nice! so your micropub endpoint gets the syndicate-to checkbox value and then tells bridgy to publish?
kerosene joined the channel
#
emmak
i had to add comma-separated-list style as a fallback to array style, to get it working with quill
#
aaronpk
oh yeah I haven't updated quill yet
#
emmak
one thing i was wondering about was whether "[]" should be part of the spec, since php doesn't seem to support array parameters without that
#
aaronpk
yeah, the [] syntax will need to be part of the micropub spec since it isn't part of form-encoding
#
emmak
or whether its bad to force something based on the quirks of a particular language
#
aaronpk
enough other languages have adopted that that it's reasonable to use it
#
bear
800 lb gorilla style "adopt" ;)
mlncn and npdoty joined the channel
#
kylewm
it's also kind of the least common denominator; other languages tolerate the [], but php needs them
pauloppenheim1 and tantek joined the channel
#
bret
cool aaronpk, thanks for making those updates
#
aaronpk
bret: lol that's just docs so far. wil have to do the actual updates later
#
tantek.com
created /creation (+20) "r"
(view diff)
#
tantek.com
edited /2015-01-01-commitments (+185) "completed mine, citations"
(view diff)
myfreeweb joined the channel
#
bret
missed the deadline :/ but I made more progress on modularizing gitpub
#
@davidbgk
@oncletom @davidbruant probablement via webmention comme sur le blog (pas encore implémenté)
(twitter.com/_/status/551133427328884736)
#
@oncletom
@davidbgk et c'est moi où y'a personne qui parle de Webmention ? Cc @DavidBruant
(twitter.com/_/status/551133689636483072)
#
tantek
bret - is it still something you're interested in doing or is it not so much an itch any more?
#
ben_thatmustbeme
oh wow, indie-auth access may be even easier than that, this should actually be a breeze to make a micropub client app
wont_on joined the channel
#
bret
tantek: totally. but in starting, I began refactoring a bunch, mainly out of necessity
#
tantek
bret - I can totally relate. In the process of implementing "like" posts I greatly simplified the Falcon storage format.
#
tantek
Eliminated a bunch of DRY violations even.
#
tantek
simplified the markup produced on my home page too
#
bret
in order to get micrpub working in the first place, I just hacked and slashed my way to the finish line. made a total mess
#
bret
its fun though, every time I do something I learn a lot, which is primarily the valuable thing for me right now
#
bret
I'm making progress, just slowly.
KevinMarks_ joined the channel
eschnou and npdoty joined the channel
#
tantek
What is Movable Type?
#
Loqi
Movable Type is commercial blogging software written in Perl and original released in 2001 https://indiewebcamp.com/Movable_Type
Kopfstein joined the channel
#
KevinMarks_
Does PHP fail if you give it repeated parameters?
#
KevinMarks_
In other words, standard checkbox form elements?
#
tantek.com
edited /Movable_Type (+370) "subheads, note Examples, no indieweb community examples, see also wordpress"
(view diff)
#
KevinMarks_
(on the [] point)
KartikPrabhu joined the channel
#
aaronpk
php only sees one value if you have multiple with the same name
#
aaronpk
you have to name them foo[] if you want it to show up as an array
#
tantek.com
edited /Movable_Type (+331) "FAQ, outreach"
(view diff)
benwerd and KartikPrabhu joined the channel
#
tantek.com
edited /2015-01-01-commitments (+230) "aaronpk done"
(view diff)
npdoty joined the channel
#
tantek
!tell snarfed do you have a list/stream/feed of your indie checkins? And have you found that your new checkin flow is resulting in more frequent checkins than before?
#
Loqi
Ok, I'll tell them that when I see them next
#
tantek.com
edited /2015-01-01-commitments (+149) "snarfed done"
(view diff)
KartikPrabhu and lupinedev joined the channel
#
tantek
npdoty: how is your 2015-01-01 h-cite generation goal going?
#
@npdoty
Satisfying an #indieweb commitment, a demo "paper" showing generation of hCite markup via pandoc and citeproc: https://npdoty.name/pandoc-hcite/
(twitter.com/_/status/550898176195301376)
#
tantek
Twitter announcement? When you have http://known.npdoty.name/ ?!?
#
npdoty
I guess in my head, tweets like that are just pointers. the content itself is on my own site. it’s manual syndication, as it were
#
tantek
why not post such "pointers" notes using Known on your own site and POSSE them to Twitter instead?
#
tantek
why put *any* primary content on Twitter ever?
KartikPrabhu and indie-visitor joined the channel
#
Loqi
Welcome, indie-visitor! Set your nickname by typing /nick yourname
indie-visitor joined the channel
#
npdoty
tantek, you’re saying, why don’t I own the syndications that will then be syndicated?
pauloppenheim joined the channel
#
npdoty
I like the turtles-all-the-way-down nature of that, but I tend to prioritize
#
tantek
that doesn't make any sense
#
tantek
a "pointer" post is not a syndication, any more than a /bookmark post is
#
tantek
or a /repost for that matter
#
tantek
views source on the h-cite demo
#
tantek
npdoty: do you have access to give/middle/family names in your system as separate pieces or are they all opaque "name" strings? e.g. in <span class="p-author">Doty, Nick</span>, and <span class="p-author">Deirdre K. Mulligan</span>
#
npdoty
hmmm… interesting
#
npdoty
I believe the CSL (Citation Style Language) spec does describe different parts of names
#
npdoty
so I could try to pass those through
#
tantek
in that case … /me goes to add some h-card
#
tantek
<span class="p-author h-card"><span class="p-family-name">Doty</span>, <span class="p-given-name">Nick</span></span>, and <span class="p-author h-card"><span class="p-given-name">Deirdre</span> <abbr class="p-additional-name">K.</abbr> <span class="p-family-name">Mulligan</span></span>
#
tantek
slight adjustment to make an explicit p-name for your entry that uses more canonical given/family ordering: <span class="p-author h-card"><abbr class="p-name" title="Nick Doty"><span class="p-family-name">Doty</span>, <span class="p-given-name">Nick</span></span>,</abbr> and <span class="p-author h-card"><span class="p-given-name">Deirdre</span> <abbr class="p-additional-name">K.</abbr> <span class="p-family-name">Mulligan</span></span>
#
npdoty
I’m not sure I’ve seen use of <abbr> for non-abbreviations like that before
#
npdoty
I’ll add an issue to my github repo about identifying different name parts
#
tantek
npdoty it's more typical when there's an initial in use e.g. Doty, N. or even Doty, N. P. ;)
#
npdoty
right
#
tantek
however it works even with the given name expanded to have the desired effect
#
npdoty
it would actually be really useful if citation processors did that when they used a style that used aggressive abbreviation
#
npdoty
law journals and the like will often abbreviate the names of journals or other items
#
tantek
typical consumers of "p-author" expect canonical (not citation style) name ordering as "name" - hence explicit markup helps that.
#
npdoty
are there consumers of “p-author” I can test with?
#
tantek
npdoty indeed - any citation style that does any abbreviation should use <abbr> with the full canonical expansion in its 'title' attribute
#
tantek
npdoty pretty much every webmention receiving site
#
tantek
gets the p-author of the h-entry and displays it as the commenter
#
npdoty
right, I was going to try sending webmentions once the citations were in place
#
npdoty
although there won’t be an h-entry in that case, I suppose
#
tantek
you could markup the paper as a whole as an h-entry
#
tantek
<body class="h-entry">
#
tantek
<h1 class="title p-name">Rendering HTML papers with hCite citations</h1>
#
tantek
<h2 class="author p-author">Nick Doty</h2>
snarfed joined the channel
#
tantek
or if you want to get fancy with the affiliation
#
npdoty
yeah, I have some separate questions (included in future work section) about marking up the metadata for the author of the paper itself
#
tantek
<div class="p-author h-card">
#
tantek
<h2 class="author p-name">Nick Doty</h2>
#
tantek
<p class="affiliation p-org">UC Berkeley, School of Information</p>
#
tantek
</div>
#
tantek
<h3 class="date"><time class="dt-published" datetime="2015-01-01">January 1, 2015</time></h3>
prtksxna joined the channel
#
npdoty
the people who would parse the p-author on the citation itself would more likely be crawlers who want to identify citations between papers, or reference management extensions who want to slurp up the citations from the current paper
#
tantek
and then one giant <div class="e-content"> around all the <sections>
#
tantek
by marking up the paper itself with h-entry, that provides properties that *others* can automatically use to cite *that paper*
#
tantek
h-entry and h-cite work together in this way
#
npdoty
yeah, totally. I want markup both to cite others and so that others can easily cite me
snarfed joined the channel
#
npdoty
I’ll try to write something up about abbreviations, which I think would be an even higher priority for me
#
tantek
when you markup your paper with h-entry then all anyone has to do is parse your paper with microformats, get the top level h-entry, and use its properties to automatically construct a citation
#
tantek
hopefully the markup examples I gave above (copy/pasting from your existing markup in the paper) will be sufficient!
#
snarfed
tantek: commitment report card time, eh? :P
#
snarfed
no checkin feed - they go to my front page, unlike the responses on https://snarfed.org/responses - but i am checking in a bit more often now
#
Loqi
snarfed: tantek left you a message 56 minutes ago: do you have a list/stream/feed of your indie checkins? And have you found that your new checkin flow is resulting in more frequent checkins than before?
#
tantek
snarfed ok. also aside, noticed a bit of spam on your /about page when I was looking for your chekins.
#
tantek
s/chekins/checkins
#
Loqi
tantek meant to say: snarfed ok. also aside, noticed a bit of spam on your /about page when I was looking for your checkins.
#
snarfed
tantek: heh, i think we've discussed that before. i keep a couple intentionally that are especially amusing
#
tantek
oh ok! I should have checked your FAQ ;)
#
tantek.com
edited /2015-01-01-commitments (+213) "/* Commitments */ npdoty done, another example snarfed checkin"
(view diff)
#
tantek
wow! Ari did a great job!
#
snarfed
whoa seriously, that's a ton of work