CAREFUL.PARTY(7) Miscellaneous Information Manual CAREFUL.PARTY(7)

careful.party — A private tilde and IPv6 VLAN for careful people

This document contains information specific to the careful.party tilde server. Familiarity with Unix-like systems and the command line is assumed. If you are not familiar with these, you can learn more by invoking help(1) back at the command line, or by searching online for tutorials.

If you haven't already, please read conduct(7). Web visitors may click the link. Members reading this from a terminal may instead access the page as follows, back at the command line:

$ man conduct

Programs commonly recognized as text editors are available from the command line. In alphabetic order, these are:

The easiest to use for those unfamiliar with any of the above is nano(1). Members desiring a vim-like experience may want to try out kak(1).

In your home directory, there is a file called .careful.party This file is where you can assign Wireguard keys and addresses from your IP address block to your devices, set which IP addresses or users can connect to your devices (if any), and whether to enable SSH authentication via Wireguard for each device.

Once you are done editing this file, run apply-prefs to validate your changes and apply them.

By default, connections between devices and outgoing connections from the server to member devices are blocked. The blocklist and allowlist options allow you to specify which IP addresses or users are allowed to initiate connections to which devices.

You can connect to the private careful.party IRC server from any device on the Wireguard VLAN. The IRC server runs on port 6667 at inner.careful.party.

When you logged in to your account over SSH for the first time, you were prompted to set a shell password. To log in to IRC with an external IRC client from a Wireguard-connected device, use your account username and, for your password, your account username followed by a colon and then your shell password. I.e.,

<username>:<shell password>

If you wish to change your IRC password to something other than your shell password after logging in, you can do so with:

/msg NickServ PASSWD <current password> <new password> <new password again>

weechat and irssi are both installed on the inner.careful.party server and set up to log you in to the private IRC server automatically. If you change your password, you will have to also change the password in your weechat and irssi configuration files before they will work again.

The main channel is called #main. You will automatically join this channel when launching weechat or irssi on the server. To join it from one of your Wireguard-connected devices, you can enter:

/join #main

Members may include a .plan file in their home directories. This file is commonly treated as a sort of internal journal. You may view a member's .plan file with the finger(1) command. E.g., to view lykso's .plan file:

$ finger lykso

Members may also keep a collection of quotes they like for other members to peruse in the .quotes file in their home directories. Each quote should be separated by a line containing only three equal signs. I.e.,

===

The qotd script uses this string to split quote files into discrete quotes when selecting a quote of the day. Any quotes longer than 1,024 characters will be discarded from consideration.

To ensure each member has an equal chance of having a quote drawn, the qotd script first selects a member at random and then selects a quote from their .quotes file.

Everything under ~/public/html can be accessed publicly at the address https://careful.party/~<you>

Everything under ~/inner/html can be accessed by Wireguard-connected devices at https://inner.careful.party/~<you>

Members can send and receive email to and from each other while connected to the Wireguard network. This can be done with the mail(1) utility via username alone while shelled in to the server, or via the inner.careful.party domain with an email client of your choosing running on a Wireguard-connected device.

The IMAP server runs behind SSL on port 993. You can connect to it over Wireguard at the hostname inner.careful.party using your shell username and password. You can connect to the SMTP server the same way at port 465. To send and receive email, you will have to connect to both.

Internal and public git web hosting are both provided via cgit at https://git.inner.careful.party and https://git.careful.party respectively. Any bare repositories set up under ~/inner/git will show up under the former, and any set up under ~/public/git will show up under the latter.

Git operations can accordingly be achieved over SSH, with read-only access over HTTP/HTTPS. Patch submission and acceptance can be achieved via email.

The examples below demonstrate how to work with internal git repositories. To work with public-facing ones, substitute careful.party for inner.careful.party and public/git for inner/git

To start a new bare repository on the server under the ~/inner/git directory, using my-repo as an example, run

$ git init --bare ~/inner/git/my-repo

This command can also just be passed to your SSH client from the command line on your terminal.

You can then add the bare repository as a remote and push to or pull from it. Assuming you have inner.careful.party configured as a host in the ~/.ssh/config file on your terminal:

$ git remote add origin \
  ssh://<username>@careful.party/home/<username>/inner/git/my-repo
$ git push --set-upstream origin main

To clone your own repository to another device with SSH access:

$ git clone <username>@careful.party:inner/git/my-repo

Cloning a repository over HTTP or HTTPS may be achieved like so:

$ git clone https://git.inner.careful.party/<username>/<project>

Cloning another member's repository over SSH, provided you have the correct permissions to read the repository, can be achieved by either passing the absolute path to the repository or specifying it relative to your own home directory. As an example:

$ git clone <you>@careful.party:../<them>/inner/git/<repo>

Issue tracking and pull requests generally may be achieved by putting your changes on a special branch and alerting the author via email or IRC, or by using the git send-email command.

The tilde does not yet provide a way to host asynchronous group discussions, unfortunately, so public discussions around issues and pull requests will have to happen on an ad-hoc basis for now.

conduct(7) irssi(1) git-send-email(1)

OpenBSD 7.9 September 3, 2026 CAREFUL.PARTY(7)