Oh, I have a habit of arguing round in circles until things become clear… if you go round long enough eventually contradictions wear off
I do my best to try and put my self in the position of the user, but absorb the technical landscape enough to be able to hopefully at least get a feel for the limits. Threads like this are enormously helpful.
The UX flow in detail for this we haven’t quite come to yet (from an account creation or publishing POV anyway) we’re working through some read-only scenarios at the moment which will help inform all this later as well.
They may also have a multitude of files, some public, some privately shared, that they may chose to associate with one of those identities, or not be associated with an identity at all.
So there needs to be the flexibility for an individual to maintain and publish content in and accessible and human readable way, without the need to create an identity, but create and share or publish with an identity if they choose to.
A building block of this is the thing we are referring to as a
I might have an identity that publishes to many different
domains; or I might have many
domains serving up information that isn’t associated with any individual or organisation at all.
I think the most useful initial starting point for many people will be to create a human readable address capable of receiving/send safecoins; or private messages. A pretty good starting point for most I’d have thought. But I don’t think we should be assuming that is the case for everyone, nor that ‘identity’ is the best place to start… it probably should be opt in to identity (be that private or public) rather than opt out.
(Then there’s also subtleties like one-way only communication, and how people will address that)
So I’m still talking myself into the core of this being the name/domain; not the identity.
I may chose to create an account, and have a bunch of human accessible addresses publishing information in the form of safe://:
Maybe I have a real identity, which publishes to these (in the form of
@<anything>, and it’s
@realme. I have a SafeID profile set up at
safe://@realme that makes that link explicit. I’m the owner of those names/domains, and the comments and posts blogs are published as
Other users can get in touch via
@realme or messages will get also through on a specific context via
Then I have another which is
@fakeme. I allow @fakeme to gust publish on
safe://sports sometimes, just for fun.
But then I have another site
safe://fishinganonymous which isn’t associated with any of my identities, nor with any other user, entity or persona. It has no published SafeID profile, It just publishes stuff about fishing, but readers still send in anonymous tips by addressing
A bit of a long reply, sorry!
Nothing in this is precluded by the approach you set out, but how we create the language, or workflow around these terms, starts to build a mental model for users that effects and forms UX, so needs careful thought and attention, so great that it’s getting it here.