#tantekhttp://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.
#@t2010: notes on my site before Twitter 2013: @-replies 2015: faves before Twitter Join the #indieweb and #ownyourdata. (ttk.me t4Zx1) (twitter.com/_/status/550924871661002752)
#beara 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_thatmustbemegot my test setup of cordova working... next the fun begins :)
#aaronpkalso 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
#tantekre: 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?
#aaronpkthere isn't a URL parameter for creating new posts
#aaronpkthe micropub endpoint is expected to create the URL and return it in the Location header
#snarfedtantek: thanks for the report! i see the problem
#Loqisnarfed: 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
#tantekaaronpk - 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.
#tantekbear, I don't think it makes much sense for explicit entry, post, note, article.
#aaronpkaccepting a URL for creating a post sounds like REST
#tantekaaronpk: nope. REST would be POSTING or PUTTING to the URL that *must* be where the data goes.
#aaronpkso are you just suggesting a different name for the parameter?
#bearalways gets confused with post and note and such
#tantekI as suggesting re-using an existing property/param rather than coming up with a new one
eburcat_ joined the channel
#aaronpkI 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
#beari'm only suggesting making slug optional for all of them (or even name)
#bearbecause the URL would require a lot of knowledge of now the plumbing works
#bearedits - not "all of them' but for post, note and article
#aaronpkokay 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
#tantekand a good reason to have a "just slug" param rather than shoehorn a use of "url" for it.
#tantekthose friends should be posting their own tag reply posts in-reply-to your post
#tantekinstagram does not allow others to add tags or tag people in your photos
#aaronpkflickr allows friends to add tags directly, right?
#tantekhowever it tracks (and shows on hover) *who* added what tags
#tantekthus acting more like tag replies with explicit attribution
#aaronpkokay well editing typos is at least a solid use case
mlncn joined the channel
#tantekediting typos seems minor enough to not necessarily want to do it as posting an "edit" reply post
#tantekthough maybe not - people post pull requests to edit typos - that's kind of the same kind of silo thing (and takes many more steps)
#aaronpktypically pull requests for editing typos happens when the people don't know each other
#aaronpkit's more of a suggestion, "here I made you a thing, you can choose to accept it if you want"
#aaronpkI 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
#aaronpkI 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
#aaronpkbut 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
#aaronpkthe 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_thatmustbemehmm, 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
#bearI was just testing some of the cleanup refactoring I just did to my code and wondered why quill was triggering an exception
#aaronpkben_thatmustbeme: yes it's a tradeoff for sure
#ben_thatmustbemealso, 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
#aaronpkit depends on how much you trust the client
#aaronpkso I'm glad there are two ways of doing it
#ben_thatmustbemehmm, 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://
#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?
#tanteknpdoty: 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>
#tantekslight 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>
#npdotyI’m not sure I’ve seen use of <abbr> for non-abbreviations like that before
#npdotyI’ll add an issue to my github repo about identifying different name parts
#tanteknpdoty it's more typical when there's an initial in use e.g. Doty, N. or even Doty, N. P. ;)
#npdotythe 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
#tantekand then one giant <div class="e-content"> around all the <sections>
#tantekby marking up the paper itself with h-entry, that provides properties that *others* can automatically use to cite *that paper*
#tantekh-entry and h-cite work together in this way
#npdotyyeah, totally. I want markup both to cite others and so that others can easily cite me
#npdotyI’ll try to write something up about abbreviations, which I think would be an even higher priority for me
#tantekwhen 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
#tantekhopefully the markup examples I gave above (copy/pasting from your existing markup in the paper) will be sufficient!
#snarfedtantek: commitment report card time, eh? :P
#snarfedno 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
#Loqisnarfed: 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?
#tanteksnarfed ok. also aside, noticed a bit of spam on your /about page when I was looking for your chekins.