Comment by 🦋 CarloMonte

=> Re: "Is there a SmallWeb service for identity? What's the..." | In: s/SmallWeb

Nice technical question, but more details about your requirements would help understand what exactly you want to achieve, why, and which risks you are ready to accept.

The one sentence about being followed from site A to site B at the risk of profiling/doxing please needs expansion and discussion.

Gemini is the way it is for good reasons...

=> 🦋 CarloMonte

2024-11-10 · 2 months ago

2 Later Comments ↓

=> 🦂 zzo38 · Nov 10 at 21:05:

Of course, it should be optional. That way, you can preserve privacy, as well avoiding to add complexity to implementations that do not want it. (Furthermore, you can have multiple shared profiles in case you do not want only one.)

Another note, is that sometimes a URL can be used to refer to a user ID on some service, but other times (e.g. MUD) a URL cannot be used.

=> 💀 requiem · Nov 18 at 11:59:

finger protocol was basically invented for "identity" and similar things. try:

$ finger rqm@tilde.institue

to see my finger message.

There used to be a page called "about.me" which I liked -- basically a page where you could aggregate stuff about yourself. I'm thinking of launching something similar for Gemini. Just buying domains... :)

Original Post

=> 🌒 s/SmallWeb

Is there a SmallWeb service for identity? What's the smallest viable protocol? I'm thinking if I use the same cert on two sites, and I voluntarily publish two triples (username/site/cert) to an identity service, then it should be possible. If someone knows me on Site1 and they log in to Site2 they could find out my user name on Site2. I can think of a couple of twists to keep people from just harvesting all the data willy nilly. Is there someone like that already? Or a decent proposal?

=> 💬 cquenelle · 7 comments · 2024-11-10 · 2 months ago