Small changes
This commit is contained in:
parent
cf8a94eb39
commit
54e0cdc52a
|
@ -4,7 +4,7 @@ Aether is a Reddit-like p2p social network - a public discussion forum designed
|
|||
|
||||
### Identity
|
||||
|
||||
Identities in Aether are based on keypairs, like in ssb. As with ssb, the human-readable usernames are not unique, although users can choose a custom nickname. Multi-device usage is currently possible, but difficult (requires manually porting a user config file). There is a strategy for multiple device logins under development that would allow users to store and sync encrypted keys from a remote backend.
|
||||
Identities in Aether are based on keypairs, like in ssb. As with ssb, users can choose a custom nickname, although it is not unique. Multi-device usage is currently possible, but difficult (requires manually porting a user config file). There is a strategy for multiple device logins under development that would allow users to store and sync encrypted keys from a remote backend.
|
||||
|
||||
### Network
|
||||
|
||||
|
|
|
@ -20,28 +20,28 @@ Users can choose a [global, memorable nickname,](https://xmpp.org/extensions/xep
|
|||
|
||||
XMPP is implemented in a distributed client-server architecture.
|
||||
|
||||
The basic protocol data unit in XMPP is an XML "stanza", a fragment of XML that is sent over a stream.
|
||||
### Data
|
||||
|
||||
### Data Storage/Message Persistence
|
||||
The basic protocol data unit in XMPP is an XML "stanza", a fragment of XML that is sent over a stream.
|
||||
|
||||
An XMPP client may store data on the server. Whether it is accessible to others or not depends on the client implementation.
|
||||
|
||||
Default settings for a Jabber server [store information](https://jabber.at/p/privacy/) including: saved contacts ("buddies"), offline messages, error logs, and perhaps chat messages and file uploads for a limited number of days.
|
||||
|
||||
### Moderation/Reputation
|
||||
### Moderation & Reputation
|
||||
|
||||
Due to the federated nature of XMPP, moderation actions are only respected if they are supported by the client.
|
||||
|
||||
Some examples of moderation in XMPP:
|
||||
[An experimental spec for groupchat moderation](https://xmpp.org/extensions/xep-0425.html)
|
||||
|
||||
### Social/Discovery
|
||||
### Social & Discovery
|
||||
|
||||
XMPP includes the ability for users to advertise their network availability or "presence." This is not strictly necessary for the exchange of data, but facilitates real-time interaction by indicating the the recipient is online and available. Users can subscribe to each other's presence statuses.
|
||||
|
||||
Users have contact lists called "rosters". Rosters are [often stored on the server](https://www.blikoontech.com/tutorials/xmpp-made-simple-roster-and-presence-explained) to protect the user's social graph.
|
||||
|
||||
### Privacy/Access Control
|
||||
### Privacy & Access Control
|
||||
|
||||
XMPP specifies that channel encryption should be used for the XMPP and HTTP channel via SSL or TLS.
|
||||
|
||||
|
@ -81,3 +81,4 @@ Applications that use XMPP are varied, and have many different business models,
|
|||
|
||||
[XMPP About](https://xmpp.org/about/technology-overview.html)
|
||||
[XMPP Wikipedia](https://en.wikipedia.org/wiki/XMPP)
|
||||
[XMPP Core Memo](https://xmpp.org/rfcs/rfc3920.html)
|
||||
|
|
Loading…
Reference in New Issue