mirror of
https://github.com/vacp2p/rfc.vac.dev.git
synced 2025-02-23 04:48:26 +00:00
chore: update markdown
This commit is contained in:
parent
2a91b48efd
commit
f3bf3a9875
@ -74,7 +74,10 @@ async function fetchDirectoryContents(dirUrl, basePath, prefixToRemove) {
|
|||||||
function adjustPathForMarkdown(filePath) {
|
function adjustPathForMarkdown(filePath) {
|
||||||
const parts = filePath.split('/')
|
const parts = filePath.split('/')
|
||||||
|
|
||||||
|
console.log(filePath)
|
||||||
|
|
||||||
if (parts?.length === 1) return filePath
|
if (parts?.length === 1) return filePath
|
||||||
|
if (filePath.includes('README.md')) return filePath
|
||||||
|
|
||||||
if (parts[parts.length - 1].endsWith('.md')) {
|
if (parts[parts.length - 1].endsWith('.md')) {
|
||||||
parts.splice(parts.length - 2, 1)
|
parts.splice(parts.length - 2, 1)
|
||||||
|
@ -406,7 +406,7 @@ message PushNotificationResponse {
|
|||||||
Where `message_id` is the `message_id` sent by the client.
|
Where `message_id` is the `message_id` sent by the client.
|
||||||
|
|
||||||
#### Handle Notification Response:
|
#### Handle Notification Response:
|
||||||
- A `PushNotificationResponse` message MUST be wrapped in a [`ApplicationMetadataMessage`](../62/payloads.md) with type set to<EFBFBD><EFBFBD>`PUSH_NOTIFICATION_RESPONSE`.
|
- A `PushNotificationResponse` message MUST be wrapped in a [`ApplicationMetadataMessage`](../62/payloads.md) with type set to `PUSH_NOTIFICATION_RESPONSE`.
|
||||||
|
|
||||||
- The response MUST be sent on the [partitioned topic](../../waku/standards/application/54/x3dh-sessions.md) of the sender and
|
- The response MUST be sent on the [partitioned topic](../../waku/standards/application/54/x3dh-sessions.md) of the sender and
|
||||||
MUST not be encrypted using the [secure transport](../../waku/standards/application/53/x3dh.md) to facilitate the usage of ephemeral keys.
|
MUST not be encrypted using the [secure transport](../../waku/standards/application/53/x3dh.md) to facilitate the usage of ephemeral keys.
|
||||||
|
@ -1,4 +1,9 @@
|
|||||||
# Vac Raw Specifications
|
# Vac RFCs
|
||||||
|
|
||||||
All Vac specifications that have not reached **draft** status will live in this repository.
|
Vac builds public good protocols for the decentralise web.
|
||||||
To learn more about **raw** specifications, take a look at [1/COSS](../1/coss.md).
|
Vac acts as a custodian for the protocols that live in the RFC-Index repository.
|
||||||
|
With the goal of widespread adoption,
|
||||||
|
Vac will make sure the protocols adhere to the set of principles,
|
||||||
|
including but not limited to liberty, security, privacy, decentralisation, and inclusivity.
|
||||||
|
|
||||||
|
To learn more, visit [Vac Research](https://vac.dev/)
|
||||||
|
4
vac/raw/README.md
Normal file
4
vac/raw/README.md
Normal file
@ -0,0 +1,4 @@
|
|||||||
|
# Vac Raw Specifications
|
||||||
|
|
||||||
|
All Vac specifications that have not reached **draft** status will live in this repository.
|
||||||
|
To learn more about **raw** specifications, take a look at [1/COSS](../1/coss.md).
|
@ -1,6 +1,5 @@
|
|||||||
## Deprecated RFCs
|
# Waku RFCs
|
||||||
|
|
||||||
Deprecated specifications are no longer used in Waku products.
|
Waku builds a family of privacy-preserving, censorship-resistant communication protocols for web3 applications.
|
||||||
This subdirectory is for achrive purpose and
|
|
||||||
should not be used in production ready implementations.
|
Contributors can visit [Waku RFCs](https://github.com/waku-org/specs) for new Waku specifications under discussion.
|
||||||
Visit [Waku RFCs](https://github.com/waku-org/specs) for new Waku specifications under discussion.
|
|
||||||
|
6
waku/deprecated/README.md
Normal file
6
waku/deprecated/README.md
Normal file
@ -0,0 +1,6 @@
|
|||||||
|
# Deprecated RFCs
|
||||||
|
|
||||||
|
Deprecated specifications are no longer used in Waku products.
|
||||||
|
This subdirectory is for achrive purpose and
|
||||||
|
should not be used in production ready implementations.
|
||||||
|
Visit [Waku RFCs](https://github.com/waku-org/specs) for new Waku specifications under discussion.
|
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading…
x
Reference in New Issue
Block a user