logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-05-20 20:09:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

revert changes in messaging-api

Browse Source
This commit is contained in:
Ivan FB 2026-04-29 17:49:10 +02:00
parent 0ede28def9
commit 8734fd5d8f
No known key found for this signature in database
GPG Key ID: DF0C67A04C543270
1 changed files with 0 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
standards/application/messaging-api.md
View File

@ -344,15 +344,6 @@ If the `mode` set is `core`, the initialised `WakuNode` SHOULD use:
`edge` mode SHOULD be used if node functions in resource restricted environment, `edge` mode SHOULD be used if node functions in resource restricted environment,
whereas `core` SHOULD be used if node has no strong hardware or bandwidth restrictions. whereas `core` SHOULD be used if node has no strong hardware or bandwidth restrictions.
**Fetching missed messages on startup**:
The node MUST persist the timestamp of the last message it successfully received or sent before going offline.
After the node is started and subscriptions are set up, the node SHOULD query the
[STORE](https://lip.logos.co/messaging/standards/core/13/store.html) protocol to retrieve messages
missed while offline, scoped to the subscribed content topics and using the persisted timestamp as the
lower bound of the query.
### Messaging ### Messaging
#### Messaging type definitions #### Messaging type definitions