@room mentions in Forgejo Matrix Main Channel #435

tebriel commented 2026年01月09日 14:55:51 +01:00

Recently there were some opinions expressed about how mentions happen in the main forgejo channel on matrix. Some suggested we stop using @room mentions as some clients don’t support muting them, or even moving these mentions to a specific announcements room. The announcements room might be nice as it prevents those @room announcements from getting lost behind a lot of backscroll. Are there other options/opinions on how to approach this?

Recently there were some opinions expressed about how mentions happen in the main forgejo channel on matrix. Some suggested we stop using @room mentions as some clients don’t support muting them, or even moving these mentions to a specific announcements room. The announcements room might be nice as it prevents those @room announcements from getting lost behind a lot of backscroll. Are there other options/opinions on how to approach this?

Gusted commented 2026年01月09日 23:59:53 +01:00

https://matrix.to/#/#forgejo-releases:a-0.me exists which could be repurposed to be the official announcement channels.

https://matrix.to/#/#forgejo-releases:a-0.me exists which could be repurposed to be the official announcement channels.

Beowulf commented 2026年01月10日 00:11:00 +01:00

I forgot about this.

I think, there are multiple things to consider:

1. There are already users complaining, that there are to many rooms and it is hard to find the right one
2. People are annoyed by room pings
3. These pings exist in the chat room, helm room, debian room and I may forgot some.
   Should all pings be merged in one room? Which could in the end mean more pings for everyone.

---

I can think of these two solutions:

1. Having a single account from where the messages (or pings) are coming. So the members can either mute room pings or mute the user (or even block the user, if it is just used for the pings - could be automated with a bot replying with @room to announcment messages). The benefit of this would be, there is no need for another room. For most user there will be no change.
2. A seperate room - people need to actively join them and they need to know that announcments are not in the "main" room (it also needs to be clear in the future for new joiners).
   The question is, if the situation in the helm and debian room are fine or if these pings would then also move to an announcement room. If so it would mean more pings for everyone. Seperate announcment rooms would mean even more rooms (and people are already complaining sometimes).

In general I think Matrix isn't the perfect basis for this, but it is the basis, so we need to work with it 🤔

I forgot about this. I think, there are multiple things to consider: 1. There are already users complaining, that there are to many rooms and it is hard to find the right one 2. People are annoyed by room pings 3. These pings exist in the chat room, helm room, debian room and I may forgot some. Should all pings be merged in one room? Which could in the end mean more pings for everyone. *** I can think of these two solutions: 1. Having a single account from where the messages (or pings) are coming. So the members can either mute room pings or mute the user (or even block the user, if it is just used for the pings - could be automated with a bot replying with `@room` to announcment messages). The benefit of this would be, there is no need for another room. For most user there will be no change. 2. A seperate room - people need to actively join them and they need to know that announcments are not in the "main" room (it also needs to be clear in the future for new joiners). The question is, if the situation in the helm and debian room are fine or if these pings would then also move to an announcement room. If so it would mean more pings for everyone. Seperate announcment rooms would mean even more rooms (and people are already complaining sometimes). In general I think Matrix isn't the perfect basis for this, but it is the basis, so we need to work with it 🤔

Beowulf commented 2026年01月28日 22:33:00 +01:00

Let's try something.

Please respond with an emoji showing how you see the situation or how it could be improved for you.
If you don't like any of the proposed solutions, please comment on how a solution could look like for you. Others can react with a 👍 to express that they prefer the proposed solution.

• 😆 : I'm fine with the current approach. No changes need to be made.
• 🎉 : I'm not annoyed, but if it is changed, I would prefer if pings are done by a single account (a bot) in the main chat room.
• ❤️ : I'm not annoyed, but if it is changed, I would prefer that the pings are moved to a separate room.
• 🚀 : I'm annoyed and would prefer that the pings be done by a single bot account in the main chat room.
• 👀 : I'm annoyed and would prefer that the pings be moved to a separate room.

Let's try something. Please respond with an emoji showing how you see the situation or how it could be improved for you. If you don't like any of the proposed solutions, please comment on how a solution could look like for you. Others can react with a 👍 to express that they prefer the proposed solution. - 😆 : I'm fine with the current approach. No changes need to be made. - 🎉 : I'm **not** annoyed, but if it is changed, I would prefer if pings are done by a single account (a bot) in the main chat room. - ❤️ : I'm **not** annoyed, but if it is changed, I would prefer that the pings are moved to a separate room. - 🚀 : I'm annoyed and would prefer that the pings be done by a single bot account in the main chat room. - 👀 : I'm annoyed and would prefer that the pings be moved to a separate room.

msrd0 commented 2026年01月31日 10:33:55 +01:00

