Mercurial > prosody-modules
annotate mod_atom/README.markdown @ 5366:db4c66a1d24b
mod_http_oauth2: Fill in some client metadata defaults
Explicit > Implicit
Maybe we should actually use these for something as well? :)
It's is somewhat an open question of how strictly we should enforce
things in the client metadata given that it is somewhat extensible.
Especially some of these enum fields which have corresponding IANA
registries.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 25 Apr 2023 18:09:08 +0200 |
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 |