Mercurial > prosody-modules
annotate mod_atom/README.markdown @ 5117:2b94ee74d1f1
Backed out changeset 85882735fd33
This wasn't a complete fix and the complete fix is way too complex
for me to do right now without a test setup.
author | Jonas Schäfer <jonas@wielicki.name> |
---|---|
date | Sat, 17 Dec 2022 14:13:06 +0100 |
parents | f478e325529e |
children |
rev | line source |
---|---|
3257 | 1 # Introduction |
2 | |
3 This module exposes users [microblogging][xep277] on Prosodys built-in HTTP server. | |
4 | |
3574
f478e325529e
mod_atom/README: Add some text about where to look for the atom feed
Kim Alvefur <zash@zash.se>
parents:
3257
diff
changeset
|
5 # Usage |
f478e325529e
mod_atom/README: Add some text about where to look for the atom feed
Kim Alvefur <zash@zash.se>
parents:
3257
diff
changeset
|
6 |
f478e325529e
mod_atom/README: Add some text about where to look for the atom feed
Kim Alvefur <zash@zash.se>
parents:
3257
diff
changeset
|
7 With default HTTP settings, the microblog of `user@example.com` would be |
f478e325529e
mod_atom/README: Add some text about where to look for the atom feed
Kim Alvefur <zash@zash.se>
parents:
3257
diff
changeset
|
8 seen at `https://example.com:5281/atom/user`. |
f478e325529e
mod_atom/README: Add some text about where to look for the atom feed
Kim Alvefur <zash@zash.se>
parents:
3257
diff
changeset
|
9 |
3257 | 10 # Configuration |
11 | |
12 The module itself has no options. However it uses the access control | |
13 mechanisms in PubSub, so users must reconfigure their microblogging node | |
14 to allow access, by setting `access_model` to `open`. | |
15 E.g. Gajim has UI for this, look for "Personal Events" → "Configure | |
16 services". | |
17 |