made using Leaflet
The Syllabus
DRAFT

Published

View
—
—
—

Parallel log channels

Both Defender's ORI and The Syllabus have Discord servers that use a system I created, where every user has their own log. This log acts as a place for them to organize their thoughts or rattle off some musings, and for others to give feedback or contribute.

The logs system should be used in conjunction with more "equal" spaces for conversation; it is simply a way to give more space for different concurrent trains of thought.

Defender's ORI logs screenshot

In Defender's ORI, the logs (which I have only screenshotted in part, due to there being many) are each named after the researcher who "owns" the space, but are available for everyone to post in. The result is a mix between an office and a mailbox, where anyone can drop into anyone else's space.

Starting up this kind of log system is as easy as making and naming the channels. Everyone's Twitter account is already a log system!

The Syllabus logs screenshot

In The Syllabus, the logs (which I have screenshotted in full, showing all active threads as of 2026-04-13) only allow the named researcher to write top-level messages to the channel. Everyone else can send messages in threads, and can start their own threads. The result is a structure much more similar to the blogosphere or YouTube, where one creator has a clear real estate advantage within the space.

Implementation of this system requires that each researcher has their own dedicated space where they can write top level messages that others cannot. On Discord, messing around with permissions a little will get you the desired result:

Create a new category.

In the new category, change the default permissions for @everyone:

No one can send messages in the channel.

Everyone can start threads and send messages in threads.

No one can pin messages in the channel.

Create a log for each researcher.

I recommend only creating a log for each researcher that asks for one; it helps to prevent there being a whole bunch of unused logs that you have to archive later.

Set the permissions for each log:

Make a new set of permissions for the "owner" of the log.

Give them the following permissions:

RESEARCHER can send messages in the channel.

RESEARCHER can pin messages in the channel.

And there you have it! A functional log system!

NB: If you are the owner of the channel, you are always able to write in every log system. This means that you will have to be careful to not intrude on someone else's space. A way to prevent this is to give ownership of the Discord to a secondary administrator account, and change all permissions from there. This also makes it easy to test if you have set all permissions correctly, without needing someone else to check for you. (Though, you should still get a second pair of eyes!)

made using Leaflet