- User Since
- Jan 13 2019, 16:26 (4 w, 6 d)
Fri, Feb 15
Thu, Feb 14
The main and probably the only good thing that I have written in code of Andreas is function process_event(). It reads an «event» (a concept similar to Envelope), checks its signatures and decides whether it has enough valid signatures to store the message from it. If it isn't (for example, the signature of the post's author is missing), the «event» remains unprocessed, and no posts are being stored into the system.
Wed, Feb 13
Wed, Feb 6
Sat, Feb 2
Before continuing this task, I need to do T59: Render Envelope to string.
Replaced with T57: Function to create envelopes from messages.
Tue, Jan 29
Mon, Jan 28
The header will look the same, but I'll move the resulting field from Message to Envelope, since priciples of signing and verifying should be universal for messages, profiles, etc.
Sun, Jan 27
Sun, Jan 20
I think this syntax is better.
One header contains all hashes for one person.
Sat, Jan 19
Also, let's talk about future. There is a chance that I will add some feature for making aliases for people. For example, you define, that you refer to person with a certain hash as to Max, and then you can link to Max in both body and headers. It doesn't matter if reader doesn't know this Max of if reader knows only another Max: in context of your envelope, «Max» always refers to whoever you meant. (See T54.) Headers which can use such aliases are Written-By and similar ones, but also... Signature. If something is signed by Max, we need first to find out who the hell Max is.
There are two options how a signed envelope could look like.
Fri, Jan 18
Jan 16 2019
To implement this, I am going to introduce new entity: PersonRef. It is not a Person, and not even an incomplete Person. It is just a reference that can be used to find a Person.
Written-By header will actually contain not Persons but PersonRefs.