# Can we have some kind of forum PSA channel?

**URL:** https://discourse.nixos.org/t/can-we-have-some-kind-of-forum-psa-channel/77302
**Category:** Meta
**Created:** [April 29, 2026, 3:32am UTC](https://discourse.nixos.org/t/can-we-have-some-kind-of-forum-psa-channel/77302 "2026-04-29T03:32:52Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![TLATER](https://discourse.nixos.org/user_avatar/discourse.nixos.org/tlater/32/4257_2.png) [@TLATER](https://discourse.nixos.org/u/TLATER)
#### Post date: [April 29, 2026, 3:32am UTC](https://discourse.nixos.org/t/can-we-have-some-kind-of-forum-psa-channel/77302/1 "2026-04-29T03:32:52Z")

</div>

From time to time things happen that affect many users. We’ll get a deluge of posts asking for help with such a thing, for example the current switch to [the dbus broker implementation](https://discourse.nixos.org/t/scary-message-about-dbus-after-running-nixos-rebuild-switch/77298).

Having explanations for what’s going on split across many threads causes pretty varying degrees of context. Could we do something to funnel users into the same topic, e.g. with a temporary global banner, ideally without requiring too much moderation involvement?

---

<div class="post-metadata">

### Author: ![vcunat](https://discourse.nixos.org/user_avatar/discourse.nixos.org/vcunat/32/11_2.png) [@vcunat](https://discourse.nixos.org/u/vcunat)
#### Post date: [April 29, 2026, 3:58am UTC](https://discourse.nixos.org/t/can-we-have-some-kind-of-forum-psa-channel/77302/2 "2026-04-29T03:58:43Z")

</div>

Topics in discourse can get pinned. Issues in GitHub, too.

Also, if discussions happen in multiple topics on discourse, it’s easy for a moderator to move them together, etc.

---

<div class="post-metadata">

### Author: ![TLATER](https://discourse.nixos.org/user_avatar/discourse.nixos.org/tlater/32/4257_2.png) [@TLATER](https://discourse.nixos.org/u/TLATER)
#### Post date: [April 29, 2026, 4:02am UTC](https://discourse.nixos.org/t/can-we-have-some-kind-of-forum-psa-channel/77302/3 "2026-04-29T04:02:54Z")

</div>

I only see these features used very rarely though, and usually only for controversial stuff where moderation _needs_ to step in. It’d be nice if we could have this for simply helpful content, too. Presumably this is in part because moderators have too much on their plates.

Can we do something about that?

---

<div class="post-metadata">

### Author: ![vcunat](https://discourse.nixos.org/user_avatar/discourse.nixos.org/vcunat/32/11_2.png) [@vcunat](https://discourse.nixos.org/u/vcunat)
#### Post date: [April 29, 2026, 4:11am UTC](https://discourse.nixos.org/t/can-we-have-some-kind-of-forum-psa-channel/77302/4 "2026-04-29T04:11:02Z")

</div>

Note that it’s not about the real [NixOS.org](http://NixOS.org) moderators. Pinning on discourse can be done by roughly 20 people currently, if I read it right:  
[https://discourse.nixos.org/g/trust\_level\_4](https://discourse.nixos.org/g/trust_level_4)

> **[Trust Level Permissions Reference](https://meta.discourse.org/t/trust-level-permissions-reference/224824)**
>
> 🔖 This reference aims to be a comprehensive list of Discourse features, marked by Trust Level, and including the relevant admin settings which influence them. Trust Level Grid - Defaults TL = Trust Level dependant ⚙ = Can be enabled or...

---

<div class="post-metadata">

### Author: ![dtomvan](https://discourse.nixos.org/user_avatar/discourse.nixos.org/dtomvan/32/31095_2.png) [@dtomvan](https://discourse.nixos.org/u/dtomvan)
#### Post date: [May 6, 2026, 5:41pm UTC](https://discourse.nixos.org/t/can-we-have-some-kind-of-forum-psa-channel/77302/5 "2026-05-06T17:41:31Z")

</div>

There’s [Breaking changes announcement for unstable](https://discourse.nixos.org/t/breaking-changes-announcement-for-unstable/17574) ? If I understand you correctly that seems like a single thread we can send people to for explanations about breaking stuff? I keep it on tracking so I can loosely keep up with it from time to time…

---

<div class="post-metadata">

### Author: ![TLATER](https://discourse.nixos.org/user_avatar/discourse.nixos.org/tlater/32/4257_2.png) [@TLATER](https://discourse.nixos.org/u/TLATER)
#### Post date: [May 6, 2026, 5:58pm UTC](https://discourse.nixos.org/t/can-we-have-some-kind-of-forum-psa-channel/77302/6 "2026-05-06T17:58:25Z")

</div>

The idea is to give drive-by users who aren’t going to look at a 131-reply topic a heads-up.

It’s also not exclusively about breaking changes, some changes are non-breaking - such as the one about the dbus broker, the new implementation is compatible.

---

<div class="post-metadata">

### Author: ![dtomvan](https://discourse.nixos.org/user_avatar/discourse.nixos.org/dtomvan/32/31095_2.png) [@dtomvan](https://discourse.nixos.org/u/dtomvan)
#### Post date: [May 6, 2026, 10:08pm UTC](https://discourse.nixos.org/t/can-we-have-some-kind-of-forum-psa-channel/77302/7 "2026-05-06T22:08:40Z")

</div>

> [@TLATER](#):
>
> The idea is to give drive-by users who aren’t going to look at a 131-reply topic a heads-up

You can just scroll to the bottom for the 3-ish most recent posts, no? All the old ones are irrelevant since you’ve either hit the issue yourself without reading the post, or you didn’t and you just moved on…

> [@TLATER](#):
>
> It’s also not exclusively about breaking changes, some changes are non-breaking

Well, it’s up to the package maintainers to decide whether they make an announcement or not. Technically some announcements may be helpful but aren’t about any breaking changes, but I guess one can just make a new topic in the development category for that and link people there from any help requests or bug reports we get.

---

<div class="post-metadata">

### Author: ![TLATER](https://discourse.nixos.org/user_avatar/discourse.nixos.org/tlater/32/4257_2.png) [@TLATER](https://discourse.nixos.org/u/TLATER)
#### Post date: [May 7, 2026, 3:02am UTC](https://discourse.nixos.org/t/can-we-have-some-kind-of-forum-psa-channel/77302/8 "2026-05-07T03:02:51Z")

</div>

> [@dtomvan](#):
>
> You can just scroll to the bottom for the 3-ish most recent posts, no?

_I_ can, and would if I was on unstable. Hell, I’d set up an RSS feed for that thread.

New users on the other hand often don’t even know what a stability guarantee _is_. They don’t know that they should be looking at that thread, or that they should scroll to the bottom of it.

> [@dtomvan](#):
>
> Technically some announcements may be helpful but aren’t about any breaking changes, but I guess one can just make a new topic in the development category for that and link people there from any help requests or bug reports we get.

I wouldn’t mind that at all - I think a new announcements sub-category would be more suited, but in either case not burying these things in a thread would help massively with visibility, and as a result hopefully prevent the duplicate post situation we have currently.

This is kind of exactly what I’m advocating for; this would be _much_ more transparent for novice users, already.

But it’s still not just modules, IMO threads like the recent Linux CVE thread would be appropriate in there too, for example. Many “situations” relevant to practically all users don’t end up in the current breaking changes thread.
