Email or username:

Password:

Forgot your password?
Top-level
Darius Kazemi

@cwebber @cj I think the model works really well for things that are essentially pure optimization problems with no or few externalities like memory management, but we are talking about interfaces that directly impact social systems (privacy). It's why I brought up the crypto example.

No comments
cj πŸ‡ΊπŸ‡ΈπŸ‡¨πŸ‡­ replied to Darius

@darius @cwebber

Well, you can pick your privacy/security models:
- HTTP signatures, ensuring your JSON-LD isn't putting private fields into public payloads, ensuring delivery matches the recipients list, handling other software's visibility (followers only, unlisted), etc
- OCAP
- <something else>

Nothing says these can't be bridged; they can coexist; adopt the style you want.

Christine Lemmer-Webber replied to Darius

@darius @cj Consider that with cryptography, the main source of advocacy today is "use libsodium because it has abstracted it for you, don't roll your own crypto"

Do you need to understand the black box of libsodium to use it safely? Some people do, but not everyone.

If you follow me, you're reading a "libsodium implementor equivalent". That can give a confused impression of what *use* is like, because I'm talking about the equivalent of crypto people saying blah blah modular arithemtic etc

Go Up