mirror of
https://github.com/versia-pub/docs.git
synced 2026-03-13 02:49:16 +01:00
fix: ✏️ Edit text for better consistency
This commit is contained in:
parent
94f437f539
commit
1f864b89c8
7 changed files with 14 additions and 18 deletions
|
|
@ -47,13 +47,13 @@ Accept: application/jrd+json
|
|||
}
|
||||
```
|
||||
|
||||
## Server Discovery
|
||||
## Instance Discovery
|
||||
|
||||
Server metadata can be accessed by making a `GET` request to the server's Versia metadata endpoint, which is located at `/.well-known/versia`.
|
||||
Instaance metadata can be accessed by making a `GET` request to the instance's Versia metadata endpoint, which is located at `/.well-known/versia`.
|
||||
|
||||
### Example
|
||||
|
||||
To discover the metadata of the server `versia.social`, an instance would make a `GET` request to `https://versia.social/.well-known/versia`.
|
||||
To discover the metadata of the instance `versia.social`, an instance would make a `GET` request to `https://versia.social/.well-known/versia`.
|
||||
|
||||
This endpoint will return an [InstanceMetadata](/entities/instance-metadata) entity.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ export const metadata = {
|
|||
|
||||
# Validation
|
||||
|
||||
Implementations **MUST** strictly validate all incoming data to ensure that it is well-formed and adheres to the Versia Protocol. If a request is invalid, the server **MUST** return a `400 Bad Request` HTTP status code.
|
||||
Implementations **MUST** strictly validate all incoming data to ensure that it is well-formed and adheres to the Versia Protocol. If a request is invalid, the instance **MUST** return a `400 Bad Request` HTTP status code.
|
||||
|
||||
<Note>
|
||||
Remember that while *your* implementation may disallow or restrict some user input, other implementations may not. You **should not** apply those restrictions to data coming from other instances.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue