view mod_atom/README.markdown @ 4515:2e33eeafe962

mod_muc_markers: Prevent any markers from reaching the archive, even if untracked Original intention was to leave alone things that this module isn't handling. However markers in archives are just problematic without more advanced logic about what is markable and what is not. It also requires a more advanced query in mod_muc_rai to determine the latest markable message instead of the latest archived message. I'd rather keep the "is archivable" and "is markable" definition the same for simplicity. I don't want to introduce yet another set of rules for no reason. No markers in MAM.
author Matthew Wild <mwild1@gmail.com>
date Mon, 22 Mar 2021 15:55:02 +0000
parents f478e325529e
children
line wrap: on
line source

# Introduction

This module exposes users [microblogging][xep277] on Prosodys built-in HTTP server.

# Usage

With default HTTP settings, the microblog of `user@example.com` would be
seen at `https://example.com:5281/atom/user`.

# Configuration

The module itself has no options. However it uses the access control
mechanisms in PubSub, so users must reconfigure their microblogging node
to allow access, by setting `access_model` to `open`.
E.g. Gajim has UI for this, look for "Personal Events" → "Configure
services".