userinfo.me support

[BigBlueHat]

This idea/spec is still in the very early stages, but I wanted to share it here as I think it'd be a good fit for @unhosted.

Let me know what you think of it. The example is minimal, but does work, and shows promise. 😀

[michielbdejong]

nice idea! you should mention on your site why you're not simply using webfinger (which reached RFC status recently), but i want useraddress to be "polyglot", so i'll gladly add it if it's not too much work. are you publishing one for yourself yet, can i test it?

[BigBlueHat]

The test examples should work. I need to add more.

There's no reason this couldn't return an XRD doc, but I've not dug
into WebFinger enough to know what else would be needed. Happy to learn
more thought. :)

userinfo.me is also meant to cover much more ground by simply being a
URL for an entity that handles Content Negotiation. Whatever else it
does is up to the implementer...by design. :)

Feedback more than welcome!

On Mon Nov 4 10:58:27 2013, Michiel@unhosted wrote:

nice idea! you should mention on your site why you're not simply using
webfinger (which reached RFC status recently), but i want useraddress
to be "polyglot", so i'll gladly add it if it's not too much work. are
you publishing one for yourself yet, can i test it?

—
Reply to this email directly or view it on GitHub
#3 (comment).

[michielbdejong]

check out https://datatracker.ietf.org/doc/rfc7033/ it's now JSON. it would be good to give an example of what sort of use case would be covered by userinfo.me but not by webfinger

[melvincarvalho]

On 4 November 2013 17:44, Michiel@unhosted notifications@github.com wrote:

check out https://datatracker.ietf.org/doc/rfc7033/ it's now JSON. it
would be good to give an example of what sort of use case would be covered
by userinfo.me but not by webfinger

I can name several:

• Friends lists
• Unordered lists
• Representing numbers
• Nested data, such as a public key
• Financial data, such as transactions

The list goes on and on ... this is why I cant use JRD for anything more
than a very simple use case

There's also no validator, so everyone has implemented it differently. I
know of no single example which follows the standard (yes, that includes
remotestorage too)

As userinfo.me supports content negotiation I'd rather suggest a more
permissive serialization such as JSON LD, which can model anything you need

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