another-im/anotherim-server
Watch
5
0
Fork
You've already forked anotherim-server
 0
Code Issues Pull requests Projects Releases 1 Packages 1 Wiki Activity Actions
1 release 1 tag
  • v2026.10.26 16ac0bfd59

    ejabberd modules 2026-10-26 Stable

    ann released this 2026-10-26 04:14:46 +00:00 | 6 commits to master since this release

    Signed by ann
    SSH key fingerprint: SHA256:W5M34SUfd1n6UVfu3dIKsi8wVTbvCykT2F7caAghIFU

    Three ejabberd modules as Debian packages for ProcessOne's ejabberd 26.09-1 .deb (each Depends: ejabberd (= 26.09-1)).

    The packages

    • ejabberd-mod-apush: another.im push. A plugin for ejabberd's own mod_push that decides what a device is woken for, seals the summary to the device's key and hands it to apushd. Other clients' push registrations (Conversations, Monal, ...) are left to stock mod_push. Carries mod_apush_muc for room mentions.
    • ejabberd-mod-component-iq: lets a component trusted by mod_privilege (the Telegram gateway) send its own iqs to upload. and pubsub. instead of having them dropped (processone/ejabberd#4472).
    • ejabberd-mod-schedule: scheduled messages (urn:tacky:schedule:0). The server holds the message and sends it as the user at the chosen time, into the archive and the carbons. Kept in Mnesia, sent once over a cluster.

    Install

    On every cluster node:

    dpkg -i ejabberd-mod-apush_*.deb ejabberd-mod-component-iq_*.deb ejabberd-mod-schedule_*.deb

    ejabberd.yml

    Under modules:, mod_apush's block is unchanged from the previous packages (replace the stock mod_push: {} and mod_push_keepalive: {}):

    mod_push:
  notify_on: all
  include_body: false
  include_sender: false
mod_push_keepalive:
  resume_timeout: 72h
  wake_on_timeout: true
mod_apush:
  grace_period: 120
  push_window: 20
mod_component_iq: {}
mod_schedule:
  max_horizon: 31536000
  max_per_chat: 100
  max_total: 500
  max_bytes: 262144
  pass_through:
    - "telegram.@HOST@"

    mod_schedule needs no SQL: it keeps its table in Mnesia (made at first start, copied to every node of the cluster). db_type: sql is optional for a server that keeps its modules in SQL. Keep telegram.@HOST@ even without the gateway. mod_schedule needs mod_mam, mod_carboncopy, mod_offline and mod_privacy, all in the default configuration.

    Restart

    On each node: ejabberdctl stop and start it again, or systemctl restart ejabberd.

    What changed since the previous packages (2026-10-25)

    • Quiet push: a message sent silently is still pushed, marked silent in the sealed summary, so the app shows it without a sound. A scheduled message released by mod_schedule does not count as the user being active on another device.
    • One push per album, not one per picture.
    • No push for poll votes, poll results, live-location moves or technical messages carrying the sender's no-push hint (urn:tacky:push-hint:0). A mention or a reply to the user still pushes.
    • New package ejabberd-mod-schedule: scheduled messages.
    Downloads