Official Heads is over Matrix

You can lurk the channels by not installing any client, use web browser as client if you register but full experience is through recommended Element client.

Matrix is a federated network: choose your home server

EG: Tested (No e-mail required at registration, tor friendly) home server:

Official Matrix documentation

Matrix<->Slack bridge update

Current Status

The Matrix<->Slack bridge for the Heads OSFW channel is currently non-functional. This situation arose due to the Slack channel transitioning from a paid to a free tier, which has limited functionality and retains only 90 days of chat history.

  • The Matrix channel remains fully operational with complete chat history.
  • The Slack channel has limited functionality and reduced message retention.
  • The bridge between Matrix and Slack is inactive.

Community Communication

The community primarily communicates via Matrix and GitHub.

  • For optimal communication and full access to chat history, please use the Matrix channel (#heads:matrix.org) via Element or any compatible open-source client.
  • GitHub remains an essential platform for project collaboration and issue tracking.

Next Steps

We are working with the Slack channel administrators to resolve this issue. The bridge can be reactivated once necessary adjustments are made on the Slack side.

To restore the bridge functionality, action is required from Slack channel administrators.

Contact

If you have any questions or concerns, please reach out through the Matrix channel or by opening an issue on the Heads-wiki GitHub repository.

Once the issue is resolved, please open an issue on the Heads-wiki to update this notice accordingly.

We appreciate your understanding and continued support as we work to improve our community communication infrastructure.

Thierry Laurion

Supporting the Project

Heads and its source code are free and open source — you never need to donate to use Heads, or to read and contribute to this wiki. But keeping the Heads source code and this documentation (heads-wiki) accurate, current, and reviewed is ongoing work, and it is not free. No one can carry a project alone for too long without becoming overwhelmed.

What donations fund

Donations — with Open Collective payments publicly tracked on the Insurgo Initiative’s Open Collective — have covered real subcontracting work: past expenses show contributors were paid for agreed, reviewed work, exactly the gap that fixed-period grants never close. Grants (such as the NLnet-funded AccessibleSecurity, AuthenticatedHeads, and TPM 2.0 for Heads projects) fund one-off, scoped efforts; they do not fund the ongoing upkeep, test hardware, and documentation maintenance that keeps Heads usable. Donations fund that day-to-day maintenance — maintainer time, and paying the experts who close the gaps.

Recurring support sustains the project

Monthly donations are preferred: they let the project plan ahead and budget its expenses instead of relying on one-off gifts. It is not the number of donors alone but the predictable, recurring total that matters — a steady group of monthly supporters sustains Heads far more reliably than many small one-time gifts.

Contributing is not only monetary

Vendors who build on Heads — NovaCustom, Nitrokey, 3mdeb, Purism — give back not only with money but with code, co-maintainership, and time on tech debt, standardization, and documentation. Purism co-developed code with Heads (the factory/OEM reset, coreboot support); NovaCustom funded specific features. This is what open source means — and commercial users are encouraged to subscribe or contract back into the project they depend on.

Found a bug under Heads/How to Contribute

  1. Refer to Contributing guidelines

(Please reapply same logic principles for Heads-wiki!)

Some specifics:

Other Matrix Rooms