Jump to content

Akademy/2023/IM Infrastructure BoF

From KDE Community Wiki
Revision as of 15:50, 22 August 2023 by Joseph (talk | contribs) (Meeting Notes: Added update re Telegram bridge shutdown)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Meeting Notes

Telegram Bridge

  • needs to go away as we lost access to some of this due to it being reported as spam
  • runs on infrastructure which we could only use for a short period of time
  • set up new Telegram bridge, but only for external facing rooms
    • causes high load
    • big spam source, as banning isn't propagated
  • update [2023-08-22]: see this mailing list post about the Telegram bridge retirement

IRC Bridge

  • plans to set up our own bridge existed already, predating the Libera bridge shutdown announcement
  • planned for deployment in August
  • only explicitly set up rooms will be bridged, reusing existing rooms, should be largely transparent to current users
  • for about six month we couldn't bridge new rooms, hosting our own bridge would solve that

What are the (valid) use-cases for Telegram bridging

  • about half of the users on our Matrix server are from Telegram
  • a large part of this is however people using both
  • Telegram is extensively used in some local communities (e.g. Brazil)
  • the overall goal is to have people on Matrix, running the bridge indefinitely was never the idea

Matrix server

  • currently ~15k users, ~10k accounts have recently been purged
  • hosted by EMS, and assumed to remain that way for the foreseeable future
  • should it ever be needed we can move that, and would get a full dump of our data there
  • new server for the bridge could also run bots, but someone would need to create those
  • working towards moving accounts to invent SSO
    • should this be limited to developer accounts only?
  • initially we had open registration, which caused spam incidents and ended up with our instance blocked

Managing rooms

  • for new rooms, file a sysadmin ticket so it gets covered by the moderation system
  • reporting spam/abuse in any KDE room using the built-in report option will trigger bans that are propagated to all rooms
  • all this needs to be documented on the Matrix wiki page
  • do we need more people helping with moderation?
    • a few more people might help
    • problem: this implies admin powers over all rooms