Meeting took place 2026-05-06T17:55:00Z→2026-05-06T19:13:00Z.
Next meeting is scheduled for 2026-05-19T17:00:00Z→2026-05-19T18:00:00Z.
Attendance
- @exodrifter (leader)
- @lunarequest (facilitator)
- @outfrost (secretary)
Agenda
- Review the financial report
- Settle on a Wiki/Notion Alternative
- Discuss the threat model
Decisions
Wiki.js was chosen as a wiki/documentation solution, to replace wiki pages on Discourse. This choice will be reevaluated should a potentially better option emerge.
@lunarequest will host our Wiki.js instance.
Notes
Finance report
Discourse costs a significant amount of money to run, due to demanding to act as a Docker orchestrator, and to be run on the container host itself. This is why the tsuki server is provisioned separately just to run Discourse.
The moonlight server, running Forgejo, tuwunel, LiveKit, Cinny, and Out Of Your Element, tends to hover around 10% CPU usage and 40-50% RAM usage, with 33% swap used at the time of checking. It’s provisioned with 2 vCPUs and 4 GB of RAM.
@exodrifter had recently made savings of about 74 USD per year by switching from ProtonMail to PurelyMail as our email provider.
Wiki alternative
We had briefly tested Wiki.js (hosted by @lunarequest) and MediaWiki (hosted by @exodrifter) as potential replacements for Discourse wiki pages. MediaWiki, while a mature and competent option, was deemed to have too tall of a learning curve, not convenient enough, and too cumbersome to maintain (e.g. requiring edits to a php source file in order to change site configuration, user groups or group memberships). It was decided that Wiki.js, despite its shortcomings (no user links or mentions, configuration limitations, development with a bus factor of 1), is our best choice for the time being.
Several other options had been considered, and rejected for various reasons, e.g. user-friendliness, licensing, SSO support, hosting complexity, and LLM involvement, among others.
Threat model
@outfrost had been assigned to draft a threat model for t/suki, but was unable to prepare it for this meeting. This topic was postponed until the next meeting.
Misc
- @outfrost suggested trying out Cryptpad for private, real-time collaborative docs editing; will try hosting a test instance when time permits.
- Context: We had also briefly tried out HedgeDoc (on a public instance), with good results in terms of real-time collaboration, but had found its access control to not meet our needs.
- @exodrifter brought up that (according to sociocracy best practices) we ought to decide on how meeting attendees would consent to minutes being published.
- It was then decided that, in our circle, we are okay with minutes being published by default, and will edit them and/or raise concerns should an issue arise.
- We have officially lost, and subsequently recovered, 2 circle documents. These are the first to ever be lost, and to be recovered, in tech circle’s history.
Backlog of topics
We plan to discuss these topics at future meetings.
- Threat model
- AI crawler defense
- Wiki contribution guidelines
- Testing of backups
- Writing bespoke software (e.g. event scheduling, to replace When2meet and Discourse events)
- Turning all t/suki members into furries (jk (unless? (force-tf?)))