KartikPrabhuJonathanNeal: any chance of adding new syntax support to fragmention see Example here: http://indiewebcamp.com/fragmention ? Also found that my minification was causing trouble with the fragmention code for some reason
KartikPrabhuanother fragmention question. Right now marginalia.js reproduces a bunch of code from fragmention.js to find the element corresponding to a fragmentioned response. Would it be a good idea to somehow attach the methods to decode the fragmention and to find the element to the DOM or something?
KartikPrabhuKevinMarks_ yes, but I am talking about somehow exposing the functions that fragmention.js uses for other scripts like marginalia.js to re-use
KartikPrabhuyes in some sense. I feel that the fragmention.js code is more "robust" and I'd like to directly use it. For instance I have somehow hard-coded the ## syntax into marginalia.js which I'd like to get rid off
wolftune, benwerd, lukebrooker, KartikPrabhu, lukebroo_, parzzix, tilgovi, tantek, torrorist, LCyrin, yakker, nloadholtes and snarfed joined the channel
kylewmsnarfed: are you around? i'm looking at the twitter publish api issue ... i was able to post a tweet using the remote api console -- is that surprising?
LoqiA comment is a kind of post that is in reply to some other post, that makes little or no sense without reading or at least knowing the context of the source post https://indiewebcamp.com/comments
barnabywalters, fkooman, friedcell and pfefferle joined the channel
GWGThough, after the MF2 parsing thing, it occurs to me that a library to generate link previews from MF2 might be something useful to work on in future
jonnybarnespresumably anyone in the “indieweb” group can access any repo owned by that group, I don’t think github has more granular controls than that
tommorrispre-commit.com already lets you check .json and .xml files in your repo to see that they are syntactically valid. would be lovely to have the blobs inside Markdown files checked too.
barnabywalterstommorris: I know of one project where outputs in the readme are generated by running the code samples, ensuring that both will always be correct
tommorrisI know that's something that the Pragmatic Bookshelf folk do - their books are basically a giant script that starts with XML files and emits PDF files, and the code in them is compiled and run as part of the build process for the book
aaronpki guess i don't see an obvious value for username+password for registered apps, whereas a bearer token "api key" style thing seems straightforward
LoqiA scrobble (AKA a listen) is a passive type of post used to publish a song (music or audio track) that you have listened to https://indiewebcamp.com/listen
fkoomanaaronpk, it is just that for regular oauth 2.0 operations you'd have userid/password anyway, so you could reuse the registration table of clients for introspection as well...but well, it doesn't really matter :)
voxpelliaaronpk: probably used the terms wrong, but in OAuth 1 you could use the same mechanism for communicating between client and server no matter if you had a user token or not
voxpellibut that wouldn't really be possible to do with OAuth 2 + Bearer tokens, as the client-credentials are now used completely separately from the tokens, rather than used together as in OAuth 1
aaronpkif you want a way for applications to obtain an access token for a *user* without asking the user, that is not part of OAuth 2 core, but can be done with an extension grant type
tommorrisso, PESOS from Mixcloud: http://api.mixcloud.com/tom-morris5/feed/ - my 'feed' on the site. wouldn't be hard to pull that in automatically, so when I 'repost' (i.e. 'retweet') a show on there, it'd post it on my own site.
voxpelliaaronpk: 2-legged was a way to communicate between a client and the server when there were no users, there's really no such thing with bearer tokens, no question really, just an observation
voxpelliaaronpk: yes yes, but client_credentials aren't bearer tokens – they are something you use with basic auth (right?) – so while it is possible to still do client-to-server communication without a user, it requires a separate mechanism
voxpellican be annoying from a client perspective even if it makes sense from the server perspective :) and therefore basic auth looks pretty attractive for clients
adactioFriends—I was thinking of maybe throwing in an Indie Web Camp the weekend after Responsive Day Out. Responsive Day Out is on Friday, June 19th so that would mean Indie Web Camp on June 20th and 21st here at 68 Middle Street in Brighton.
barnabywaltersrhiaro: Saw you had some problems with php-mf2 in the logs — sorry to hear about it, did you get it working in the end? I just revised the installation and usage documentation and would appreciate your feedback as a new user!
adactiotantek: yeah, I thought about that. We'd miss out on piggy-backing on Responsive Day Out, but then again, maybe there wouldn't me much crossover in interest.
voxpelliadactio: having the annual Brighton meetup at June 20th and 21st? Not sure I can make it, will move to a new apartment around then and a bit like that – planned to go to the Brighton one this year otherwise though
tantek.comedited /2015 (+168) "/* Candidate Cities */ add Brighton with adactio, voxpelli; add barnaby to Berlin - all per IRC, sort "o" organizer votes to top of each city" (view diff)
adactiovoxpelli: I'm not sure if there will be an Indie Web Camp in Brighton this September. This year that's the weekend that Clearleft will be celebrating its 10th birthday so there may not be time for an Indie Web Camp.
KevinMarks_what I was thinking was to have a replacement for the app engine users api that supports indieweb login and adds helpful things like name and phot
snarfedby replacement, do you just mean a python lib that works on app engine? or specifically a lib with a compatible API so you can port existing code with minimal/no change?
aaronpkanother way to handle the problem of URLs not mapping cleanily to filesystem names for /IndieArchive could be to store the files on disk with a name that is a hash of the URL
aaronpkmight be a good idea to keep an accompanying .meta file for each, which could store the original URL as well as things like the HTTP headers from the request
aaronpkwhat would be great is if any of these projects gave an example of 1) creating a warc file for a specific URL, and then 2) outputting the HTML and headers from that warc file for a given URL