or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Syncing
xxxxxxxxxx
ThreadParticipant Protocol
This protocol coordinates the management of the participants within a single message.
DIDComm itself only transfers messages from one party to one other party. Disclosure of other participants is voluntary and not cryptograhically verifiable. This protocol is another voluntary participation protocol among it's participants.
This protocol works well alongside the ThreadSync Protocol, allowing for missed message discovery and sync: https://hackmd.io/dxoXK4I-TGehMuFRoz1O8g
The following protocol messages allow participants to communicate about adding and removing participants on the thread. Participation is completely voluntary with all interactions.
Each add or remove message uses a new thread, with a parent thread of the thread under subject for modifying participants.
For the listed message examples, the id of the main thread is represented by
[mainthread]
Add Participant
A
share_history
of true indicates that previous messages are expected to be sent to the newly added participant. A value of false indicates that old messages should not be shared. The method of prior message sharing is out of scope for this protocol.the
reason
is an optional human readable explanation of why the participant is being added.Remove Participant
Signals the suggestion of a removal.
ParticipantList
<did>
]Publishes who the sender believes is a participant within the thread. Upon receiving this message, the recipient should compare it to their own list of participants within the thread.
Open Questions
Future Ideas
Typical flow
Alice and Bob are exchanging messages. Alice suggests adding Carol, and Bob signals his agreement by returning a ParticipantList which includes both Alice and Carol.
Bob sends a message to both, and then Carols sends a message to both.
[Message]
has been used to indicate a message of any type.