Aaron Parecki

@caseorganic Here is a sample reply!

@glennjones the group has been dwindling after each stop, a few of us are now at the myhotel bar! #indiewebcampuk

@sebastien.lt Testing webmentions! Crossing my fingers.

@adactio Crossing my fingers that this post makes it! #indiewebcampuk #webmention

@BarnabyWalters Thanks for managing the iPad hangout streaming!

@al3x Aw, missed you last night! We are in Brighton otherwise totally would have been there. How long are you in town? We're back Monday eve.

@paulmison lol! I forgot I was wearing it over there actually.

It seems that Idno is designed to use different data stores using this class: https://github.com/idno/idno/blob/master/Idno/Core/DataConcierge.php, is that correct? If so, it should be possible to swap that out with a wrapper that stores things in Postgres. Do you see any issues with that? I would be more comfortable running this under Postgres or MySQL to avoid introducing a new piece of technology on my stack.

Would be great to see idno support hosting a user profile at a TLD. For example if erinjorichey.com was a CNAME to erinjo.idno.co, then Idno could serve her profile from her TLD. This would be great to support hosting multiple Idno profiles (for hosting sites for communities or small businesses on a single install)

@BarnabyWalters This is a great idea! I took a slightly different approach with @pkbot

@steveivy @shineslike Glad to hear I'm not the only one!

@aral I see what you're getting at, but there are a few problems with your arguments. I wrote a bit here: http://aaronparecki.com/articles/2013/08/31/1/on-trickle-down-technology

@scw I haven't found a good system yet. So for now my budgeting involves depositing my paycheck into 3 accounts, one for rent/basic living stuff, one for fluff money, and one is my savings acct. I spend from multiple cards regularly.

@kevinmarks haha yeah, it is always surprised by my paycheck. Then again, so am I! I guess I'm ok with a few extra alerts in that case though, better to know the system is working than to miss a real alert later.

@fdevillamil Thanks for the notes!

Re 1: adding rel=me is a manual step right now if you're editing your own HTML. However as @barnabywalters pointed out, this is really "exposing important problems further up in the chain" (http://waterpigs.co.uk/articles/indiewebcamp-signin-ux/) It's also entirely possible that an identity hosting provider like about.me would add the markup automatically.

Re 2: This is not quite accurate anymore, given my recent work on distributed IndieAuth (see http://indiewebcamp.com/distributed-indieauth and http://spec.indieauth.com/ for more background). It is now possible for each person to delegate to an IndieAuth server of their choosing, rather than the relying site choosing which IndieAuth server to use. This makes it more resilient to failures.

Re 3: The cultural issue of associating your online identity with a URL rather than an email address has been the subject of much debate for a long time. I would also be open to suggestions on how to handle changing domain names, and whether that should happen at the IndieAuth layer or at the site you're logging in to. Feel free to add things to the wiki! http://indiewebcamp.com/indieauth

#indieauth

@oscargodson fair, and I want to write a thorough response on how @medium could become more indieweb friendly: http://indiewebcamp.com/friendly

@oscargodson Also see: https://medium.com/indieweb-thoughts/9d0e36524dbf

@aral Seriously! I would love if they did this! Incidentally, app.net did a great job of this.

@rejennarate I never do that lol

@jschweinsberg Wilkommen an die IndieWeb!