docs(messaging): delivery track#387
Conversation
da48176 to
f718684
Compare
bde8486 to
e63e239
Compare
Ivansete-status
left a comment
Ivansete-status
left a comment
There was a problem hiding this comment.
Thanks!
Just adding some comments in case it helps
| ## Dependencies | ||
|
|
||
| - **AnonComms**: RLN membership allocation LEE program deployed and functional | ||
| - **AnonComms**: Zerokit 1.0 API stable and public |
There was a problem hiding this comment.
They recently deployed 2.0
We are currently using 0.9.0 and need to bump soon
| - 2 Delivery engineers | ||
| - 1 Chat engineer | ||
|
|
||
| The [Developer Preview](2025-package-sds-in-reliable-channel-api.md) delivers the core SDS experience. This milestone completes the [Reliable Channel API](https://github.com/logos-messaging/specs/pull/89) by adding: |
There was a problem hiding this comment.
I didn't notice that currently ongoing PR and raised that one: logos-messaging/specs#104
I'll merge both in one so that we just handle one PR.
|
|
||
| Also, deprecates store hash queries as they enable linkability of participants in same channel from a store node PoV. | ||
| Finally, prepare reliable channel to support de-MLS like encryption. | ||
| Also deprecates store hash queries as they enable linkability of participants in the same channel from a store node PoV. Prepares reliable channel to support de-MLS encryption. |
There was a problem hiding this comment.
I don't think we can fully deprecate store-hash queries because SDS offers the option to configure "retrieval hints" so that the app has mechanism to recover lost messages, and one possible hint is by allowing hash-based queries. We will see how the development evolves, though.
There was a problem hiding this comment.
We don't need to remove this from protocol, but ideally in the future we shouldn't rely on Store nodes.
But I agree, perhaps we might not be able to stop querying store nodes in this milestone. Let's see how it goes.
| | [Risk] | [how to we address this risk] | | ||
| | Risk | (Accept, Own, Mitigation) | | ||
| | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | Reed-Solomon reconstruction in segementation might be reduntant | Reed-Solomon-based reconstruction in Segmentation might be redundant, because SDS-R already ensures re-transmission of messages. Consider removing, discuss with AnonComms team. | |
There was a problem hiding this comment.
I don't think we currently implement or use Reed-Solomon. I didn't see it mentioned on any spec either.
There was a problem hiding this comment.
Reed-Solomon is part of Segmentation
|
|
||
| https://github.com/logos-messaging/pm/issues/318 | ||
|
|
||
| **Owner**: Chat Team |
There was a problem hiding this comment.
This can be for Chat Team of course but, should its implementation live in logos-delivery? It sounds like a low level feature.
There was a problem hiding this comment.
The segmentation library was already migrated to Nim by Chat team, this milestone was defined quite a while ago.
I will add Delivery team here too, because you will need to move it to one of these repos:
3 participants
Description
Define and refactor milestones: