https://www.youtube.com/watch?v=p7ekjtcTs4k
I worked a lot on secure messaging and confidential communication.
I see a great match of work that TBD folks do in the #DWN space with secure and confidential messages.
Sure, it is more of a building block requiring application logic and features, but it is a perfect start.
In general, today's communication channels are broken because that attached to a sensitive identifier like phone or email that is forced to be public and almost impossible to drop or change, especially for phone numbers.
If your phone number gets leaked, you will get spam in the best case.
What if you could have a communication channel with an identifier that is easy to drop or stop following or, even better, have an identifier for different types of relations? Most extreme and privacy-focused pattern - create a new identity for every relationship or, to some extent, for every transaction.
DIDs give you such an identifier.
We all know about did comm, but for me, did comm is to tech, to low-level, and does not offer an end-to-end solution with transport, persistence, and something more user-focused.
We still need to find a balance between privacy and convenience, how to manage KYC and address books for new identifiers, and how to simplify a cognitive load of a network of networks.
vp /
npub1u6…tnd7t
2023-08-13 13:55:37
Author Public Key
npub1u6qhg5ucu3xza4nlz94q90y720tr6l09avnq8y3yfp5qrv9v8sus3tnd7tPublished at
2023-08-13 13:55:37Event JSON
{
"id": "322a3e1a1f47283910c58523b2b5fccca3fff8323780fe7169dfadd7d75af2e3",
"pubkey": "e681745398e44c2ed67f116a02bc9e53d63d7de5eb26039224486801b0ac3c39",
"created_at": 1691934937,
"kind": 1,
"tags": [
[
"t",
"dwn"
]
],
"content": "https://www.youtube.com/watch?v=p7ekjtcTs4k\nI worked a lot on secure messaging and confidential communication.\nI see a great match of work that TBD folks do in the #DWN space with secure and confidential messages.\nSure, it is more of a building block requiring application logic and features, but it is a perfect start.\nIn general, today's communication channels are broken because that attached to a sensitive identifier like phone or email that is forced to be public and almost impossible to drop or change, especially for phone numbers.\nIf your phone number gets leaked, you will get spam in the best case.\nWhat if you could have a communication channel with an identifier that is easy to drop or stop following or, even better, have an identifier for different types of relations? Most extreme and privacy-focused pattern - create a new identity for every relationship or, to some extent, for every transaction.\nDIDs give you such an identifier.\nWe all know about did comm, but for me, did comm is to tech, to low-level, and does not offer an end-to-end solution with transport, persistence, and something more user-focused.\nWe still need to find a balance between privacy and convenience, how to manage KYC and address books for new identifiers, and how to simplify a cognitive load of a network of networks.",
"sig": "69dc37df5d1764e019bd56ef5db2431c33717703990d26c91cc802864ae039aa3af5764d4141fc6bc5d029118d7022e38acfff7c01a6628601de67f3667dc988"
}