Aaron Parecki

@cubicgarden yes! here it is! https://aaronparecki.com/2017/06/27/6/quantified-self-data-access

@rayterrill Dedicated hardware: https://aaronparecki.com/2016/10/08/15/multi-camera-portable-live-video That hardware also won't randomly try to install Adobe updates during an event.

Thankfully @martijnvdven was watching remotely and took very thorough notes in text! https://indieweb.org/2017/Demos

@wardcunningham Coming down!

Interesting, complaining that their comments are being taken out of Facebook? I assume they were public posts and public comments tho.

@quicklywilliam Shoot really? Is there somewhere I can read about the changes? I want all the details!

@manton2 You're welcome to join remotely as well! We'll have video and a remote link for each room: https://indieweb.org/2017#Remote_Participation

@macgenie Awesome! I've added that to the schedule for Saturday evening activities! https://indieweb.org/2017/Schedule#Saturday

I am super interested in topic-specific hubs. That's the main goal of a new project I have brewing! My first attempt at this is https://news.indieweb.org but I want to make it easier to submit things as well as easier to create new hubs!

@cubicgarden For sure! If I don't see you during the break, find me at the @bmndr table during lunch!

@closetgeekshow mocking? that doesn't sound like the indieweb people I know. plz DM me more info, I'd like to make sure this is addressed

@closetgeekshow at the very least, it allows you to own your data while still talking with people on twitter, like this! check my last link!

@closetgeekshow you *can* have the best of both worlds, it's called POSSE! https://indieweb.org/POSSE

Awesome!

If your webmention sender looks at the rendered HTML to find links, then you won't have to add anything special for this syntax! That's how I handle it on my site, since some of my posts are plaintext source and I don't want to match @-names and URLs in totally separate code paths.

Hah, me too! I get in Friday morning and will be there through Wednesday!

@tomas_quinones I don't think those pick up the 88-108 broadcast range, do they? Anyway I want something consumery for this.

I've heard that. I don't think I can get a phone with a radio cheaper than I can get a plain radio tho.

I've seen this done a few ways:

• The Device Flow: https://tools.ietf.org/html/draft-ietf-oauth-device-flow which is what you see on browserless devices like the Apple TV logging in to a cable provider from your phone. A short code is generated and displayed on the screen, you launch a browser on your phone and enter the code. This would work just as well from the command line on the same device.
• I've also seen apps use the authorization flow, by displaying the authorization URL on the command line prompt and instructing the user to open it in a browser. The redirect URI is a hosted web page that displays the authorization code and instructs the user to paste it back at the terminal.
• The command line app can launch an HTTP server on localhost and use that as the redirect URL for the authorization code flow. This option ends up being the most seamless since it works like a traditional flow without any special instructions to the user.

I am a member of the W3C Social Web Working Group (https://www.w3.org/wiki/Socialwg), and have been organizing IndieWebCamp (https://indieweb.org/) conferences in this space for the last 7 years. We've been making a lot of progress:

• https://www.w3.org/TR/webmention/ - cross-site commenting
• https://www.w3.org/TR/micropub/ - API for apps to create posts on various servers
• https://www.w3.org/TR/websub/ - realtime subscriptions to feeds
• More: https://indieweb.org/specs

We focus on making sure there are a plurality of implementations and approaches rather than trying to build a single software solution to solve everything.

Try commenting on my copy of this post on my website by sending me a webmention!