Federated vs Delegated

Get Started. It's Free
or sign up with your email address
Federated vs Delegated by Mind Map: Federated vs Delegated

1. aesthetics

2. possibilities limited only by imagination, politics

3. Facebook

4. Facebook

4.1. Centralised

4.2. One persona: your civil identity since Facebook requires real name

4.3. Compartmentalisation under that one identity is possible, but Facebook keeps oversight over all of the different contexts you use your account for

5. brand power

6. OpenID: only authentication, no trust. Trust depends on online reputation of url that is claimed.

7. off-site activities published to the huge Facebook ecosystem via Newsfeed

8. Facebook: proprietary

8.1. marketing power

9. decisive

10. limited only by developer imagination

11. user choice / transferable

12. Open ID

12.1. slowly becoming more viable (via Google Social Graph API, OAuth, Portable Contacts, example)

12.2. security conscious but so new it's unclear how phishable eg.

12.3. option for stronger authentication

13. OpenID

14. OpenID

14.1. Inconsistent, but improving (see Google LSO and JanRain RPX)

14.2. could be applicable to more people as it does offer more sources of identity

15. usability

15.1. Facebook

15.1.1. familiarity

15.1.2. trust

15.1.3. ease of use

16. access to data

16.1. Facebook

16.1.1. already richly populated for many people

16.1.2. limited to what FB chooses to expose

16.1.3. single persona

16.1.4. tends towards private

16.1.5. arguably secure

16.1.6. password only protection (no strong auth)

17. ownership of technology

17.1. OpenID: open source & federated

17.1.1. consensus

17.1.2. broader pool of innovators

17.1.3. Unified conversations on social web (i.e. not Facebook only, Google only, etc.)

18. existing user base

18.1. Facebook

18.1.1. huge and self aware

18.2. OpenID

18.2.1. larger, potentially, though currently unaware and disinterested

19. other

20. website deployment support

20.1. Facebook

20.1.1. Easy for Facebook

20.1.2. Requires ongoing support for multiple proprietary vendors if desired

20.2. OpenID

20.3. Easy, consistent support for all open standard ID and data providers

21. Trust and privacy

21.1. OpenID

21.1.1. Decentralised

21.1.2. Multiple OpenID accounts for multiple, non-linkable personas