chatnet
A place for your group’s conversations.
Channels keep topics separate. Direct messages are between two people.
Night shift starts now. Tonight’s theme is train stations — anything you recorded while waiting for something that left without you.
Utrecht platform 4, 05:40. Mono, no wind cover, you can hear the announcement bleed through.
That announcement has been my alarm for three years. Sending mine from platform 2 in Leiden before the line closes.
Stitching the submissions into one set — same command as last month:
# fade each entry into the nextsox *.flac night-shift.aiff trim 0 10800 fade 8Order of the set, with the timestamps we agreed on.
Joining from the 22:10 out of Leiden. One bar of signal, so I’ll mostly listen.
You can tell who is around before you type.
You pick a state in your own panel and it shows up everywhere you appear: beside your name in a member list, in a conversation header, in a direct message. Role is a separate thing, set per server.
- Online
- around, available to chat
- Idle
- away from the keyboard
- Do not disturb
- reading, not replying
- Invisible
- appears offline to everyone
Being online means someone is there. It does not promise a reply.
Each channel is its own conversation.
Categories keep a server legible once it grows past a handful of rooms. In Slow Radio the listening channel is the set itself, field recordings is raw audio, gear swap is equipment. Same server, three different jobs.
Unread counts sit on the channel that moved, so you can skip the ones that did not.
Your fade cuts the Leiden announcement too early — 8 seconds clips the last word. Re-do it at 14?
Send the raw file and I’ll re-stitch it before midnight.
Raw, unedited. Watch the last twenty seconds.
And the private version of the same thing.
A direct message is one-to-one. You open it from a person rather than a channel, and it keeps the same composer, the same attachments and the same presence in the header. The only thing that changes is the audience.
The left column lists conversations you already have. Nothing appears there from strangers.
Create an account to open oneOrder of the set, with the timestamps we agreed on.
Stitching the submissions into one set — same command as last month:
# fade each entry into the nextsox *.flac night-shift.aiff trim 0 10800 fade 8Files land in the message, not in a download tray.
Drop a file and it previews in place: images open in a lightbox, video and audio play inside the message, a PDF shows a page count, and anything else arrives as a download card with its original name. Ten megabytes per upload.
Markdown works in every message. Bold, italics, strikethrough, inline code, links, and fenced blocks that keep their language label.
Images, video attachments, audio and PDFs preview inline. An emoji picker sits next to the composer.
From six channels down to two.
Example communities, not servers to browse. A server is a container for channels; a direct message is a conversation with one person in it.
An ambient and field-recording collective that mixes one night set every month.
yuki — Set is rendered. 3:00:08, fade 8s, no gaps.
A reading group that works through one paper a week and keeps the notes.
mara — Section 4 is where the argument actually happens. Everyone still reading?
Four flatmates, four channels, one invite link. No moderation.
fen — Boiler fixed. It was the valve, not the thermostat.
Bring your group to chatnet.
Make a server, put a few channels in it, send the invite link. The reading above is the same thing every member sees, minus your own messages.
