Meeting took place 2026-09-01 17:02 to 18:01 UTC.
Next meeting is scheduled for 2026-09-22 17:00 to 18:00 UTC.
- @exodrifter (leader, interim facilitator)
- @outfrost (secretary)
- @fuguesoft
- The Admin circle has approved a membership policy. In particular:
- A newcomer's membership in a circle is granted once existing members consent to it
- If a circle member misses 3+ meetings without notice or retroactive justification, they are marked as inactive
- Inactive members do not count towards decision-making quorum
- An inactive member can resume attending meetings and return to active membership at will, unless other members decide to revoke their memebership in the meantime
- A member is expected to be able to dedicate at least 3 hours a week to meetings and circle tasks
- Onboard @fuguesoft
- Discuss technical possibilities for implementing Community circle's to-be NSFW content policies
- Explore Wiki contribution guidelines
- Revisit Discourse backups not working
- Discuss potential contributions to greencal
@fuguesoft expressed that they would like to join the Tech circle because they're passionate about gamedev, and interested in learning more about self-hosting. They said they have yet to figure out what kind of work they'd like to do for t/suki, and that it'll be part of the learning process.
@fuguesoft's membership has been approved.
Community circle would like to learn what kind of options exist in (or are easy to add to) the services we run that would allow for opt-in viewing of NSFW content, in particular content gating, tag-based content warnings, spoilering, blurring/hiding of sensitive media, etc.
So far we know about the following:
- Discourse
- We can add users manually to a group, and gate visibility of forum categories based on group
- There is no way to gate direct messages
- Matrix
- Encrypted DMs cannot be filtered, and any enforcement in DMs in general would be difficult
- Users on Matrix join individual rooms, it's not possible to grant someone a single group membership to let them into gated rooms and spaces
- We can, however, set rooms and/or spaces to be invite-only, and invite users manually when approved; this could in theory be automated, but may require significant effort developing a bot
- Forgejo
- We can require repositories with adult-only content to be private (meaning invite-only, where invites are managed by repository owner(s))
@exodrifter will research further options for content visibility controls on our services, in particular:
- Is there a concern about explicit content on the service?
- In what ways can we control access to and/or visibility of such content?
- Are there ways to circumvent the access controls?
@exodrifter will schedule a maintenance to update Discourse again soon. It was suggested to make a VM snapshot before beginning the update.
- @fuguesoft is interested, but doesn't know Haskell
- @outfrost is somewhat interested in contributing to the frontend side
We plan to discuss these topics at future meetings.
- Threat model (once a draft is available)
- Wiki contribution guidelines
- Testing of backups
- Writing bespoke software (e.g. event scheduling, to replace When2meet and Discourse events)