IndieWebCamp SF IndieComms

Tantek Çelik:

I wrote this post because I was frustrated with which app to talk to whom

also, every time I open an app the queued messages show up and distract me from what i was trying to do

what if instead you choose the person first, then have links to all the ways people can talk to you?

Kevin Marks:

you can do bits of this with iMessage or android, but they choose the contact model for you

Tantek Çelik:

I might want to be contacted by random people on AIM, but if you indieauth in, it will show you more options

Ryan Barrett:

the way we do ACLs now is someone else logs in with indieauth, which is a huge ask

Kevin Marks:

if you want a shim, you can detect facebook and twitter with client-side iframes if they aren't logged in

Tantek Çelik:

I keep the to-do list for my site code Falcon on http://indiewebcamp.com/falcon so it's public domain

I have contact, create&meet and elsewhere. I'd like to add "pay me" too

If you go via my site I can vary what contact method to show when

wavis:

I think this is the problem - knowing how to contact people when

Ryan Barrett:

the high cognitive load is that everyone's "contact me" UX will be different, whicg creates cognitive load too

I want to have the visual muscle memory to do the same

Aaron Parecki:

if we use microformats, hCard, we can have a plugin that converges these for any given site

Ryan Barrett:

I have a half-finished user style for hCard that does this, but I need someone better with CSS and JS

Tantek Çelik:

If we get the markup right, we can share a CSS style that does this well.

usually I'm OK with "ship something crappy and iterate it" but this needs to be at least as good as native

wavis:

can we take out the grid? can it just try automatically?

Aaron Parecki:

getting the user preferences is tricky because you are matching both sides' preferences

Tantek Çelik:

I have some friends who only use AIM, others who only use gTalk you need to meet their UX

wavis:

I want to add multiplexing - I want to read and or send with one interface

we want status messaging too - know what is possible then

Tantek Çelik:

that is what is done live on the server - my apps can update the availability of the server

if you look at a Windows phone it is based on people centric UI, but ti just expresses your addressbook

Ryan Barrett:

silos have started to do this- they can route preferences but they are silo'd

Tantek Çelik:

can we collect the URI schemes for launching all these apps?

Ryan Barrett:

there are fairly well-documented ways to find the URLs for iOS/Android etc

Tantek Çelik:

i want to hack on this tomorrow morning. The stretch goal is to do it doing purely with web standards websockets/WebRTC

Adam Brault:

we have a way to do peer to peer but fall back on silos

the challenge of WebRTC is it it peer to peer and you have to bring your own signalling

it should be the most federated example - this is why we combine xmpp with WebRTC

Aaron Parecki:

could I do signalling that is not XMPP?

Adam Brault:

yes you don't have to use XMPP, we can build a signalling mechanism

Aaron Parecki:

as long as we have servers, we can do the discovery right?

Kevin Marks:

the challenge is routing between clients and discovering IP+port - if you have a server you can make this work

Adam Brault:

github.com/andyet/signalmaster is a signal server that talky.io uses, you could run this

Kevin Marks:

if you want a shim, you can detect facebook and twitter with client-side iframes if they aren't logged in

Darius C. Dunlap:

if it's blue you're in iMessage, if it's green it's SMS

this is a cool idea - it's piece of doing the next step of bringing them to my website first

at least it's a nascar that it is situationally aware