view mod_manifesto/README.markdown @ 3656:3e0f4d727825

mod_vcard_muc: Add an alternative method of signaling avatar change When the avatar has been changed, a signal is sent that the room configuration has changed. Clients then do a disco#info query to find the SHA-1 of the new avatar. They can then fetch it as before, or not if they have it cached already. This is meant to be less disruptive than signaling via presence, which caused problems for some clients. If clients transition to the new method, the old one can eventually be removed. The namespace is made up while waiting for standardization. Otherwise it is very close to what's described in https://xmpp.org/extensions/inbox/muc-avatars.html
author Kim Alvefur <zash@zash.se>
date Sun, 25 Aug 2019 20:46:43 +0200
parents 777554cf1ae1
children
line wrap: on
line source

---
summary: Module for raising awareness about the Security Test Days
...

Introduction
============

This module informs users about the XMPP Test day and whether their
contacts are affected. For mor info about the test day, see
<https://stpeter.im/journal/1496.html>

Configuration
=============

``` lua
manifesto_contact_encryption_warning = [[
    Your rant about security here
]]
admin_contact_address = "mailto:xmpp@example.com"
```

`admin_contact_address` can be a JID or a `mailto:` URI.

The default for `manifesto_contact_encryption_warning` is the following:

    Hello there.

    This is a brief system message to let you know about some upcoming changes to the $HOST service.

    Some of your contacts are on other Jabber/XMPP services that do not support encryption.  As part of an initiative to increase the security of the Jabber/XMPP network, this service ($HOST) will be participating in a series of tests to discover the impact of our planned changes, and you may lose the ability to communicate with some of your contacts.

    The test days will be on the following dates: January 4, February 22, March 22 and April 19.  On these days we will require that all client and server connections are encrypted.  Unless they enable encryption before that, you will be unable to communicate with your contacts that use these services:

    $SERVICES

    Your affected contacts are:

    $CONTACTS

    What can you do?  You may tell your contacts to inform their service administrator about their lack of encryption.  Your contacts may also switch to a more secure service.  A list of public services can be found at https://xmpp.net/directory.php

    For more information about the Jabber/XMPP security initiative that we are participating in, please read the announcement at https://stpeter.im/journal/1496.html

    If you have any questions or concerns, you may contact us via $CONTACTVIA at $CONTACT

Translations would be appreciated. There is currently a Swedish
translation residing in a text file in the same directory as the module.