My main answer would be I'm not annoyed, but if it is changed, I would prefer that the pings are moved to a separate room. But, I think that the announcements should be divided up by their "priority". If a security release was made that should be installed ASAP, then I believe a room ping should happen in all rooms. For things like the monthly report which I'd consider lowest priority that I could just as well read days later, a normal message in some separate room with no room ping (so ppl can decide whether to mute these notifications or not) should be enough. Then maybe normal releases could be room ping'ed in a separate room, which (at least my client) gives me the option to not mute while muting non-pinging messages.

My main answer would be _I'm **not** annoyed, but if it is changed, I would prefer that the pings are moved to a separate room._ But, I think that the announcements should be divided up by their "priority". If a security release was made that should be installed ASAP, then I believe a room ping should happen in all rooms. For things like the monthly report which I'd consider lowest priority that I could just as well read days later, a normal message in some separate room with no room ping (so ppl can decide whether to mute these notifications or not) should be enough. Then maybe normal releases could be room ping'ed in a separate room, which (at least my client) gives me the option to not mute while muting non-pinging messages.

0ko commented 2026年05月29日 18:12:40 +02:00

I'd like to add that as a releases team member I've been getting more anxious from thought of doing security release announcements with at-room mentions in main Forgejo Chat because it will ping a lot of people, most of which are not self-hosting. I'd prefer to do that in a dedicated room.

I think major releases can still be announced with at-room because they are rare and invite some useful skimming through release notes or blog post to learn about changes that would actually affect Forgejo usage for everyone, not just for instance maintainers.

I'd like to add that as a releases team member I've been getting more anxious from thought of doing security release announcements with at-room mentions in main Forgejo Chat because it will ping a lot of people, most of which are not self-hosting. I'd prefer to do that in a dedicated room. I think major releases can still be announced with at-room because they are rare and invite some useful skimming through release notes or blog post to learn about changes that would actually affect Forgejo usage for everyone, not just for instance maintainers.

alterNERDtive commented 2026年06月10日 16:50:54 +02:00

Bringing my comment over from the matrix room so it doesn’t get lost:

to add to this, i am not in the release announcement room for a reason: i don’t want to receive release announcements via matrix. release announcements should happen in the release announcements room.

Bringing my comment over from the matrix room so it doesn’t get lost: > to add to this, i am not in the release announcement room for a reason: i don’t want to receive release announcements via matrix. release announcements should happen in the release announcements room.

ingenarel-NeoJesus commented 2026年06月10日 16:54:24 +02:00

here's my two cents copy pasted from the forgejo chat:

can the releases please be in a seperate channel or something?

i'm just in codeberg chat because i use codeberg and somtimes wanna talk about codeberg issues that i'm having/feature requests, and i'm in forgejo chat because codeberg uses forgejo and when i need to interact with codeberg via scripts and stuff i need to use the forgejo api and also why not join the chat

i don't run my own git forge, so i really don't need announcement pings

i'm in the tuwunel (matrix homeserver) chat and tuwunel announcements both. because i run my own tuwunel instance so i want pings from there too

just saying, no hate

here's my two cents copy pasted from the forgejo chat: > can the releases please be in a seperate channel or something? > i'm just in codeberg chat because i use codeberg and somtimes wanna talk about codeberg issues that i'm having/feature requests, and i'm in forgejo chat because codeberg uses forgejo and when i need to interact with codeberg via scripts and stuff i need to use the forgejo api and also why not join the chat > i don't run my own git forge, so i really don't need announcement pings > i'm in the tuwunel (matrix homeserver) chat and tuwunel announcements both. because i run my own tuwunel instance so i want pings from there too > just saying, no hate

crispycat commented 2026年06月12日 19:27:15 +02:00

Something that happens quite often with Matrix (specifically using Schildi/Element) in my experience is scrolling occasionally bugs out with large amounts of messages, making it impossible to actually view the one with the mention, moving them to a separate room would fix this

Something that happens quite often with Matrix (specifically using Schildi/Element) in my experience is scrolling occasionally bugs out with large amounts of messages, making it impossible to actually view the one with the mention, moving them to a separate room would fix this

0ko commented 2026年06月13日 14:20:23 +02:00

To sum up the current votes:

• 14 people think no changes are needed
• there are 32 votes to have something changed (I haven't checked for duplicate votes)
  • out of them, 4 people are annoyed with current state of things
  • out of them, the majority favors a separate room over a single bot account with 23/9 votes

So it's pretty clear now that we should move these notifications to a separate room. We might try to have Forgejo Moderation Account take over room #forgejo-releases:a-0.me as it's founder during room migration to Forgejo v12. Alternatively, it is also possible to just create a new room.

To sum up the current votes: * 14 people think no changes are needed * there are 32 votes to have something changed (_I haven't checked for duplicate votes_) * out of them, 4 people are annoyed with current state of things * out of them, the majority favors a separate room over a single bot account with 23/9 votes So it's pretty clear now that we should move these notifications to a separate room. We might try to have Forgejo Moderation Account take over room `#forgejo-releases:a-0.me` as it's founder during room migration to Forgejo v12. Alternatively, it is also possible to just create a new room.