Fix dead links

This commit is contained in:
Jesse Wierzbinski 2024-03-17 20:29:00 -10:00
parent 7fbd474da2
commit 33cd650ad5
No known key found for this signature in database
3 changed files with 4 additions and 4 deletions

View file

@ -3,7 +3,7 @@
Lysand employs cryptography to safeguard objects from being altered during transit. This is achieved by signing objects using a private key, and then verifying the signature with a corresponding public key. Lysand employs cryptography to safeguard objects from being altered during transit. This is achieved by signing objects using a private key, and then verifying the signature with a corresponding public key.
> [!NOTE] > [!NOTE]
> The 'author' of the object refers to the entity (usually an [Actor](objects/actors)) that created the object. This is indicated by the `author` property on the object body. > The 'author' of the object refers to the entity (usually an [Actor](../objects/actors)) that created the object. This is indicated by the `author` property on the object body.
All HTTP requests **MUST** be sent over HTTPS for security reasons. Servers **MUST NOT** accept HTTP requests, unless it is for development purposes. All HTTP requests **MUST** be sent over HTTPS for security reasons. Servers **MUST NOT** accept HTTP requests, unless it is for development purposes.

View file

@ -2,7 +2,7 @@
Lysand employs JSON (JavaScript Object Notation) entities for its data structure. This format is designed to be straightforward, facilitating easy implementation and comprehension. Lysand employs JSON (JavaScript Object Notation) entities for its data structure. This format is designed to be straightforward, facilitating easy implementation and comprehension.
All JSON entities such as [Publications](/data-entities/publications), [Actors](/data-entities/actors), and [Actions](/data-entities/actions) **MUST** include the following attributes: All JSON entities such as [Publications](objects/publications), [Actors](objects/actors), and [Actions](objects/actions) **MUST** include the following attributes:
## Identifier (ID) ## Identifier (ID)
@ -23,7 +23,7 @@ Example: `2021-01-01T00:00:00.000Z`
The `uri` attribute of an entity is a string that signifies the URI of the entity. It is used to identify the entity, and **MUST** be unique among all entities. This URI **MUST** be unique across the entire network, and include the `id` of the entity in the URI. The `uri` attribute of an entity is a string that signifies the URI of the entity. It is used to identify the entity, and **MUST** be unique among all entities. This URI **MUST** be unique across the entire network, and include the `id` of the entity in the URI.
URIs must adhere to the rules defined [here](/spec). URIs must adhere to the rules defined [here](spec).
## Entity Type ## Entity Type

View file

@ -68,5 +68,5 @@ All responses **MUST** include at least the following headers:
- `Content-Type: application/json; charset=utf-8` if the response contains a body - `Content-Type: application/json; charset=utf-8` if the response contains a body
- `Signature` if the response body is signed (which is typically the case) - `Signature` if the response body is signed (which is typically the case)
- `Cache-Control: no-store` on entities that can be edited directly without using a [Patch](objects/patch), such as [Actors](objects/actors) - `Cache-Control: no-store` on entities that can be edited directly without using a [Patch](objects/patch), such as [Actors](objects/actors)
- A cache header with a `max-age` of at least 5 minutes for entities that are not expected to change frequently, such as [Notes](objects/notes) - A cache header with a `max-age` of at least 5 minutes for entities that are not expected to change frequently, such as [Notes](objects/publications)
- A cache header with a large `max-age` for media files when served by a CDN or other caching service under the server's control - A cache header with a large `max-age` for media files when served by a CDN or other caching service under the server's control