Change the client to get what we want

From Federated Social Web Incubator Group
Jump to: navigation, search


Goals

This section is incomplete. You can help by expanding it.

Notes

  • contacts api is progressing
  • w3c contacts api exists too! they're working on merging it

[StatusNet]

  • as web app i need to be able to:
    • get the user's identity (so I can route a subscription request)
    • set the user's identity (so the proper place to route to is in the list)
      • these are still a little wonky; currently mostly targets auth/login
    • get other contacts from the user (so we can suggest friends, do typeahead, etc)
      • that part might be feasible with the current plugin!
  • for our remote subscribe (and fave/repeat/comment....) we'd love something like:
    • site asks the browser for an identity
      • specify what kinds of identity we're interested "someone who speaks ostatus"
    • user may have option to pick an identity
    • browser responds with the needed info
    • site does whatever it needed
  • Ability to cause a browser to auth on demand
  • Browser should keep track of stuff I use/have, and surface that to the page when requested
  • Want ability to <verb> things as <some user> out on the web (similar to how rss subscribe works today in the browser, but pluggable)

[kinda generalizes into discussion of cross-domain data storage generally]

check out x prefs as example

  • data store that can allow other sites to read it
  • a little bit of structure and type
  • Need to look at desktop OSes, see what the functionality gap is (there are analogues to apps registering themselves as handlers, for example)
  • How can we create federated identities which don't suffer from correlation attacks? Can the client help?

Outcomes

This section is incomplete. You can help by expanding it.

== People

This section is incomplete. You can help by expanding it.