Do you think it would be feasible to encrypt the private object names as well?
My thinking here is that a simple KV store is enough here and place the burden on the "client" to deal with things like querying the data.
My thinking here is that a simple KV store is enough here and place the burden on the "client" to deal with things like querying the data.
1. All messages from and to all users sent after X date (when starting up)
2. All messages from and to a specific user sent before Y date (when viewing history)
All of this would need to utilize pagination so we aren't sending 500 messages to a client all at once.
These query options could be added to the JSON object store I'm proposing, but I don't see how they might be used outside of storing messages.
1. All messages from and to all users sent after X date (when starting up)
2. All messages from and to a specific user sent before Y date (when viewing history)
All of this would need to utilize pagination so we aren't sending 500 messages to a client all at once.
These query options could be added to the JSON object store I'm proposing, but I don't see how they might be used outside of storing messages.
Shall we focus on the design/spec of the actual base protocol first though? I'd like to get a design/spec we can all agree on and a poc server/client implemented with a goal of I can message
@mckinley@mckinley.cc
Shall we focus on the design/spec of the actual base protocol first though? I'd like to get a design/spec we can all agree on and a poc server/client implemented with a goal of I can message
@mckinley@mckinley.cc
ssh client, because that's me, no-matter where I am. The only exception to this rule is I usually create a separate key for any "work" / " company" I am a part of.
ssh client, because that's me, no-matter where I am. The only exception to this rule is I usually create a separate key for any "work" / " company" I am a part of.
1. You can verify that a device key belongs to the person to whom you mean to send messages. If you verify the keys with someone in person and suddenly start receiving messages from their account with a different key, you'll know something's going on.
2. It's easier to register new clients, because you can just type in a username and a password.
The problem with things like certificate or key revocation as is possible with GPG (IHMO) is that this makes the system a bit centralised where you have to rely on publishing your key(s) or certificates to a "key server" and if your key(s) having to publish a revocation.
The problem with things like certificate or key revocation as is possible with GPG (IHMO) is that this makes the system a bit centralised where you have to rely on publishing your key(s) or certificates to a "key server" and if your key(s) having to publish a revocation.
A property of ec keys is deriving new keys that can be determined to be "on curve." bitcoin has some BIPs that derive single use keys for every transaction connected to a wallet. And be derived as either public or private chains. https://qvault.io/security/bip-32-watch-only-wallets/
A property of ec keys is deriving new keys that can be determined to be "on curve." bitcoin has some BIPs that derive single use keys for every transaction connected to a wallet. And be derived as either public or private chains. https://qvault.io/security/bip-32-watch-only-wallets/
I was also reading the cryptographic part of Scuttlebutt: https://ssbc.github.io/scuttlebutt-protocol-guide/
Personally I _think_ Encrypted feeds is a much easier "thing" to support.
Personally I _think_ Encrypted feeds is a much easier "thing" to support.
And I was not aware of that RFC. Will be reading it.
But if I want to tell to everybody that I follow something encrypted. It won't be possible.
echo -n "My secret π€" | keys encrypt -armor -sender gabriel@github \\
-recipient kex1ts0qw8fwkvle2f2xsqumetmr9ev5ppx22rl5hnycen68sanjzl7qnta629 \\
-recipient kex1ts0qw8fwkvle2f2xsqumetmr9ev5ppx22rl5hnycen68sanjzl7qnta627 > msg.enc
echo -n "My secret π€" | keys encrypt -armor -sender gabriel@github \\
-recipient kex1ts0qw8fwkvle2f2xsqumetmr9ev5ppx22rl5hnycen68sanjzl7qnta629 \\
-recipient kex1ts0qw8fwkvle2f2xsqumetmr9ev5ppx22rl5hnycen68sanjzl7qnta627 > msg.enc
echo -n "My secret π€" | keys encrypt -armor -sender gabriel@github \\
-recipient kex1ts0qw8fwkvle2f2xsqumetmr9ev5ppx22rl5hnycen68sanjzl7qnta629 \\
-recipient kex1ts0qw8fwkvle2f2xsqumetmr9ev5ppx22rl5hnycen68sanjzl7qnta627 > msg.enc
echo -n "My secret π€" | keys encrypt -armor -sender gabriel@github \
-recipient kex1ts0qw8fwkvle2f2xsqumetmr9ev5ppx22rl5hnycen68sanjzl7qnta629 \
-recipient kex1ts0qw8fwkvle2f2xsqumetmr9ev5ppx22rl5hnycen68sanjzl7qnta627 > msg.enc