add a way to retrieve contacts about sockethub HOT 5 CLOSED

OK, why not submit a pull request?

I was thinking about this recently. So, ideally what happens is the
contacts are stored in remoteStorage, in a 'contacts' module. Sockethub
does no contact management (of course), but can fetch contact lists from
various social networks -- leaving it to the app the worry about merging
in, identifying duplicates, etc.

On area I'm not sure the answer to yet, breaks up into several questions:

1. how should the contacts look when they come back to the client after the
   fetch request?

• Is this something we should be concerned with activity streams for?
• Or is it another "out of scope" situation that has more to do with
  sockethub internals than the problem domain activity streams was meant to
  address?
• What should the response verb be, fetch?
  1. Does the response come back as a non-massaged raw facebook data?
• So the app would need to know all the various parsing rules for each
  social network (i dont like the idea of making the app worry about this,
  but it's faster & simpler for sockethub, and what you implemented in your
  patch)?
• Or, should each entry come back either as it's own response, or in an
  array, but massaged and normalized?

Curious to know if you've given it much thought as you were writing this
feature? Or just wanted to get the data from facebook to the app and didn't
think about these questions? I'm a little hesitant to just make the app
handle the various data formats of the different platforms - that seems to
go against the ideal of sockethub, don't you think?

Cheers!
Nick

On Thu, Mar 7, 2013 at 8:43 AM, Michiel@unhosted
[email protected]:

i know the syntax for this is still up in the air, but i went ahead and
created a 'fetch' verb that allows you to retrieve the list of facebook
friends of the current user:

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/54
.

from sockethub.

i'll make it a pull request when it works, right now it's still just experimental code.

yes, i'm also writing the contacts module at the same time, but connected only via the app, so remoteStorage and sockethub don't have talk to each other directly

from sockethub.

On Thu, Mar 7, 2013 at 8:50 PM, Michiel@unhosted
[email protected]:

i'll make it a pull request when it works, right now it's still just
experimental code.

yes, i'm also writing the contacts module at the same time, but connected
only via the app, so remoteStorage and sockethub don't have talk to each
other directly

yeah, that's the best way to go. are you planning to add data
normalization? if so we should discuss the format, otherwise I will do it
and make some tickets for after you pull request

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/54#issuecomment-14602683
.

from sockethub.

yeah, i am going to work ahead a little bit in my fork with several things i need for myself, to survive in the No Cookie Crew. And then we can see which ones you want to merge upstream (you already indicated for instance you're not interested in the 'shell' platform, that's fine) and for the ones you do want to merge in, how they all fit in.

in this case i think it's easiest if you just copy that o.fetch function from the link above, and fit that into your code in a way that makes sense to how you're architecting it. as soon as upstream sockethub can fetch facebook contacts, i will update https://unhosted.org/adventures/13/Dealing-with-users-in-unhosted-web-apps.html to refer to Sockethub master instead of to my 'adventures fork'.

For that, also, maybe at some point you want to tag a version tag that apps can refer to? because if an app says 'this app requires sockethub', then it will get bit rot every time something changes; it's much easier for an app to be able to say 'this app requires sockethub-0.17.3'

from sockethub.

Issue more than a year old, closing.

from sockethub.