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.
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.
Agreed.
Do you think it would be feasible to encrypt the private object names as well?
POST http://montague.example/api/v1/post) and delivering a message (POST http://capulet.example/api/v1/inbox) should absolutely be enforced by the specification. I didn't see that last night, but it became clear after thinking about it.
POST http://montague.example/api/base/v1/post) and delivering a message (POST http://capulet.example/api/base/v1/inbox) should absolutely be enforced by the specification. I didn't see that last night, but it became clear after thinking about it.
yarnd can see old posts. They can even reconstruct old conversations. There is no plausible deniability there, unless you're proposing we remove the non-cached posts permanently. I'm definitely not a fan of that.
:
For @ullarah:
VGhlcmUgaXMgYSBwYXNzd29yZCwgYW5kIHRoZXJlIGlzIG9ubHkgb25lIGZpbGUgaW4gdGhlIGFyY2hpdmUuFor @prologic:
VGFrZSBhIGxvb2sgYXQgdGhlICJGb3JlbnNpY3MiIGNhdGVnb3J5Lg==I definitely made this one too hard. If you want to try some easier ones, take a look in the JavaScript console of CyberChef. There's a whole series of these challenges made by the developers.
:
:
yarnd. Is there a way to see the full history of a feed? I don't see a prev metadata tag on yours.
yarnd and a separate federated chat server could (optionally) share account information so your Yarn account credentials are used for a Matrix or XMPP account on the same server?
Remember: The wizard can help you with his Magic.
<style>.select{display:none}.select:target{display:block}</style>
...
<a href="#option1">1</a> <a href="#option2">3</a> <a href="#option3">3</a>
<div id="option1" class="select">...</div>
<div id="option2" class="select">...</div>
<div id="option3" class="select">...</div>
I hope the second Myria will retain the yellow and blue stripes.
🟩⬛⬛🟨🟨
🟩🟩🟩🟩🟩
The Chrome hack is supposed to be a backup plan. I think it's more than likely they'll just tack the digit on like you'd expect.