categorize and format all wiki .mds
continuous-integration/drone/push Build is passing Details

This commit is contained in:
Ben Harris 2022-09-29 14:53:09 -04:00
parent f4b35a2f16
commit 54e2389a81
37 changed files with 575 additions and 397 deletions

116
composer.lock generated
View File

@ -4,7 +4,7 @@
"Read more about it at https://getcomposer.org/doc/01-basic-usage.md#installing-dependencies",
"This file is @generated automatically"
],
"content-hash": "a938f0c9200db6bf821ba64b8fd9b39f",
"content-hash": "4819cdd6fda4c82d5fb0f50ad5cf3897",
"packages": [
{
"name": "dflydev/dot-access-data",
@ -83,16 +83,16 @@
},
{
"name": "league/commonmark",
"version": "2.2.2",
"version": "2.3.5",
"source": {
"type": "git",
"url": "https://github.com/thephpleague/commonmark.git",
"reference": "13d7751377732637814f0cda0e3f6d3243f9f769"
"reference": "84d74485fdb7074f4f9dd6f02ab957b1de513257"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/thephpleague/commonmark/zipball/13d7751377732637814f0cda0e3f6d3243f9f769",
"reference": "13d7751377732637814f0cda0e3f6d3243f9f769",
"url": "https://api.github.com/repos/thephpleague/commonmark/zipball/84d74485fdb7074f4f9dd6f02ab957b1de513257",
"reference": "84d74485fdb7074f4f9dd6f02ab957b1de513257",
"shasum": ""
},
"require": {
@ -101,24 +101,26 @@
"php": "^7.4 || ^8.0",
"psr/event-dispatcher": "^1.0",
"symfony/deprecation-contracts": "^2.1 || ^3.0",
"symfony/polyfill-php80": "^1.15"
"symfony/polyfill-php80": "^1.16"
},
"require-dev": {
"cebe/markdown": "^1.0",
"commonmark/cmark": "0.30.0",
"commonmark/commonmark.js": "0.30.0",
"composer/package-versions-deprecated": "^1.8",
"embed/embed": "^4.4",
"erusev/parsedown": "^1.0",
"ext-json": "*",
"github/gfm": "0.29.0",
"michelf/php-markdown": "^1.4",
"phpstan/phpstan": "^0.12.88 || ^1.0.0",
"phpunit/phpunit": "^9.5.5",
"nyholm/psr7": "^1.5",
"phpstan/phpstan": "^1.8.2",
"phpunit/phpunit": "^9.5.21",
"scrutinizer/ocular": "^1.8.1",
"symfony/finder": "^5.3",
"symfony/finder": "^5.3 | ^6.0",
"symfony/yaml": "^2.3 | ^3.0 | ^4.0 | ^5.0 | ^6.0",
"unleashedtech/php-coding-standard": "^3.1",
"vimeo/psalm": "^4.7.3"
"unleashedtech/php-coding-standard": "^3.1.1",
"vimeo/psalm": "^4.24.0"
},
"suggest": {
"symfony/yaml": "v2.3+ required if using the Front Matter extension"
@ -126,7 +128,7 @@
"type": "library",
"extra": {
"branch-alias": {
"dev-main": "2.3-dev"
"dev-main": "2.4-dev"
}
},
"autoload": {
@ -183,7 +185,7 @@
"type": "tidelift"
}
],
"time": "2022-02-13T15:00:57+00:00"
"time": "2022-07-29T10:59:45+00:00"
},
{
"name": "league/config",
@ -368,20 +370,20 @@
},
{
"name": "nette/utils",
"version": "v3.2.7",
"version": "v3.2.8",
"source": {
"type": "git",
"url": "https://github.com/nette/utils.git",
"reference": "0af4e3de4df9f1543534beab255ccf459e7a2c99"
"reference": "02a54c4c872b99e4ec05c4aec54b5a06eb0f6368"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/nette/utils/zipball/0af4e3de4df9f1543534beab255ccf459e7a2c99",
"reference": "0af4e3de4df9f1543534beab255ccf459e7a2c99",
"url": "https://api.github.com/repos/nette/utils/zipball/02a54c4c872b99e4ec05c4aec54b5a06eb0f6368",
"reference": "02a54c4c872b99e4ec05c4aec54b5a06eb0f6368",
"shasum": ""
},
"require": {
"php": ">=7.2 <8.2"
"php": ">=7.2 <8.3"
},
"conflict": {
"nette/di": "<3.0.6"
@ -447,9 +449,9 @@
],
"support": {
"issues": "https://github.com/nette/utils/issues",
"source": "https://github.com/nette/utils/tree/v3.2.7"
"source": "https://github.com/nette/utils/tree/v3.2.8"
},
"time": "2022-01-24T11:29:14+00:00"
"time": "2022-09-12T23:36:20+00:00"
},
{
"name": "psr/event-dispatcher",
@ -503,25 +505,25 @@
},
{
"name": "symfony/deprecation-contracts",
"version": "v2.5.0",
"version": "v3.1.1",
"source": {
"type": "git",
"url": "https://github.com/symfony/deprecation-contracts.git",
"reference": "6f981ee24cf69ee7ce9736146d1c57c2780598a8"
"reference": "07f1b9cc2ffee6aaafcf4b710fbc38ff736bd918"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/symfony/deprecation-contracts/zipball/6f981ee24cf69ee7ce9736146d1c57c2780598a8",
"reference": "6f981ee24cf69ee7ce9736146d1c57c2780598a8",
"url": "https://api.github.com/repos/symfony/deprecation-contracts/zipball/07f1b9cc2ffee6aaafcf4b710fbc38ff736bd918",
"reference": "07f1b9cc2ffee6aaafcf4b710fbc38ff736bd918",
"shasum": ""
},
"require": {
"php": ">=7.1"
"php": ">=8.1"
},
"type": "library",
"extra": {
"branch-alias": {
"dev-main": "2.5-dev"
"dev-main": "3.1-dev"
},
"thanks": {
"name": "symfony/contracts",
@ -550,7 +552,7 @@
"description": "A generic function and convention to trigger deprecation notices",
"homepage": "https://symfony.com",
"support": {
"source": "https://github.com/symfony/deprecation-contracts/tree/v2.5.0"
"source": "https://github.com/symfony/deprecation-contracts/tree/v3.1.1"
},
"funding": [
{
@ -566,20 +568,20 @@
"type": "tidelift"
}
],
"time": "2021-07-12T14:48:14+00:00"
"time": "2022-02-25T11:15:52+00:00"
},
{
"name": "symfony/polyfill-ctype",
"version": "v1.24.0",
"version": "v1.26.0",
"source": {
"type": "git",
"url": "https://github.com/symfony/polyfill-ctype.git",
"reference": "30885182c981ab175d4d034db0f6f469898070ab"
"reference": "6fd1b9a79f6e3cf65f9e679b23af304cd9e010d4"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/symfony/polyfill-ctype/zipball/30885182c981ab175d4d034db0f6f469898070ab",
"reference": "30885182c981ab175d4d034db0f6f469898070ab",
"url": "https://api.github.com/repos/symfony/polyfill-ctype/zipball/6fd1b9a79f6e3cf65f9e679b23af304cd9e010d4",
"reference": "6fd1b9a79f6e3cf65f9e679b23af304cd9e010d4",
"shasum": ""
},
"require": {
@ -594,7 +596,7 @@
"type": "library",
"extra": {
"branch-alias": {
"dev-main": "1.23-dev"
"dev-main": "1.26-dev"
},
"thanks": {
"name": "symfony/polyfill",
@ -602,12 +604,12 @@
}
},
"autoload": {
"psr-4": {
"Symfony\\Polyfill\\Ctype\\": ""
},
"files": [
"bootstrap.php"
]
],
"psr-4": {
"Symfony\\Polyfill\\Ctype\\": ""
}
},
"notification-url": "https://packagist.org/downloads/",
"license": [
@ -632,7 +634,7 @@
"portable"
],
"support": {
"source": "https://github.com/symfony/polyfill-ctype/tree/v1.24.0"
"source": "https://github.com/symfony/polyfill-ctype/tree/v1.26.0"
},
"funding": [
{
@ -648,20 +650,20 @@
"type": "tidelift"
}
],
"time": "2021-10-20T20:35:02+00:00"
"time": "2022-05-24T11:49:31+00:00"
},
{
"name": "symfony/polyfill-php80",
"version": "v1.24.0",
"version": "v1.26.0",
"source": {
"type": "git",
"url": "https://github.com/symfony/polyfill-php80.git",
"reference": "57b712b08eddb97c762a8caa32c84e037892d2e9"
"reference": "cfa0ae98841b9e461207c13ab093d76b0fa7bace"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/symfony/polyfill-php80/zipball/57b712b08eddb97c762a8caa32c84e037892d2e9",
"reference": "57b712b08eddb97c762a8caa32c84e037892d2e9",
"url": "https://api.github.com/repos/symfony/polyfill-php80/zipball/cfa0ae98841b9e461207c13ab093d76b0fa7bace",
"reference": "cfa0ae98841b9e461207c13ab093d76b0fa7bace",
"shasum": ""
},
"require": {
@ -670,7 +672,7 @@
"type": "library",
"extra": {
"branch-alias": {
"dev-main": "1.23-dev"
"dev-main": "1.26-dev"
},
"thanks": {
"name": "symfony/polyfill",
@ -715,7 +717,7 @@
"shim"
],
"support": {
"source": "https://github.com/symfony/polyfill-php80/tree/v1.24.0"
"source": "https://github.com/symfony/polyfill-php80/tree/v1.26.0"
},
"funding": [
{
@ -731,32 +733,31 @@
"type": "tidelift"
}
],
"time": "2021-09-13T13:58:33+00:00"
"time": "2022-05-10T07:21:04+00:00"
},
{
"name": "symfony/yaml",
"version": "v5.4.3",
"version": "v6.1.4",
"source": {
"type": "git",
"url": "https://github.com/symfony/yaml.git",
"reference": "e80f87d2c9495966768310fc531b487ce64237a2"
"reference": "86ee4d8fa594ed45e40d86eedfda1bcb66c8d919"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/symfony/yaml/zipball/e80f87d2c9495966768310fc531b487ce64237a2",
"reference": "e80f87d2c9495966768310fc531b487ce64237a2",
"url": "https://api.github.com/repos/symfony/yaml/zipball/86ee4d8fa594ed45e40d86eedfda1bcb66c8d919",
"reference": "86ee4d8fa594ed45e40d86eedfda1bcb66c8d919",
"shasum": ""
},
"require": {
"php": ">=7.2.5",
"symfony/deprecation-contracts": "^2.1|^3",
"php": ">=8.1",
"symfony/polyfill-ctype": "^1.8"
},
"conflict": {
"symfony/console": "<5.3"
"symfony/console": "<5.4"
},
"require-dev": {
"symfony/console": "^5.3|^6.0"
"symfony/console": "^5.4|^6.0"
},
"suggest": {
"symfony/console": "For validating YAML files using the lint command"
@ -790,7 +791,7 @@
"description": "Loads and dumps YAML files",
"homepage": "https://symfony.com",
"support": {
"source": "https://github.com/symfony/yaml/tree/v5.4.3"
"source": "https://github.com/symfony/yaml/tree/v6.1.4"
},
"funding": [
{
@ -806,7 +807,7 @@
"type": "tidelift"
}
],
"time": "2022-01-26T16:32:32+00:00"
"time": "2022-08-02T16:17:38+00:00"
},
{
"name": "tildeteam/wiki",
@ -862,7 +863,8 @@
"ext-shmop": "*",
"ext-sockets": "*",
"ext-posix": "*",
"ext-mbstring": "*"
"ext-mbstring": "*",
"ext-ctype": "*"
},
"platform-dev": [],
"plugin-api-version": "2.2.0"

View File

@ -9,7 +9,7 @@ $total_users = shell_exec("members team | wc -w");
<div class="row">
<h1>users</h1>
<p><a href="https://kiwi.tilde.chat/#team">
<p><a href="https://tilde.chat/kiwi/#team">
<img src="https://tilde.chat/badges/badge.php?channel=%23team" alt="users online in #team">
</a></p>
<p><?=$online_users?> of <?=$total_users?> total users logged in</p>

View File

@ -4,7 +4,8 @@ published: true
title: account recovery
description: how to get back in to your account
category:
- main
- about
- guides
---
if you ever lose access to your tilde.team account, there are a couple ways

View File

@ -1,10 +1,10 @@
---
author: ~ben and ~khuxkm
published: true
published: false
title: administration
description: ~team admin guide
category:
- main
- admin
---
1. [adding users](#adding-users)

View File

@ -3,26 +3,32 @@ author: ~ubergeek
published: true
title: advanced ssh
description: advanced ssh tricks
category:
- main
category:
- technical
- guides
---
Some more advanced ssh topics.
## SSH Tunnels
SSH can be used as a sort of "poor man's VPN". For example, you want to get into IRC with your local client (mIRC, Weechat, etc), but your local network blocks IRC ports.
SSH can be used as a sort of "poor man's VPN". For example, you want to get into IRC with your local client (mIRC,
Weechat, etc), but your local network blocks IRC ports.
However! Your local network will almost always allow SSH (sysadmins need this for most day to day work). You can connect to tilde.team, and use port forwarding to get on.
However! Your local network will almost always allow SSH (sysadmins need this for most day to day work). You can connect
to tilde.team, and use port forwarding to get on.
If you are connecting from a Linux machine, you can do this:
```
ssh -L 6667:localhost:6667 tilde.team
```
After being logged in, open your local IRC client, and use 127.0.0.1:6667 for your server setting. Voila! You're now on team's IRC server.
After being logged in, open your local IRC client, and use 127.0.0.1:6667 for your server setting. Voila! You're now on
team's IRC server.
What that SSH command did was open a local port tunnel (-L), using local port 6667 (6667:) pointed at localhost (From the remote's point of view), on remote port 6667 (Default IRC port).
What that SSH command did was open a local port tunnel (-L), using local port 6667 (6667:) pointed at localhost (From
the remote's point of view), on remote port 6667 (Default IRC port).
Putty has the same ability (For Windows and Mac users), under Connection --> SSH --> Tunnels.
@ -30,7 +36,8 @@ You can do this for any arbitrary port.
## File Copying
What if you don't want to edit files on the team server, but instead, you want to create it on your local machine? You don't want to have to copy/paste or re-type all of that, right?
What if you don't want to edit files on the team server, but instead, you want to create it on your local machine? You
don't want to have to copy/paste or re-type all of that, right?
SCP to the rescue! SCP copies files over the ssh protocol. It works just like the cp command, but allows you to do this:
@ -42,13 +49,15 @@ As long as you can ssh, you can copy files to and from the remote side. It also
## Mount tilde folders on your machine using sshfs
But what if manually downloading files, editing them, and uploading them again is too tedious? Wouldn't it be great to just be able to edit a file on tilde.team from your home terminal?
But what if manually downloading files, editing them, and uploading them again is too tedious? Wouldn't it be great to
just be able to edit a file on tilde.team from your home terminal?
With sshfs, you can mount a remote folder on your computer, and access it as if it were a local folder.
Refer to your distribution's package manager on how to install sshfs.
Once sshfs is installed, you can mount any folder on tilde.team to any folder on your machine. This example mounts your homefolder to `/tmp/tilde`:
Once sshfs is installed, you can mount any folder on tilde.team to any folder on your machine. This example mounts your
homefolder to `/tmp/tilde`:
`mkdir -p /tmp/tilde && sshfs USERNAME@tilde.team:/home/USERNAME /tmp/tilde`
@ -62,9 +71,11 @@ What if you don't want to really log into team.tilde, but you just need to run a
`ssh tilde.team ping google.com`
The above executes the ping command from the server side of the house. The one thing you need to be careful of here are quotes and input redirection. It can have surprising affects, mixing remote and local pipes.
The above executes the ping command from the server side of the house. The one thing you need to be careful of here are
quotes and input redirection. It can have surprising affects, mixing remote and local pipes.
## SSH config
Each user has their own, personal configuration for ssh. The configuration files lives at `~/.ssh/config.`
A very common thing to do in this file is to create hosts aliases.
@ -76,8 +87,10 @@ host tilde
LocalForward localhost:6667 localhost:6667
```
There are tons of other options, including this LocalForward line to automatically set up the tunnel as show [above](#ssh-tunnels).
There are tons of other options, including this LocalForward line to automatically set up the tunnel as
show [above](#ssh-tunnels).
For more information about the available options, check the man page: `man ssh_config`.
You can set this up remotely, to make jumping to other hosts easier, or locally (If supported in your ssh setup) to make connecting easier for you.
You can set this up remotely, to make jumping to other hosts easier, or locally (If supported in your ssh setup) to make
connecting easier for you.

View File

@ -3,8 +3,10 @@ author: ~ben
published: true
title: bsd.tilde.team
description: an alternate freebsd host for tilde.team
category:
- main
category:
- services
- guides
- technical
---
tilde.team offers an alternate host: [bsd.tilde.team](https://bsd.tilde.team), which runs freebsd 13.
@ -19,7 +21,11 @@ currently it supports:
currently, this vm is hosted on a server i rent from hetzner in germany, so feel free to put your chat client
etc here if you get better ping.
the user creation script copied over the `~/.ssh/authorized_keys` file in your $HOME on ~team. feel free to adjust as needed or holler if you need an admin for something. you should be able to just ssh user@bsd.tilde.team instead of user@tilde.team
the user creation script copied over the `~/.ssh/authorized_keys` file in your $HOME on ~team. feel free to adjust as
needed or holler if you need an admin for something. you should be able to just ssh user@bsd.tilde.team instead of
user@tilde.team
there's a [mailing list thread](https://lists.tildeverse.org/hyperkitty/list/tildeteam@lists.tildeverse.org/thread/LRLAYRTHJLFQWZAXZZW62GYQLW7S2WYC/) for discussion that i'll post updates to. feel free to holler in #team on irc as well.
there's
a [mailing list thread](https://lists.tildeverse.org/hyperkitty/list/tildeteam@lists.tildeverse.org/thread/LRLAYRTHJLFQWZAXZZW62GYQLW7S2WYC/)
for discussion that i'll post updates to. feel free to holler in #team on irc as well.

View File

@ -4,36 +4,63 @@ published: true
title: command line for absolute beginners
description: guide for those looking for a foothold in learning and using gnu+linux
category:
- main
- beginners
- guides
- technical
---
So, you want to join a public-access shell community like tilde.team, but you don't yet have experience using GNU+Linux or other UNIX-like operating systems? This tutorial is designed to give you enough guidance that you can get started and move on to successfully directing your future learning. Once you get a basic level of self-sufficiency, tilde.team is a great place to practice and learn more.
So, you want to join a public-access shell community like tilde.team, but you don't yet have experience using GNU+Linux
or other UNIX-like operating systems? This tutorial is designed to give you enough guidance that you can get started and
move on to successfully directing your future learning. Once you get a basic level of self-sufficiency, tilde.team is a
great place to practice and learn more.
## GNU+Linux is a text-based operating system. And it takes work and thought to start using.
You'll find a lot of people online arguing that GNU+Linux is _not_ a text-based operating system, and that it in fact has a GUI interface just like Windows. It is true that you can use GNU+Linux through a graphical user interface (GUI) like Gnome, or that you can use services from GNU+Linux servers like tilde.team through a web interface. But the people who are so keen on GUIs are saying this to make GNU+Linux sound like an easy transition for Windows or Mac users. However: (1) to really leverage the power of GNU+Linux, you need to learn to interact with it as a text-based system, and (2) while it is different, it's not really that hard. It will take effort to learn the differences, but that effort will pay huge dividends.
You'll find a lot of people online arguing that GNU+Linux is _not_ a text-based operating system, and that it in fact
has a GUI interface just like Windows. It is true that you can use GNU+Linux through a graphical user interface (GUI)
like Gnome, or that you can use services from GNU+Linux servers like tilde.team through a web interface. But the people
who are so keen on GUIs are saying this to make GNU+Linux sound like an easy transition for Windows or Mac users.
However: (1) to really leverage the power of GNU+Linux, you need to learn to interact with it as a text-based system,
and (2) while it is different, it's not really that hard. It will take effort to learn the differences, but that effort
will pay huge dividends.
## How do I connect to a shell server?
The most common way to connect remote GNU+Linux system is with an SSH client. SSH stands for secure-shell. SSH allows you to make a private connection between your computer and a shell server like [tilde.team](https://tilde.team), and it ensures that nobody else along the wire can listen in on your connection. Check out [our SSH page](https://tilde.team/wiki/ssh) for information on connecting to tilde.team over SSH.
The most common way to connect remote GNU+Linux system is with an SSH client. SSH stands for secure-shell. SSH allows
you to make a private connection between your computer and a shell server like [tilde.team](https://tilde.team), and it
ensures that nobody else along the wire can listen in on your connection. Check
out [our SSH page](https://tilde.team/wiki/ssh) for information on connecting to tilde.team over SSH.
If you are having trouble with making your first SSH connection to tilde.team, or anything else while you're learning from this tutorial, drop by the [tilde.team web chat](https://web.tilde.chat/) or email an admin for help ([sudoers@tilde.team](mailto:sudoers@tilde.team)).
If you are having trouble with making your first SSH connection to tilde.team, or anything else while you're learning
from this tutorial, drop by the [tilde.team web chat](https://web.tilde.chat/) or email an admin for
help ([sudoers@tilde.team](mailto:sudoers@tilde.team)).
## What is a shell?
An operating system (OS) is the nuts and bolts that makes all the parts of your computer work together for you. At its core, the OS is not friendly for day to day computer usage. A shell is a user friendly "wrapper" around the operating system that allows you to use it easily. A shell can be graphical, like the Windows or Android GUIs. Or a shell can be text-based. A text based shell, also called a command line interface (or CLI), is a tool you can use to control the operating system by sending it text commands.
An operating system (OS) is the nuts and bolts that makes all the parts of your computer work together for you. At its
core, the OS is not friendly for day to day computer usage. A shell is a user friendly "wrapper" around the operating
system that allows you to use it easily. A shell can be graphical, like the Windows or Android GUIs. Or a shell can be
text-based. A text based shell, also called a command line interface (or CLI), is a tool you can use to control the
operating system by sending it text commands.
What kind of things can you make the OS do? Things like opening files, listing the files in a directory, displaying the current system load, or telling you what other users are currently doing.
What kind of things can you make the OS do? Things like opening files, listing the files in a directory, displaying the
current system load, or telling you what other users are currently doing.
## What is a command?
Commands are simple words, often abbreviated, that make the system do things when typed into the shell. Some simple examples are 'ls' which lists the files in a directory, or 'cd' which changes your location to a new directory (cd = change directory), or 'exit' which logs you out of your current shell session. There are thousands of useful commands, but you only need to know a few to get started and be self-sustaining.
Commands are simple words, often abbreviated, that make the system do things when typed into the shell. Some simple
examples are 'ls' which lists the files in a directory, or 'cd' which changes your location to a new directory (cd =
change directory), or 'exit' which logs you out of your current shell session. There are thousands of useful commands,
but you only need to know a few to get started and be self-sustaining.
This tutorial will teach you the few commands that should allow you to take care of yourself and start down the real, longer-term path of self-directed learning. Once you're logged into tilde.team (or any GNU+Linux shell server), you can practice the following commands as you learn them.
This tutorial will teach you the few commands that should allow you to take care of yourself and start down the real,
longer-term path of self-directed learning. Once you're logged into tilde.team (or any GNU+Linux shell server), you can
practice the following commands as you learn them.
## What are the first commands a new user should learn?
When you're first starting to use a shell in a UNIX-like environment, you will want to be able to do the following things:
When you're first starting to use a shell in a UNIX-like environment, you will want to be able to do the following
things:
1. logging in and logging out
2. list the files or directories in a directory
@ -45,17 +72,22 @@ When you're first starting to use a shell in a UNIX-like environment, you will w
8. download files from elsewhere on the internet
9. learn more about new commands
When you're logged into a shell, you should see a command prompt and a blinking cursor. At this point, simply type a command and hit Enter to run it. You can try this as you work through learning the commands below.
When you're logged into a shell, you should see a command prompt and a blinking cursor. At this point, simply type a
command and hit Enter to run it. You can try this as you work through learning the commands below.
### Logging In, with `ssh`
Recall from the How-Do-I-Connect section above that you can use a SSH client to log into tilde.team. Once you're logged in, you can use the command line SSH client to log into any other shell server; in the example below, let's say you want to log into tilde.town from tilde.team.
Recall from the How-Do-I-Connect section above that you can use a SSH client to log into tilde.team. Once you're logged
in, you can use the command line SSH client to log into any other shell server; in the example below, let's say you want
to log into tilde.town from tilde.team.
Skipping some specifics for now, you can log into tilde.town from a tilde.team shell by using SSH as follows:
> `ssh tilde.team`
Some shell servers allow you to log in with nothing more than a username and password. But increasingly, many servers (like both tilde.team and tilde.town) require you to use ssh keys. To learn more about ssh keys, again, see our [SSH page](ssh).
Some shell servers allow you to log in with nothing more than a username and password. But increasingly, many servers (
like both tilde.team and tilde.town) require you to use ssh keys. To learn more about ssh keys, again, see
our [SSH page](ssh).
### Logging Out, with `logout` or `exit`
@ -69,7 +101,8 @@ To list the files in a directory, simply type `ls`. This will print a list of th
### Changing Directories, with `cd`
You may move from one directory to another with `cd`. Wherever you are in the file system, you can type `cd` by itself to return to your home directory:
You may move from one directory to another with `cd`. Wherever you are in the file system, you can type `cd` by itself
to return to your home directory:
> `cd`
@ -79,24 +112,29 @@ Change to the directory with your html files as follows:
### Read the Contents of a File, with `less`
If you're still in your public_html directory, you should see a file called 'index.php' when you use the `ls` command. Let's peek inside 'index.php' as follows:
If you're still in your public_html directory, you should see a file called 'index.php' when you use the `ls` command.
Let's peek inside 'index.php' as follows:
> `less index.php`
`less` has opened the 'index.php' file for you to read. You cannot edit it; only read it. Type `q` (quit) to stop viewing the file contents and return to the shell.
`less` has opened the 'index.php' file for you to read. You cannot edit it; only read it. Type `q` (quit) to stop
viewing the file contents and return to the shell.
### Edit and Save Changes to a File, with `nano`
`nano` is one of many text editors availble for GNU+Linux. There are many more powerful editors, but we'll start with this one because it is simple. Let's open your 'index.php' file and make some changes.
`nano` is one of many text editors availble for GNU+Linux. There are many more powerful editors, but we'll start with
this one because it is simple. Let's open your 'index.php' file and make some changes.
> `nano index.php`
Now you're viewing the contents of 'index.php' again, but this time you can change the contents. If you don't know HTML, be careful here. Use your arrow keys to move the cursor down to the line that says the following:
Now you're viewing the contents of 'index.php' again, but this time you can change the contents. If you don't know HTML,
be careful here. Use your arrow keys to move the cursor down to the line that says the following:
`<p>Just log in with your secure internet shell to change this file!</p>`
Leave the `<p>` and `</p>` tags as they are, but change the sentence in between them.
Now, save and quit by hitting the key combination Ctrl+x, and then typing 'y' in response to the question about wanting to save the modified buffer.
Now, save and quit by hitting the key combination Ctrl+x, and then typing 'y' in response to the question about wanting
to save the modified buffer.
Now you can pull up a browser to see the change at your tilde.team URL:
'https://tilde.team/~yourUserName'
@ -109,7 +147,8 @@ Let's create a new file in your public_html directory, called 'testing.html'.
'testing.html' did not exist before you opened it with `nano`, so it was created for you.
Now, add some quick contents by opening the file for editing with `nano`, and adding whatever you want. Then Ctrl+x to save, you will have created a new file.
Now, add some quick contents by opening the file for editing with `nano`, and adding whatever you want. Then Ctrl+x to
save, you will have created a new file.
Type `ls` to view the contents of your directory an confirm that you did indeed make the file.
@ -117,7 +156,8 @@ Later in this tutorial, we will come back to this file and make it viewable in y
### Create a New Directory, with `mkdir`
First, hop back to your home directory with the `cd` command (remember that `cd` from anywhere in the file system will take you back to your home directory).
First, hop back to your home directory with the `cd` command (remember that `cd` from anywhere in the file system will
take you back to your home directory).
Now create a new directory called 'downloads' in your home directory:
@ -135,17 +175,21 @@ Move 'fileone.txt' into 'downloads':
> `mv fileone.txt downloads/`
Now if you `ls` the contents of your home directory, you will no longer see 'fileone.txt', because it has been moved into 'downloads'. If you 'ls' the contents of 'downloads' (a shortcut command is `ls downloads`), you will see it there.
Now if you `ls` the contents of your home directory, you will no longer see 'fileone.txt', because it has been moved
into 'downloads'. If you 'ls' the contents of 'downloads' (a shortcut command is `ls downloads`), you will see it there.
Next, copy 'filetwo.txt' into 'downloads' as follows:
> `cp filetwo.txt downloads`
Now if you `ls` the contents of your home directory, 'filetwo.txt' will still be there. This is because `cp` made a copy of 'filetwo.txt' and put the copy in 'downloads'. It did not touch the original file in your home directory. Verify this with `ls` in your home directory and in 'downloads'.
Now if you `ls` the contents of your home directory, 'filetwo.txt' will still be there. This is because `cp` made a copy
of 'filetwo.txt' and put the copy in 'downloads'. It did not touch the original file in your home directory. Verify this
with `ls` in your home directory and in 'downloads'.
### Delete Files and Directories, with `rm` and `rmdir`
As long as you're in one of your own directories (e.g. your home, or 'downloads' or 'public_html'), you can create a new files. Create a new file called 'testtrash.txt':
As long as you're in one of your own directories (e.g. your home, or 'downloads' or 'public_html'), you can create a new
files. Create a new file called 'testtrash.txt':
> `nano testtrash.txt`
@ -155,9 +199,12 @@ Now, you can delete the file with the `rm` (remove) command:
> `rm testtrash.txt`
Notice that you don't get a warning that you're about to delete it, and you don't even get a confirmation that it is deleted. You've learned your first command that you need to be careful with. If you delete an important file with `rm`, it is gone forever.
Notice that you don't get a warning that you're about to delete it, and you don't even get a confirmation that it is
deleted. You've learned your first command that you need to be careful with. If you delete an important file with `rm`,
it is gone forever.
You can delete directories the same way, only using the `rmdir` command (remove directory) instead of `rm`. If you use `mkdir testtrash`, you can then delete it as follows:
You can delete directories the same way, only using the `rmdir` command (remove directory) instead of `rm`. If you
use `mkdir testtrash`, you can then delete it as follows:
> `rmdir testtrash`
@ -167,83 +214,118 @@ If you want to delete directories that still have contents in them, use the foll
> `rm -rf directoryName`
Be very, very careful with this command. Many a user, new and seasoned, has been stung by hastily deleting directories like this. This is also the source of the classic sysadmin joke/horror story about `rm -rf /` which deletes the entire file system.
Be very, very careful with this command. Many a user, new and seasoned, has been stung by hastily deleting directories
like this. This is also the source of the classic sysadmin joke/horror story about `rm -rf /` which deletes the entire
file system.
### Downloading Files, with `wget`
Now `cd` into your 'downloads' directory because we're going to use it for actual downloads.
Use the `wget` (WWW get) command to download a text copy of this tutorial from tilde.team user cmccabe's public_html directory:
Use the `wget` (WWW get) command to download a text copy of this tutorial from tilde.team user cmccabe's public_html
directory:
> `wget https://tilde.team/~cmccabe/gnu-linux-toot.txt`
You will see output of the command that confirms it is downloading. You can also verify that it has downloaded with your `ls` command. You can also peek at the contents with the `nano` or `less` commands that you learned above.
You will see output of the command that confirms it is downloading. You can also verify that it has downloaded with
your `ls` command. You can also peek at the contents with the `nano` or `less` commands that you learned above.
If you know the URL of other files you'd like to download, you can grab those too, just swapping the URL above for any URL:
If you know the URL of other files you'd like to download, you can grab those too, just swapping the URL above for any
URL:
> `wget [URL here]`
A brief note on security here, if you do pull any scripts from the Internet using `wget`, it's important that you do not execute those scripts until you've read over what it does. Otherwise, you run the risk of compromising your account or allowing other malicious actions to take place.
A brief note on security here, if you do pull any scripts from the Internet using `wget`, it's important that you do not
execute those scripts until you've read over what it does. Otherwise, you run the risk of compromising your account or
allowing other malicious actions to take place.
### Learn More About Commands, with `man` (and `help`)
At this point, you've learned most of the commands you need for basic self-sufficiency in a GNU+Linux shell environment. With just a few more, you can go a long way. When you want to learn more about a command, you can look at its "man page" with the `man` command. "Man pages" are the instruction manuals for most commands and programs in GNU+Linux.
At this point, you've learned most of the commands you need for basic self-sufficiency in a GNU+Linux shell environment.
With just a few more, you can go a long way. When you want to learn more about a command, you can look at its "man page"
with the `man` command. "Man pages" are the instruction manuals for most commands and programs in GNU+Linux.
Try out `man` by looking at any of the commands you've learned already (except `cd`\*). For example, `man ls` would open the man page for the `ls` command. When looking at a man page, type `q` at any time to quit and return to the shell.
Try out `man` by looking at any of the commands you've learned already (except `cd`\*). For example, `man ls` would open
the man page for the `ls` command. When looking at a man page, type `q` at any time to quit and return to the shell.
The `man` command will be one of your most valuable tools for as long as you're using the GNU+Linux shell. You will always be learning new commands and new ways to use old commands, and `man` will help you do it.
The `man` command will be one of your most valuable tools for as long as you're using the GNU+Linux shell. You will
always be learning new commands and new ways to use old commands, and `man` will help you do it.
\* Note: technically speaking `cd` is a shell built-in, not a command. Make a mental note of that and you can learn more about the distinction later. For now, note that you can use `help cd` to learn more about the `cd` command.
\* Note: technically speaking `cd` is a shell built-in, not a command. Make a mental note of that and you can learn more
about the distinction later. For now, note that you can use `help cd` to learn more about the `cd` command.
## Commands have options and arguments.
When you look at the man page for a command like `ls`, you'll see in the DESCRIPTION section a number of **options** that you can use to modify how the command works. They look like `-a` or `-h` or `-l`. Try adding the `-a` option to `ls` and note the difference:
When you look at the man page for a command like `ls`, you'll see in the DESCRIPTION section a number of **options**
that you can use to modify how the command works. They look like `-a` or `-h` or `-l`. Try adding the `-a` option
to `ls` and note the difference:
> `ls -a`
The `-a` option now lists "all" contents of your directory, including "hidden" files (aka dot files). You could combine the three options listed above in the form of `ls -alh` to list "all" files, in "long" form, and display file sizes in "human" readable format. Most commands have
The `-a` option now lists "all" contents of your directory, including "hidden" files (aka dot files). You could combine
the three options listed above in the form of `ls -alh` to list "all" files, in "long" form, and display file sizes in "
human" readable format. Most commands have
Commands also have **arguments**, or information passed into a command for some kind of processing. You have already used these arguments when you told nano to open a file: `nano testtrash.txt`. In this case, "testtrash.txt" was the argument to the nano command. You also used "testtrash.txt" as an argument to the `rm` command when you did `rm testtrash.txt`.
Commands also have **arguments**, or information passed into a command for some kind of processing. You have already
used these arguments when you told nano to open a file: `nano testtrash.txt`. In this case, "testtrash.txt" was the
argument to the nano command. You also used "testtrash.txt" as an argument to the `rm` command when you
did `rm testtrash.txt`.
Commands will often combine options and arguments, sometimes in specific sequences. You can learn about these when read a command's man page.
Commands will often combine options and arguments, sometimes in specific sequences. You can learn about these when read
a command's man page.
## The Filesystem Hierarchy
You already know that you get dropped into your "home" directory when you first log in. Your home directory is just one of many, many other directories on the system. All of these directories are organized under one master directory called the "root directory". The root directory is often referred to with a single forward slash, like this: /
You already know that you get dropped into your "home" directory when you first log in. Your home directory is just one
of many, many other directories on the system. All of these directories are organized under one master directory called
the "root directory". The root directory is often referred to with a single forward slash, like this: /
You can list all the directories at the root level by using the `ls` command again, as follows:
> `ls /`
Want to check out some of the directories you see in root? You could either `cd` into them and `ls` the contents, or just `ls` the comments directly as follows:
Want to check out some of the directories you see in root? You could either `cd` into them and `ls` the contents, or
just `ls` the comments directly as follows:
> `ls /etc`
This would display the contents of the "etc" directory, which itself lives in the "root" directory. Notice that the command uses "/" + "etc" to create a path to the destination. In "etc" is another directory called "cron.d", and you can use the same principle to view its contents:
This would display the contents of the "etc" directory, which itself lives in the "root" directory. Notice that the
command uses "/" + "etc" to create a path to the destination. In "etc" is another directory called "cron.d", and you can
use the same principle to view its contents:
> `ls /etc/cron.d`
You now know enough to look around the file system. Note that most GNU+Linux systems (like tilde.team) adhere somewhat to an organization scheme called the Filesystem Hierarchy Standard ([Wikipedia link](https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard)). This is another subject for you to read up on later.
You now know enough to look around the file system. Note that most GNU+Linux systems (like tilde.team) adhere somewhat
to an organization scheme called the Filesystem Hierarchy
Standard ([Wikipedia link](https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard)). This is another subject for
you to read up on later.
## How can I keep my things private, or share them with others?
As you explore the filesystem, you might bump into some directories that won't let you in. For example, if you try to `cd` into the home directory for the root user (not the same as the root directory), you'll see this error: "/root: Permission denied". This is because GNU+Linux systems maintain a "mode" for each file that limits which users can read, write or execute it.
As you explore the filesystem, you might bump into some directories that won't let you in. For example, if you try
to `cd` into the home directory for the root user (not the same as the root directory), you'll see this error: "/root:
Permission denied". This is because GNU+Linux systems maintain a "mode" for each file that limits which users can read,
write or execute it.
If you don't own a file, then you can't change its mode. This is a basic security principle in GNU+Linux systems.
For the files you own (i.e. the files within your home directory), you can change the file modes yourself. You do this using the "change mode" command, `chmod`.
For the files you own (i.e. the files within your home directory), you can change the file modes yourself. You do this
using the "change mode" command, `chmod`.
Each file has three permission levels: for the file owner, for members of the file's group\*, and for all other system users. For each level, you can permit any combination of "read", "write", and "execute" permissions.
Each file has three permission levels: for the file owner, for members of the file's group\*, and for all other system
users. For each level, you can permit any combination of "read", "write", and "execute" permissions.
(/\* Do a web search for GNU+Linux users and groups to learn more about this important concept.)
You can change a file's mode with `chmod` one of two ways. The first is a symbolic way in which you add or subtract 'r', 'w', and/or 'x' (read, write, execute) to 'u', 'g', or 'o' (user, group, or other). For example:
You can change a file's mode with `chmod` one of two ways. The first is a symbolic way in which you add or subtract '
r', 'w', and/or 'x' (read, write, execute) to 'u', 'g', or 'o' (user, group, or other). For example:
> `chmod g+x filename.txt`
This gives 'execute' privileges to members of filename.txt's group.
You can also use `chmod` numerically, through which you may set the user, group and other permissions all at once. For example:
You can also use `chmod` numerically, through which you may set the user, group and other permissions all at once. For
example:
> `chmod 755 filename.txt`
@ -255,7 +337,8 @@ To get an interactive, visual feel for numeric file modes, try the tilde.team [f
--
Finally, remember that 'testing.html' file we made above? Let's use that as an example of how you can control who can view your files. Use the following to make the 'testing.html' file visible in your website:
Finally, remember that 'testing.html' file we made above? Let's use that as an example of how you can control who can
view your files. Use the following to make the 'testing.html' file visible in your website:
> cd ## to return you to your home directory
> `chmod 644 public_html testing.html`
@ -266,11 +349,14 @@ https://tilde.team/~username/testing.html
## The End (of The Beginning)
There you have it -- you know about logging in, using basic shell commands, and the file system, and you're now self-sustaining (and a little more).
There you have it -- you know about logging in, using basic shell commands, and the file system, and you're now
self-sustaining (and a little more).
tilde.team is about community, but it is about community of individuals who work hard to learn. what you have just leaned will give you a platform on which you can learn by doing and trying things out.
tilde.team is about community, but it is about community of individuals who work hard to learn. what you have just
leaned will give you a platform on which you can learn by doing and trying things out.
Below are some other common programs you'll likely want to use. Most of these have man pages, so you can read more about them. Others you'll just have to try out to see how they work.
Below are some other common programs you'll likely want to use. Most of these have man pages, so you can read more about
them. Others you'll just have to try out to see how they work.
## List of Common Programs
@ -298,7 +384,8 @@ Below are some other common programs you'll likely want to use. Most of these ha
`tilde` - a manager for user-submitted scripts
`webirc` - register for [thelounge](https://irc.tilde.team) webchat (in case you don't like weechat or irssi, or want to get push notifications for mentions and query messages :)
`webirc` - register for [thelounge](https://irc.tilde.team) webchat (in case you don't like weechat or irssi, or want to
get push notifications for mentions and query messages :)
`chat` - open `weechat` preconnected to our irc
@ -308,7 +395,8 @@ And in this corner, we shall describe some common activities people perform in a
## Other Intro-to-Linux Material
Not suprisingly, you'll find a lot of other intro material online or in your local library. Here are a few that have been mentioned by tilde.team members:
Not suprisingly, you'll find a lot of other intro material online or in your local library. Here are a few that have
been mentioned by tilde.team members:
Terminus - an interactive game-like introduction to shell commands
http://www.mprat.org/Terminus/

View File

@ -3,79 +3,82 @@ author: ~ben
published: true
title: code of conduct
description: tilde.team code of conduct
category:
- main
category:
- beginners
- about
---
> **tl;dr** learn by doing and helping. be excellent to each other. have fun!
## 1. purpose
a primary goal of tilde.team is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. as such, we are committed to providing a friendly, safe and welcoming environment for all.
a primary goal of tilde.team is to be inclusive to the largest number of contributors, with the most varied and diverse
backgrounds possible. as such, we are committed to providing a friendly, safe and welcoming environment for all.
this code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
this code of conduct outlines our expectations for all those who participate in our community, as well as the
consequences for unacceptable behavior.
we invite all those who participate in tilde.team to help us create safe and positive experiences for everyone.
## 2. tilde.team mission
[full goals/roadmap document](https://tilde.team/wiki/goals-roadmap)
**tilde.team exists to foster an engaged community for socializing, learning, and making cool stuff**
in a mass-media age, it is up to small, intentional communities to gather and work together to provide a space outside of the advertising-laden, profit-seeking, corporate-owned world of social media.
to that end, tilde.team strives to be a radically inclusive community where people of all backgrounds and all technological experience levels can come together to learn, to teach, and to delight in one another's creations.
in a mass-media age, it is up to small, intentional communities to gather and work together to provide a space outside
of the advertising-laden, profit-seeking, corporate-owned world of social media.
to that end, tilde.team strives to be a radically inclusive community where people of all backgrounds and all
technological experience levels can come together to learn, to teach, and to delight in one another's creations.
## 3. expected behavior
the following behaviors are expected and requested of all community members:
* participate in an authentic and active way. in doing so, you contribute to the health and longevity of this community.
* exercise consideration and respect in your speech and actions.
* attempt collaboration before conflict.
* refrain from demeaning, discriminatory, or harassing behavior and speech.
* be mindful of your surroundings and of your fellow participants.
* teach when people need help. don't do it for them.
* participate in an authentic and active way. in doing so, you contribute to the health and longevity of this community.
* exercise consideration and respect in your speech and actions.
* attempt collaboration before conflict.
* refrain from demeaning, discriminatory, or harassing behavior and speech.
* be mindful of your surroundings and of your fellow participants.
* teach when people need help. don't do it for them.
## 4. unacceptable behavior
the following behaviors are considered harassment and are unacceptable within our community:
* violence, threats of violence or violent language directed against another person.
* sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
* posting or displaying sexually explicit or violent material.
* posting or threatening to post other people's personally identifying information ("doxing").
* personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
* unwelcome sexual attention. this includes sexualized comments or jokes.
* deliberate intimidation, stalking or following.
* attempting to disrupt the normal operation of tilde.team (colloquially "hacking the Gibson"). if you think something's insecure and want to poke at it, tell us first.
* violence, threats of violence or violent language directed against another person.
* sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
* posting or displaying sexually explicit or violent material.
* posting or threatening to post other people's personally identifying information ("doxing").
* personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
* unwelcome sexual attention. this includes sexualized comments or jokes.
* deliberate intimidation, stalking or following.
* attempting to disrupt the normal operation of tilde.team (colloquially "hacking the Gibson"). if you think something's
insecure and want to poke at it, tell us first.
## 5. consequences of unacceptable behavior
unacceptable behavior from any community member, including sponsors and those with decision-making authority (sudo), will not be tolerated.
unacceptable behavior from any community member, including sponsors and those with decision-making authority (sudo),
will not be tolerated.
anyone asked to stop unacceptable behavior is expected to comply immediately.
if a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from tilde.team without warning (meaning your account will be terminated and all user data deleted).
if a community member engages in unacceptable behavior, the community organizers may take any action they deem
appropriate, up to and including a temporary ban or permanent expulsion from tilde.team without warning (meaning your
account will be terminated and all user data deleted).
## 6. reporting guidelines
if you are subject to or witness unacceptable behavior, or have any other concerns, please contact an admin (see info below).
if you are subject to or witness unacceptable behavior, or have any other concerns, please contact an admin (see info
below).
additionally, help engaging with law enforcement is available.
## 7. addressing grievances
if you feel you have been falsely or unfairly accused of violating this code of conduct, use the contact info below to send a concise description of your grievance.
if you feel you have been falsely or unfairly accused of violating this code of conduct, use the contact info below to
send a concise description of your grievance.
## 8. scope
@ -84,28 +87,27 @@ we expect all tilde.team members to abide by this code of conduct while:
* engaging with other members
* publishing content on tilde.team
## 9. contact info
tilde.team admins:
you can also send a mail to [sudoers@tilde.team](mailto:sudoers@tilde.team) to make sure we all get it.
* [ben](https://tilde.team/~ben/):
- [ben@tilde.team](mailto:ben@tilde.team)
- on irc `/query ben hello`
* [ben](https://tilde.team/~ben/):
- [ben@tilde.team](mailto:ben@tilde.team)
- on irc `/query ben hello`
* [khuxkm](https://tilde.team/~khuxkm/):
- [khuxkm@tilde.team](mailto:khuxkm@tilde.team)
- on irc `/query khuxkm hello`
- [khuxkm@tilde.team](mailto:khuxkm@tilde.team)
- on irc `/query khuxkm hello`
* [cmccabe](https://tilde.team/~cmccabe/):
- [cmccabe@tilde.team](mailto:cmccabe@tilde.team)
- on irc `/query cmccabe hello`
- [cmccabe@tilde.team](mailto:cmccabe@tilde.team)
- on irc `/query cmccabe hello`
## 10. license and attribution
this code of conduct is based on [citizencodeofconduct.org](http://citizencodeofconduct.org/) and [tilde.town coc](http://tilde.town/wiki/conduct.html) under the terms of the [creative commons attribution-sharealike license](http://creativecommons.org/licenses/by-sa/3.0/).
this code of conduct is based on [citizencodeofconduct.org](http://citizencodeofconduct.org/)
and [tilde.town coc](http://tilde.town/wiki/conduct.html) under the terms of
the [creative commons attribution-sharealike license](http://creativecommons.org/licenses/by-sa/3.0/).
## 11. terms of service

View File

@ -3,15 +3,15 @@ author: ~ben
published: true
title: disk usage tools and guidelines
description: tips and tricks for keeping track of your disk usage on tilde.team and elsewhere
category:
- main
category:
- about
- guidelines
---
files tend to keep growing and growing until you run out of disk space all of a sudden.
let's take a look at some tools to keep an eye on disk usage.
## tilde.team guidelines
even though we have plenty of disk space to go around on tilde.team,
@ -38,7 +38,6 @@ for a short period of time so we can adjust your quota temporarily.
run `quota` to see your current usage and grace period (if you're over).
add `-s` to print using friendlier units.
### du
`du` (short for `d`isk `u`sage) is the go-to tool.
@ -52,15 +51,14 @@ common switches include:
example:
to see the disk usage of the current directory, run:
du -sh
du -sh
check the manpage for more information and additional switches
### ncdu
`ncdu` (short for `nc`urses `d`isk `u`sage) is extremely useful for visualizing
disk usage.
disk usage.
call `ncdu` with no args to recurse starting in the current directory or
pass a dir name to start there
@ -71,7 +69,6 @@ space.
press `?` to see additional keybinds once you've started it up. you can change
the sort order, open a shell, and delete files without closing the program.
### df
`df` (short for `d`isk `f`ree) lists mounted disks with usage, free space,

View File

@ -3,11 +3,13 @@ author: ~ben
published: true
title: domains
description: domains associated with tilde.team
category:
- main
category:
- about
- services
---
because [~ben](https://tilde.team/~ben/) hoards domain names, the following domains are associated with tilde.team and/or the tildeverse somehow:
because [~ben](https://tilde.team/~ben/) hoards domain names, the following domains are associated with tilde.team
and/or the tildeverse somehow:
* [fuckup.club](http://fuckup.club) - alias
* [nand.sh](https://nand.sh/) - alias
@ -27,4 +29,5 @@ because [~ben](https://tilde.team/~ben/) hoards domain names, the following doma
aliases can be used as-is, where redirects will simply change to a tilde.team url.
note that redirects do not have ssl certs. if you have a cool project that could use one of the not sure or redirect domains, let me know.
note that redirects do not have ssl certs. if you have a cool project that could use one of the not sure or redirect
domains, let me know.

View File

@ -4,7 +4,8 @@ published: true
title: email
description: email settings for tilde.team
category:
- main
- services
- guides
---
tilde.team has a mailserver. here are your options:
@ -15,52 +16,56 @@ tilde.team has a mailserver. here are your options:
- alpine - should work out of the box
- [webmail](https://mail.tilde.team)
- imap/smtp
- some clients will autoconfigure (tested with thunderbird)
- email address: username@tilde.team (or any of the aliased [domains](domains))
- username: username (without the domain)
- password: your shell password
- port info:
- imap: imap.tilde.team port 143 (starttls)
- imaps: imap.tilde.team port 993 (tls)
- pop3: pop3.tilde.team port 995 (tls)
- smtp: smtp.tilde.team port 587 (starttls)
- smtps: smtp.tilde.team port 465 (tls)
- some clients will autoconfigure (tested with thunderbird)
- email address: username@tilde.team (or any of the aliased [domains](domains))
- username: username (without the domain)
- password: your shell password
#### connection info
| protocol | hostname | port | security |
|----------|-----------------|------|----------|
| imap | mail.tilde.team | 143 | starttls |
| imaps | mail.tilde.team | 993 | tls |
| pop3s | mail.tilde.team | 995 | tls |
| smtp | mail.tilde.team | 578 | starttls |
| smtps | mail.tilde.team | 465 | tls |
### alternate domains and addresses
because [~ben](https://tilde.team/~ben/) hoards domain names, you can
because [~ben](https://tilde.team/~ben/) hoards domain names, you can
use any of the [domains on this list](domains) with your tildemail:
mail sent to yourusername@ any of those domains will end up in your
mail sent to yourusername@ any of those domains will end up in your
inbox. most clients will allow you to add additional identities/aliases.
additionally, any address with a `+` and arbitrary text behind it
additionally, any address with a `+` and arbitrary text behind it
will be forwarded to your email: ie. `yourusername+somethingcool@tildeteam.org`.
plus-addresses are very useful for filtering mail.
### forwarding and sieve
if you would like your tildemail to be forwarded somewhere else, put that
if you would like your tildemail to be forwarded somewhere else, put that
email address in a file called `~/.forward`
```bash
echo myotheraddress@example.com > ~/.forward
```
we also have [sieve](http://sieve.info) and
we also have [sieve](http://sieve.info) and
[managesieve](https://wiki1.dovecot.org/ManageSieve) support.
scripts belong in `~/sieve/`, with the active sieve script
scripts belong in `~/sieve/`, with the active sieve script
named `~/.dovecot.sieve` (to conform with managesieve).
here are some [example sieve scripts](
https://wiki.dovecot.org/Pigeonhole/Sieve/Examples)
managesieve is available on the default port (4190) if you want
managesieve is available on the default port (4190) if you want
to use an external managesieve client (like the [thunderbird add-on](
https://github.com/thsmi/sieve)).
[our webmail](https://mail.tilde.team/#/settings/filters) is pre-configured
[our webmail](https://mail.tilde.team/#/settings/filters) is pre-configured
to manage your sieve scripts.
---

View File

@ -4,14 +4,21 @@ published: false
title: finger
description: finger as a social network
category:
- main
- publishing
- services
- guides
---
the [finger protocol](https://en.wikipedia.org/wiki/Finger_protocol) was created way back in 1977. its purpose was to display information about the queried user of a system, or all the users of a system.
the [finger protocol](https://en.wikipedia.org/wiki/Finger_protocol) was created way back in 1977. its purpose was to
display information about the queried user of a system, or all the users of a system.
it fell out of use in the 1990s due to various security concerns. the old finger daemons were buggy and easily exploited, while the information garnered from a query could be used for social engineering attacks. nowadays, the finger daemons have been refined and are no longer so vulnerable.
it fell out of use in the 1990s due to various security concerns. the old finger daemons were buggy and easily
exploited, while the information garnered from a query could be used for social engineering attacks. nowadays, the
finger daemons have been refined and are no longer so vulnerable.
in the post-facebook world, new types of social networks are popping up. the latest in this movement is a resurgence of the finger protocol. what follows is a rough guide for getting yourself up to speed with finger on [tilde.team](https://tilde.team).
in the post-facebook world, new types of social networks are popping up. the latest in this movement is a resurgence of
the finger protocol. what follows is a rough guide for getting yourself up to speed with finger
on [tilde.team](https://tilde.team).
## tilde.team specifics
@ -27,7 +34,8 @@ the standard query for finger is simply
finger user@host
```
which displays login name, home directory, shell, real name, current login time, idle time, whether or not the user has mail, and the contents of the user's ~/.plan file. Here is an example of the output:
which displays login name, home directory, shell, real name, current login time, idle time, whether or not the user has
mail, and the contents of the user's ~/.plan file. Here is an example of the output:
```
Login: username Name: Bob Bobson XXII
@ -42,10 +50,14 @@ hey hey hey everybody!
## .plan
The ~/.plan file displayed at the end of the finger query response allows for some customization. You can put literally any text you want there. Status updates, summaries, etc. This little file allows us to use finger as a rudimentary social network.
The ~/.plan file displayed at the end of the finger query response allows for some customization. You can put literally
any text you want there. Status updates, summaries, etc. This little file allows us to use finger as a rudimentary
social network.
For example, say you want to use it as a personal summary, like having a blurb about what you're working on. Place the statement into ~/.plan and you're ready to go!
For example, say you want to use it as a personal summary, like having a blurb about what you're working on. Place the
statement into ~/.plan and you're ready to go!
For a more traditional social network style format, put dated and timed status updates as if you're tooting on a mastodon instance. The sky's the limit! Well, actually, text is the limit. But you get the idea. Right?
For a more traditional social network style format, put dated and timed status updates as if you're tooting on a
mastodon instance. The sky's the limit! Well, actually, text is the limit. But you get the idea. Right?
hope to see you on finger soon!

View File

@ -4,7 +4,9 @@ published: true
title: gemini cgi guide
description: a guide to using CGI on gemini
category:
- main
- publishing
- guides
- technical
---
## where to put CGI scripts

View File

@ -4,7 +4,9 @@ published: true
title: gemini
description: gemini hosting on tilde.team
category:
- main
- publishing
- services
- guides
---
tilde.team offers gemini hosting!

View File

@ -4,10 +4,13 @@ published: true
title: getting started
description: tilde.team getting started guide
category:
- main
- beginners
- technical
- guides
---
this guide is not very thorough or complete. if you want something nicer, try [our cli for beginners article](cli-for-beginners).
this guide is not very thorough or complete. if you want something nicer,
try [our cli for beginners article](cli-for-beginners).
---
@ -34,12 +37,12 @@ New to the command line and all this webby cowfoolery? You're in luck! Here's a
- `ssh your_username@tilde.team`
- Enter your ssh key passphrase (if you set one).
### Legacy Windows
- [git bash](https://gitforwindows.org) included with a standard git install
- [msys2](https://msys2.github.io) is quite nice and has support for [mosh](https://mosh.org)
- another option is to use [WSL (windows subsystem for linux)](https://docs.microsoft.com/en-us/windows/wsl/install-win10)
- another option is to
use [WSL (windows subsystem for linux)](https://docs.microsoft.com/en-us/windows/wsl/install-win10)
### Linux
@ -49,7 +52,8 @@ New to the command line and all this webby cowfoolery? You're in luck! Here's a
### MacOS
- Browse to Applications/Utilities/Terminal and launch Terminal (or press cmd+space, start typing Terminal, and press return)
- Browse to Applications/Utilities/Terminal and launch Terminal (or press cmd+space, start typing Terminal, and press
return)
- `ssh your_username@tilde.team`
- Enter your ssh key passphrase (if you set one).

View File

@ -3,64 +3,65 @@ author: ~ben
published: false
title: goals and roadmap
description: tilde.team roadmap and goals list
category:
- main
category:
- about
---
[living draft of this document](https://pad.tildeverse.org/code/#/2/code/edit/RFBUqXec+9+MlZzx4mnhU3ps/)
these ideas are partly about building one system (in this case, tilde.team) but also about supporting a
these ideas are partly about building one system (in this case, tilde.team) but also about supporting a
broader ecosystem of interconnected systems.
1. develop a clear system identity as an alternative social environment for the technically-inclined;
specifically, serving as a non-commercial alternative to the mainstream, corporate-owned media and social media.
the dual points of (1) an alternative social/communications medium and (2) technically inclined user base are
important because, together, they put the users in the role of protecting (and enjoying!) the tools of
communication that are currently being neutered by corporate commodification of the www.
1. develop a clear system identity as an alternative social environment for the technically-inclined;
specifically, serving as a non-commercial alternative to the mainstream, corporate-owned media and social media.
the dual points of (1) an alternative social/communications medium and (2) technically inclined user base are
important because, together, they put the users in the role of protecting (and enjoying!) the tools of
communication that are currently being neutered by corporate commodification of the www.
2. related to #1, focus on cultivating a technically-inclined user base that is aware of the societal value of
non-commercial, alternative communication and social media. (not all users have to be code wizards, but it's safe
to assume that the very premise of a command-line platform will weed out pure-GUI people.)
2. related to #1, focus on cultivating a technically-inclined user base that is aware of the societal value of
non-commercial, alternative communication and social media. (not all users have to be code wizards, but it's safe
to assume that the very premise of a command-line platform will weed out pure-GUI people.)
3. provide tools, resources and encouragement for users to develop ideas and best practices for the next
generation of public access unix systems (in this case, in the form of a tilde box [1]). the "next generation" is
always ahead of the present, so this implies that the system is in a constant state of development and
self-improvement, with a continually rolling set of goals, and regular testing and evaluation of experimental
projects. --all of which is powered by user involvement in a brainstorming/experimenting/teaching/learning/doing
model.
3. provide tools, resources and encouragement for users to develop ideas and best practices for the next
generation of public access unix systems (in this case, in the form of a tilde box [1]). the "next generation" is
always ahead of the present, so this implies that the system is in a constant state of development and
self-improvement, with a continually rolling set of goals, and regular testing and evaluation of experimental
projects. --all of which is powered by user involvement in a brainstorming/experimenting/teaching/learning/doing
model.
4. related to #3, really emphasize that learning through doing is a core theme of the system.
5. serve partly as a meta-community among other tildes and pubnixes, both spreading best practices to them and
learning from experiences from them.
5. serve partly as a meta-community among other tildes and pubnixes, both spreading best practices to them and
learning from experiences from them.
6. through this development (#5) of interconnections among similar communities, develop trusted individual-based
communication networks among many similar systems. here's where that federation concept comes in, possibly
allowing people to have a 'home' system, and to use those credentials to visit other systems as well.
6. through this development (#5) of interconnections among similar communities, develop trusted individual-based
communication networks among many similar systems. here's where that federation concept comes in, possibly
allowing people to have a 'home' system, and to use those credentials to visit other systems as well.
7. last but absolutely not least --> MAKE IT FUN! it should not be a bitter place to sulk or rant about the
mainstream. it should be a social environment in which users can go wild and push their creative skills to the
limit. it should be a place to appreciate what does not exist on facebook and other exploitative commercial
environments.
mainstream. it should be a social environment in which users can go wild and push their creative skills to the
limit. it should be a place to appreciate what does not exist on facebook and other exploitative commercial
environments.
8. idea mill:
* if software development is a main activity to be encouraged among the users, provide a forum for saying "here's an idea; who wants to develop it?"
* this could happen somewhere on the [forum](https://forum.tilde.team) (which would also need some love from the devs)
* this would allow people to find co-developers, or to allow non-devs to give devs good ideas.
* if software development is a main activity to be encouraged among the users, provide a forum for saying "here's an
idea; who wants to develop it?"
* this could happen somewhere on the [forum](https://forum.tilde.team) (which would also need some love from the
devs)
* this would allow people to find co-developers, or to allow non-devs to give devs good ideas.
## future plans
* ldap auth
* nextcloud?
* onlyoffice
* mumble/teamspeak
* nextcloud?
* onlyoffice
* mumble/teamspeak
* ~ben shouldn't be the single point of failure. need a way to pass command to another admin if i go MIA.
## to do
* come up with a community charter
* terms of use
* terms of use
* aup
* better documentation

View File

@ -4,7 +4,9 @@ published: true
title: gopher
description: gopher server and proxy
category:
- main
- guides
- services
- publishing
---
the [gopher protocol](http://en.wikipedia.org/wiki/Gopher_(protocol)) was

View File

@ -3,16 +3,19 @@ author: ~ben
published: true
title: irc
description: irc information
category:
- main
category:
- guides
- technical
- beginners
---
hi teammates!
the tilde.chat irc network is available publicly at irc.tilde.chat:6697 (with ssl) as a round robin of
the tilde.chat irc network is available publicly at irc.tilde.chat:6697 (with ssl) as a round robin of
[available nodes](https://tilde.chat/wiki/servers).
to connect directly to our node, you can use the following addresses:
- localhost port 6667 when at your shell or via ssh port-forwarding
- team.tilde.chat port 6697 with ssl
@ -37,13 +40,13 @@ location (`~/.weechat/relay_socket`). to get started using it, follow these step
1. in weechat:
* `/relay add unix.weechat %h/relay_socket`
* `/set relay.network.password mysupersecretpassword` - don't use this password
of course. note that you might already have this set.
of course. note that you might already have this set.
2. at your shell:
* `chmod o+rw ~/.weechat/relay_socket` - note that other members of the team group
are not included in the granted permissions. this allows nginx to connect
to your socket on your behalf. you will need to do this every time you start
weechat as the socket doesn't exist until weechat starts up.
are not included in the granted permissions. this allows nginx to connect
to your socket on your behalf. you will need to do this every time you start
weechat as the socket doesn't exist until weechat starts up.
3. in your relay client:
* glowing-bear:
@ -57,11 +60,12 @@ location (`~/.weechat/relay_socket`). to get started using it, follow these step
- relay host: $user.ttm.sh
- relay port: 443
- your relay password
- (if you get "Error: Could not connect using WebSocket", check to be sure
~/ and ~/.weechat have at least o+rx permissions so nginx can reach
~/.weechat/relay_socket)
## znc
- (if you get "Error: Could not connect using WebSocket", check to be sure
~/ and ~/.weechat have at least o+rx permissions so nginx can reach
~/.weechat/relay_socket)
## znc
the system znc authenticates using your shell password (same as with email and
[nextcloud](https://cloud.tilde.team)). reach out to an admin on irc or

View File

@ -3,13 +3,15 @@ author: ~cmccabe
published: true
title: learning opportunities
description: a list of code challenges, internships, and other resources to support learning by tilde.team members
category: education
- main
category: education
- guides
- beginners
---
## Coding Challenge Websites
There are many coding challenge websites on the Internet today. below are a few of them. the tilde.team shell is a great place to work on solutions to the challenges.
There are many coding challenge websites on the Internet today. below are a few of them. the tilde.team shell is a great
place to work on solutions to the challenges.
Please, just be mindful of efficient coding practices while working on these.
@ -28,7 +30,7 @@ These challenges focus primarily on practicing various computer security princip
## Internships and Other Developmental Opportunities
### Formlabs
### Formlabs
* [https://formlabs.com/company/careers/job/82446/apply/](https://formlabs.com/company/careers/job/82446/apply/)
@ -36,4 +38,5 @@ These challenges focus primarily on practicing various computer security princip
## This Page Is Built Based On Your Input!
If you know of other internships, opportunities, or other (good) code challenge sites, submit a pull request for this page, or mention it to an admin on IRC.
If you know of other internships, opportunities, or other (good) code challenge sites, submit a pull request for this
page, or mention it to an admin on IRC.

View File

@ -4,7 +4,8 @@ published: true
title: lua
description: set up tools to write lua code
category:
- main
- guides
- tecnical
---
This page will explain how to set up your tilde.team account for

View File

@ -4,21 +4,22 @@ published: true
title: mailing list netiquette
description: tildeverse mailing lists etiquette guide
category:
- main
- beginners
- guidelines
---
the tildeverse has now its own mailing list service. you can take a look at:
[lists.tildeverse.org](https://lists.tildeverse.org/)
this is a description of the basic *netiquette* rules for this service. most of
the text is taken shamelessly from
the text is taken shamelessly from
[man.sr.ht/lists.sr.ht/etiquette.md](https://man.sr.ht/lists.sr.ht/etiquette.md)
with some adaptations and a couple more suggestions taken from other lists out
there.
some email clients have popularized email usage patterns which are considered
poor form on many mailing lists. please review some of our suggestions for
participating more smoothly in discussions on the tildeverse. this advice will
participating more smoothly in discussions on the tildeverse. this advice will
likely serve you well outside the tildeverse as well.
if you have any troubles following these guides or don't know how to configure
@ -42,7 +43,7 @@ some email clients will paste the entire email you're replying to into your
response and encourage you to write your message over it. this behavior is
called "top posting" and is discouraged on the tildeverse lists (or on any
mailing list really). instead, cut out any parts of the reply that you're not
directly responding to and write your comments inline. feel free to edit the
directly responding to and write your comments inline. feel free to edit the
original message as much as you like. in other words, keep the relevant context
for your reply and delete the rest. this makes cleaner emails that are easier to
read, even if the reader jumps in the middle of a thread.
@ -79,7 +80,7 @@ You might respond with:
please wrap lines in your email at 72 columns. many people use email readers
designed to faithfully display plain text and won't break lines at a width which
is comfortable for reading, or won't break lines at all, which is useful when
reviewing patches. some readers also have many things open in addition to their
reviewing patches. some readers also have many things open in addition to their
mail client, and may not allocate as much screen real-estate to email as you do.
if you're curious about why this arbitrary column count. "regular" terminals
@ -99,7 +100,7 @@ inline signature. look in your local pgp implementation's documentation for
try not to send attachment to the list or, if you do it, make sure they are
small files. think about people with bad internet connection or limited
resources. it's better to send a link to download whatever you want to share.
resources. it's better to send a link to download whatever you want to share.
if you send links, it's a good practice to describe the content and the size,
so the reader can choose to download it or not before following the link. for
example, you can upload a file to [ttm.sh](https://ttm.sh) or drop it in your

View File

@ -3,42 +3,42 @@ author: ~ben
published: true
title: tilde.team manifesto
description: tilde.team manifesto
category:
- main
category:
- beginners
- about
---
> tilde.team is a shared system that provides an inclusive, non-commercial space
> tilde.team is a shared system that provides an inclusive, non-commercial space
> for teaching, learning, practicing and enjoying the social medium of unix.
here are some of our most important values:
1. tilde.team is an alternative social environment for the technically-inclined;
specifically, a non-commercial alternative to the mainstream, corporate-owned
media and social media. we aim to put the users in control of the tools of
communication that are currently being neutered by corporate commodification
of the www.
1. tilde.team is an alternative social environment for the technically-inclined;
specifically, a non-commercial alternative to the mainstream, corporate-owned
media and social media. we aim to put the users in control of the tools of
communication that are currently being neutered by corporate commodification
of the www.
2. provide tools, resources and encouragement for users to develop ideas and
best practices for the next generation of public access unix systems. the
"next generation" is always ahead of the present, so this implies that the
system is in a constant state of development and self-improvement, with a
continually rolling set of goals, and regular testing and evaluation of
experimental projects. --all of which is powered by user involvement in a
brainstorming/experimenting/teaching/learning/doing model.
2. provide tools, resources and encouragement for users to develop ideas and
best practices for the next generation of public access unix systems. the
"next generation" is always ahead of the present, so this implies that the
system is in a constant state of development and self-improvement, with a
continually rolling set of goals, and regular testing and evaluation of
experimental projects. --all of which is powered by user involvement in a
brainstorming/experimenting/teaching/learning/doing model.
3. serve partly as a meta-community among other tildes and pubnixes, both
sharing best practices and learning from their experiences.
4. last but absolutely not least --> MAKE IT FUN! it should not be a bitter
place to sulk or rant about mainstream culture. it should be a social
environment in which users can go wild and push their creative skills to the
limit. it should be a place to appreciate what does not exist in other
exploitative commercial environments.
3. serve partly as a meta-community among other tildes and pubnixes, both
sharing best practices and learning from their experiences.
4. last but absolutely not least --> MAKE IT FUN! it should not be a bitter
place to sulk or rant about mainstream culture. it should be a social
environment in which users can go wild and push their creative skills to the
limit. it should be a place to appreciate what does not exist in other
exploitative commercial environments.
---
this document is still a work in progress. if you have any ideas or
this document is still a work in progress. if you have any ideas or
suggestions, [send a pr](https://tildegit.org/team/site/src/branch/master/wiki/pages/manifesto.md)!
[living draft of this document here](https://pad.tilde.team/code/#/2/code/edit/RFBUqXec+9+MlZzx4mnhU3ps/)

View File

@ -4,7 +4,8 @@ published: true
title: other tildes
description: an up-to-date list of other tildes
category:
- main
- about
- tildeverse
---
if you're starting a tilde and want to be added to this list, [open a PR :)](

View File

@ -4,7 +4,8 @@ published: true
title: privacy policy
description: tilde.team privacy policy
category:
- main
- beginners
- about
---
tilde.team takes privacy seriously and, as such, remains committed to being in

View File

@ -4,7 +4,9 @@ published: true
title: hosting public git repos
description: hosting public git repos on tilde.team
category:
- main
- publishing
- technical
- guides
---
Besides the [Gitea instance][1] of tildeverse, you could easily set up a

View File

@ -4,16 +4,19 @@ published: true
title: services
description: tilde.team services list
category:
- main
- services
- tildeverse
---
i'll keep this wiki page updated with the services that we run and maintain :)
as a founding member of the [tildeverse](https://tildeverse.org), tilde.team hosts a number of services for the tildeverse to share.
as a founding member of the [tildeverse](https://tildeverse.org), tilde.team hosts a number of services for the
tildeverse to share.
### our deployed projects
- [forum](https://forum.tilde.team) ([source](https://tildegit.org/team/forum)) - mostly defunct in favor of [bbj](https://bbj.tildeverse.org)
- [forum](https://forum.tilde.team) ([source](https://tildegit.org/team/forum)) - mostly defunct in favor
of [bbj](https://bbj.tildeverse.org)
### code related stuff
@ -22,14 +25,14 @@ as a founding member of the [tildeverse](https://tildeverse.org), tilde.team hos
### general utilities
- [cryptpad](https://pad.tildeverse.org)
- [cryptdrive](https://pad.tildeverse.org/drive/)
- [markdown/code editor](https://pad.tildeverse.org/code/)
- [presentation slides editor](https://pad.tildeverse.org/slides/)
- [polls](https://pad.tildeverse.org/poll/)
- [kanban boards](https://pad.tildeverse.org/kanban/)
- [whiteboard](https://pad.tildeverse.org/whiteboard/)
- [file drop](https://pad.tildeverse.org/file/)
- [todo lists](https://pad.tildeverse.org/todo/)
- [cryptdrive](https://pad.tildeverse.org/drive/)
- [markdown/code editor](https://pad.tildeverse.org/code/)
- [presentation slides editor](https://pad.tildeverse.org/slides/)
- [polls](https://pad.tildeverse.org/poll/)
- [kanban boards](https://pad.tildeverse.org/kanban/)
- [whiteboard](https://pad.tildeverse.org/whiteboard/)
- [file drop](https://pad.tildeverse.org/file/)
- [todo lists](https://pad.tildeverse.org/todo/)
- [nextcloud](https://cloud.tilde.team/) - 250mb limit: log in with your shell password
- [paste bin](https://paste.tildeverse.org)
- [nullpointer fileshare](https://ttm.sh)
@ -40,16 +43,17 @@ as a founding member of the [tildeverse](https://tildeverse.org), tilde.team hos
- [tilde.news](https://tilde.news) - [lobste.rs](https://lobste.rs) sister site for tilde-related links
- [irc](https://tilde.chat) tilde.chat irc network for the tildeverse
- we host one node of the [network](https://tilde.chat/wiki/servers)
- we host [quotes.tilde.chat](https://quotes.tilde.chat)
- [znc bouncer](https://znc.tilde.team/) - log in with your shell password
- we host one node of the [network](https://tilde.chat/wiki/servers)
- we host [quotes.tilde.chat](https://quotes.tilde.chat)
- [znc bouncer](https://znc.tilde.team/) - log in with your shell password
- [xmpp](xmpp) federated chat network
- [pleroma](https://pleroma.tilde.zone) federated social network
- [mastodon](https://tilde.zone) federated social network
- [pinafore front-end](https://pinafore.tilde.zone)
- [halcyon front-end](https://halcyon.tilde.zone)
- [pinafore front-end](https://pinafore.tilde.zone)
- [halcyon front-end](https://halcyon.tilde.zone)
- [email](email) ([webmail](https://mail.tilde.team), smtp/imap, mutt, and alpine)
- [mailing lists](https://lists.tildeverse.org) - hosted on top of our mailserver
- [mailing lists](https://lists.tildeverse.org) - hosted on top of our mailserver
- tildeverse nntp accessible via news.tilde.team port 119 (read-only, for write access, you need to ssh inside)
- [bbj](https://tildegit.org/bbj/bbj) ([web mirror here](https://bbj.tildeverse.org)) - forked from [desvox/bbj](https://github.com/bbj-dev/bbj)
- [bbj](https://tildegit.org/bbj/bbj) ([web mirror here](https://bbj.tildeverse.org)) - forked
from [desvox/bbj](https://github.com/bbj-dev/bbj)
- [gopher proxy](https://gopher.tilde.team) - defaults to our local gopherd: gopher://tilde.team

View File

@ -4,7 +4,8 @@ published: true
title: spartan
description: spartan hosting on tilde.team
category:
- main
- publishing
- services
---
tilde.team offers spartan hosting!
@ -35,4 +36,5 @@ here's a simple example in sh
only the first line of the file MUST send `\r\n`
see you in... the Spartan-verse? Laconia? we haven't come up with a name, but feel free to stop by #spartan on irc to discuss!
see you in... the Spartan-verse? Laconia? we haven't come up with a name, but feel free to stop by #spartan on irc to
discuss!

View File

@ -4,7 +4,9 @@ published: true
title: ssh
description: ssh tutorial and background info
category:
- main
- beginners
- technical
- guides
---
_or, how to tell other computers to do cool things_
@ -12,9 +14,9 @@ _or, how to tell other computers to do cool things_
---
> all users are required to use an ssh keypair for login, or will be required
to proceed with manual account recovery with [~ben](/~ben/) or another admin.
drop a line to [sudoers@tilde.team](mailto:sudoers@tilde.team) or hop on
[irc](https://kiwi.tilde.chat/#team) for assistance.
> to proceed with manual account recovery with [~ben](/~ben/) or another admin.
> drop a line to [sudoers@tilde.team](mailto:sudoers@tilde.team) or hop on
[irc](https://tilde.chat/kiwi/#team) for assistance.
## tilde.team details
@ -83,8 +85,8 @@ be hacked) and for me, your humble sysadmin (less administration than passwords)
## how to make an ssh key
SSH supports a handful of types of cryptographic keys. The most used are [RSA](
<https://en.wikipedia.org/wiki/RSA_(cryptosystem)>) and the more modern [Ed25519](
https://en.wikipedia.org/wiki/EdDSA#Ed25519).
<https://en.wikipedia.org/wiki/RSA_(cryptosystem)>) and the more modern [Ed25519](
https://en.wikipedia.org/wiki/EdDSA#Ed25519).
RSA is the de-facto standard and is supported everywhere (just choose a big
enough key like 4096 bits to be secure). Ed25519 is designed to be faster and
@ -98,7 +100,7 @@ Keep in mind that these instructions leave your private keys unencrypted in
your local hard disk. So keep them private; never share them. A good solution
is to provide a password for them at creation time, but this implies entering
a password any time you used them (impractical) or use something like [ssh-agent](
https://man.openbsd.org/ssh-agent.1) (a bit more complex)
https://man.openbsd.org/ssh-agent.1) (a bit more complex)
We don't have documentation for this [(yet)](https://tildegit.org/team/site/src/branch/master/wiki)
so either go with no password keys, or ask on IRC ([#team](https://web.tilde.chat/?join=team)) for help.
@ -126,12 +128,12 @@ ssh-keygen -t ed25519 -a 100
```
1. if you press enter to accept the defaults, your public and private key will
be located at `~/.ssh/id_ed25519.pub` and `~/.ssh/id_ed25519` respectively
be located at `~/.ssh/id_ed25519.pub` and `~/.ssh/id_ed25519` respectively
1. `cat ~/.ssh/id_ed25519.pub`
1. copy the output of the last command and paste it in the sshkey field on the
signup form (or email it to [~sudoers](mailto:sudoers@tilde.team) if you already have an account)
signup form (or email it to [~sudoers](mailto:sudoers@tilde.team) if you already have an account)
#### using your keypair
@ -153,7 +155,9 @@ where username is your username (~ben would use `ssh ben@tilde.team`)
### windows 10
windows 10 1809 or later has openssh built in, so you no longer need to install third-party tools. if openssh is not enabled, please see microsoft's documentation on [openssh in windows](https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_overview).
windows 10 1809 or later has openssh built in, so you no longer need to install third-party tools. if openssh is not
enabled, please see microsoft's documentation
on [openssh in windows](https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_overview).
#### generating your keypair
@ -172,8 +176,8 @@ ssh-keygen -t ed25519 -a 100
```
1. if you press enter to accept the defaults, your public and private key will
be located at `%UserProfile%\.ssh\id_ed25519.pub` and `%UserProfile%\.ssh\id_ed25519`
respectively
be located at `%UserProfile%\.ssh\id_ed25519.pub` and `%UserProfile%\.ssh\id_ed25519`
respectively
1. `type %UserProfile%\.ssh\id_ed25519.pub`
@ -199,7 +203,8 @@ where username is your username (~ben would use `ssh ben@tilde.team`)
### legacy windows
older versions of windows unfortunately do not come with openssh, and you will need to install a third-party tool. you may choose from any of the following options:
older versions of windows unfortunately do not come with openssh, and you will need to install a third-party tool. you
may choose from any of the following options:
- [windows subsystem for linux](https://docs.microsoft.com/en-us/windows/wsl/install-win10)
- [msys2](http://www.msys2.org/)
@ -220,7 +225,7 @@ ssh-keygen -t ed25519 -a 100
```
1. if you press enter to accept the defaults, your public and private key will
be located at `~/.ssh/id_ed25519.pub` and `~/.ssh/id_ed25519` respectively
be located at `~/.ssh/id_ed25519.pub` and `~/.ssh/id_ed25519` respectively
1. `cat ~/.ssh/id_ed25519.pub`
@ -264,7 +269,7 @@ ssh-keygen -t ed25519 -a 100
```
1. if you press enter to accept the defaults, your public and private key will
be located at `~/.ssh/id_ed25519.pub` and `~/.ssh/id_ed25519` respectively
be located at `~/.ssh/id_ed25519.pub` and `~/.ssh/id_ed25519` respectively
1. `cat ~/.ssh/id_ed25519.pub`
@ -288,4 +293,6 @@ where username is your username (~ben would use `ssh ben@tilde.team`)
---
this tutorial is based on and uses parts of [the tilde.club ssh primer](https://github.com/tildeclub/tilde.club/blob/master/docs/ssh.md) and [the tilde.town ssh guide](https://tilde.town/wiki/getting-started/ssh.html).
this tutorial is based on and uses parts
of [the tilde.club ssh primer](https://github.com/tildeclub/tilde.club/blob/master/docs/ssh.md)
and [the tilde.town ssh guide](https://tilde.town/wiki/getting-started/ssh.html).

View File

@ -4,15 +4,15 @@ published: true
title: stuff to do on tilde.team
description: programs and utilities to use on tilde.team
category:
- main
- beginners
---
- `chat` - opens weechat connected to #meta and #team
- `cat $(which chat)` to see what defaults we're setting
- `cat $(which chat)` to see what defaults we're setting
- `mutt` - command line mail client for @tilde.team mail
- `alpine` - alternate command line mail client based on pine
- `bbj` - command line bbs (bulletin board and jelly)
- source here: [gitea mirror](https://tildegit.org/bbj/bbj) and [github fork](https://github.com/bbj-dev/bbj)
- source here: [gitea mirror](https://tildegit.org/bbj/bbj) and [github fork](https://github.com/bbj-dev/bbj)
- `who` - see who else is connected right now
- `pb` - [pastebin](https://paste.tilde.team)
- `talk` - old school tty-sharing tool: see `man talk` for more info
@ -20,7 +20,8 @@ category:
- `toot` - submit a post to the [tilde.team mastodon account](https://tilde.zone/@tildeteam)
- `botany` - tend to your plants and visit teammates' gardens
- `bb` - [bashblog tool](tildeblogs)
- `feels` - ttbp feels engine, forked from [tilde.town/~endorphant](https://tilde.town/~endorphant/ttbp/). post to gopher, web, or internal only.
- `feels` - ttbp feels engine, forked from [tilde.town/~endorphant](https://tilde.town/~endorphant/ttbp/). post to
gopher, web, or internal only.
- `dcss` - connect to [tildecrawl](https://crawl.tildeverse.org) and get your roguelike on
you can type `motd` to see this while you're logged in :)

View File

@ -4,7 +4,8 @@ published: true
title: teaching and learning on tilde.team
description: how to find and get help learning
category:
- main
- guides
- beginners
---
**tl;dr** bring project ideas. bring your skills. learn by doing.

View File

@ -4,7 +4,7 @@ published: false
title: my-new-page
description: description of the page
category:
- main
- main
---
wiki content here!

View File

@ -3,19 +3,23 @@ author: ~ben
published: true
title: tildeblogs with bashblog
description: tildeblogs information
category:
- main
category:
- publishing
---
> bashblog has some outstanding bugs that we haven't had time to fix. it still mostly works, but we wouldn't mind help
> fixing [the issues](https://tildegit.org/team/bashblog/issues).
bashblog is available system-wide as `bb`
tildeblogs can be built with [bashblog](https://tildegit.org/team/bashblog)
change to your ~/public_html/blog directory: `cd ~/public_html/blog`
change to your ~/public_html/blog directory: `cd ~/public_html/blog`
(bashblog will do this for you if you forget)
---
## usage
1. `bb post`
@ -24,14 +28,13 @@ change to your ~/public_html/blog directory: `cd ~/public_html/blog`
3. save, close, and then select from the bashblog menu choices
---
## advanced
edit the `.config` file to change the name and url and other settings for your blog
for an example of customization, see [~ben's blog](https://tilde.team/~ben/blog/)
for an example of customization, see [~ben's blog](https://tilde.team/~ben/blog/)
([config source](https://tildegit.org/ben/tilde/src/branch/master/blog/.config)).
for more details: see [the bashblog repo](https://tildegit.org/team/bashblog)

View File

@ -3,11 +3,11 @@ author: ~ben
published: true
title: tildepages
description: user pages on tilde.team
category:
- main
category:
- publishing
---
because [~ben](https://tilde.team/~ben/) hoards domain names, you can
because [~ben](https://tilde.team/~ben/) hoards domain names, you can
use the following domains with your tildepage:
see also the [master list of domains](domains).
@ -22,7 +22,7 @@ see also the [master list of domains](domains).
* tildeteam.net
* tildeteam.org
this means you can access your user page from any of the following
this means you can access your user page from any of the following
url formats, substituting domain and username:
* `https://domain.tld/~username/`
@ -35,21 +35,23 @@ url formats, substituting domain and username:
are served at the addresses described above.
static files are served normally, along with the following dynamic options:
* php - name the file with a .php extension or use index.php
* perl - name the file with a .pl extension
* sh/cgi - name the file with a .sh or .cgi extension
* python - name the file with a .py extension
* lua - name the file with a .lua extension
* cgi-bin - name it whatever you want and place it in `~/public_html/cgi-bin/`
don't forget to make the cgi-bin script executable
don't forget to make the cgi-bin script executable
if you're having trouble with any of these cgi scripts, make sure that the script
has a correct shebang, is executable, and that you're sending the content-type
has a correct shebang, is executable, and that you're sending the content-type
header as the first thing.
## webring
check out [~webring](https://tilde.team/ring/) for instructions of how to add your tilde.team html pages to the team webring.
check out [~webring](https://tilde.team/ring/) for instructions of how to add your tilde.team html pages to the team
webring.
## static page generators
@ -59,29 +61,29 @@ engines.
### blog engines
* [bashblog](tildeblogs) - a single shell script that helps you build a blog
with plain html or markdown. also supports mirroring your posts into your
[`~/public_gopher` gopherhole](gopher).
with plain html or markdown. also supports mirroring your posts into your
[`~/public_gopher` gopherhole](gopher).
* [ttbp](ttbp) - tilde.team blogging platform. originally built for [tilde.town](
https://tilde.town/) by [~endorphant](https://tilde.town/~endorphant/). forked
with a handful of patches for our setup.
https://tilde.town/) by [~endorphant](https://tilde.town/~endorphant/). forked
with a handful of patches for our setup.
### ssgs
* [mkdocs](https://www.mkdocs.org) - markdown project documentation tool.
additional themes are available from the [mkdocs-bootstrap](
http://mkdocs.github.io/mkdocs-bootstrap/) and [mkdocs-bootswatch](
http://mkdocs.github.io/mkdocs-bootswatch/) projects. just set your theme name
to one those listed and rebuild. generally recommended to not build the mkdocs
source directly in your webroot. set the destination to somewhere in `~/public_html`,
symlink, or move/copy the generated files manually. for example, if you wanted to
make a mkdocs site called mywiki available on the web, you could do:
`ln -s ~/mywiki ~/public_html/wiki`
* [mkdocs](https://www.mkdocs.org) - markdown project documentation tool.
additional themes are available from the [mkdocs-bootstrap](
http://mkdocs.github.io/mkdocs-bootstrap/) and [mkdocs-bootswatch](
http://mkdocs.github.io/mkdocs-bootswatch/) projects. just set your theme name
to one those listed and rebuild. generally recommended to not build the mkdocs
source directly in your webroot. set the destination to somewhere in `~/public_html`,
symlink, or move/copy the generated files manually. for example, if you wanted to
make a mkdocs site called mywiki available on the web, you could do:
`ln -s ~/mywiki ~/public_html/wiki`
* [hugo](https://gohugo.io/) - static site generator built in go
* [jekyll](https://jekyllrb.com/) - static site generator used by github for
[github pages](https://pages.github.com) built in ruby
* [jekyll](https://jekyllrb.com/) - static site generator used by github for
[github pages](https://pages.github.com) built in ruby
* [zola](https://getzola.org/) - single-binary static site generator written in rust

View File

@ -4,13 +4,15 @@ published: true
title: terms of service
description: tilde.team terms of service
category:
- main
- beginners
- about
- guidelines
---
tilde.team relies on the common courtesy and consideration of users to make
tilde.team relies on the common courtesy and consideration of users to make
its services fair for everyone. the following offences will result in a service ban:
tl;dr: don't do anything illegal or harmful, especially anything that could
tl;dr: don't do anything illegal or harmful, especially anything that could
[anger the hosting company](https://www.ovh.com/world/support/terms-and-conditions/)
you must be at least 13 years or older to use tilde.team.
@ -20,25 +22,24 @@ here are some things that we don't allow:
* deliberately defacing the accounts of other users
* deliberately trying to disrupt tilde.team's server
* using tilde.team as a launch pad for disrupting other servers
- this includes outgoing net- and portscanning
- this includes outgoing net- and portscanning
* using tilde.team to impersonate other websites and businesses for criminal purposes
* storing/distributing pornography of any genre and medium (especially child pornography)
* storing/distributing content that defames any individual
* promoting racial, ethnic, religious, political & other forms of bigotry
* mining cryptocurrencies
## network considerations
outgoing net- and portscanning is prohibited on tilde.team.
> this is outdated now that tilde.team lives on ovh
after the [major outage](/~ben/blog/november-13-post-mortem.html) of november 13th,
after the [major outage](/~ben/blog/november-13-post-mortem.html) of november 13th,
we have run in to the clause in the [hetzner tos](
https://www.hetzner.com/rechtliches/root-server/) that prohibits net- and
https://www.hetzner.com/rechtliches/root-server/) that prohibits net- and
portscanning. please don't try to reach anything in the [RFC-1918](
https://tools.ietf.org/html/rfc1918) private address space. for some reason,
https://tools.ietf.org/html/rfc1918) private address space. for some reason,
packets sent there will end up at the default gateway and may be interpreted as an attack.
i've added firewall rule to prevent outgoing requests to these subnets:
@ -47,7 +48,6 @@ i've added firewall rule to prevent outgoing requests to these subnets:
* 172.16.0.0/12
* 192.168.0.0/16
## resource usage
in general, we have plenty of resources available.

View File

@ -4,7 +4,8 @@ published: true
title: feels - tilde.team blogging platform
description: a cli blogging platform that can publish to your tilde page and your gopherhole
category:
- main
- publishing
- guides
---
`ttbp` stands for "tilde.town blogging platform", the original working name for
@ -99,7 +100,7 @@ directory.
if you opt to publish, the program creates a directory `~/.ttbp/www` where it
stores all html files it generates, and symlinks this from your `~/public_html`
with your chosen blog directory.
with your chosen blog directory.
you can also opt to publish to gopher, and the program will automatically
generate a gophermap of your feels.
@ -180,14 +181,14 @@ your ~/.ttbp directory entirely. **you might want to back up your
* to modify your stylesheet, edit your ~/.ttbp/config/style.css
* to modify the page header, edit your ~/.ttbp/config/header.txt
* there's a place marked off in the default header where you can safely put
custom HTML elements!
* there's a place marked off in the default header where you can safely put
custom HTML elements!
* to modify the page footer, edit your ~/.ttbp/config/footer.txt
### general tips/troubleshooting
* if the date looks like it's ahead or behind, it's because you haven't set
your local timezone yet. here are some
your local timezone yet. here are some
[timezone setting instructions](http://www.cyberciti.biz/faq/linux-unix-set-tz-environment-variable/)
* the feels burying tool will effectively clear your post for the day; you can
use this feature to start a fresh entry on a particular day by burying the
@ -202,4 +203,5 @@ these are a few ideas being kicked around, or under active development:
* buried feels browser
other ideas are listed on github as
[upcoming features](https://github.com/modgethanc/ttbp/issues?q=is%3Aissue+is%3Aopen+label%3A"upcoming+features") or [feature requests](https://github.com/modgethanc/ttbp/issues?q=is%3Aissue+is%3Aopen+label%3A"feature+request")!
[upcoming features](https://github.com/modgethanc/ttbp/issues?q=is%3Aissue+is%3Aopen+label%3A"upcoming+features")
or [feature requests](https://github.com/modgethanc/ttbp/issues?q=is%3Aissue+is%3Aopen+label%3A"feature+request")!

View File

@ -3,8 +3,9 @@ author: ~ben
published: true
title: daemonize with user units
description: a quick tutorial on creating and managing daemonized processes with systemd user units
category:
- main
category:
- guides
- technical
---
so you've got a process that you want to keep running. you might have it in a
@ -14,9 +15,9 @@ tmux or screen session. let's use systemd user units to manage it!
mkdir -p ~/.config/systemd/user/
2. create a basic service. save something like this in
`~/.config/systemd/user/my-new-service.service` (using the name of the unit
you're creating)
2. create a basic service. save something like this in
`~/.config/systemd/user/my-new-service.service` (using the name of the unit
you're creating)
[Unit]
Description=foo

View File

@ -3,8 +3,9 @@ author: ~ben
published: true
title: xmpp
description: how to use xmpp/jabber with your tilde.team account
category:
- main
category:
- services
- guides
---
[![](https://compliance.conversations.im/badge/tilde.team)](
@ -25,13 +26,14 @@ if you have a recommended client for mac platforms, feel free to discuss
and add it to this list.
we have a tilde.team MUC (multi-user chat) at [team@conference.tilde.team](
xmpp:team@conference.tilde.team?join), feel free to stop by!
xmpp:team@conference.tilde.team?join), feel free to stop by! note that the
official chat for tilde.team is [#team](https://tilde.chat/kiwi/#team) on irc.
## biboumi
there's also a [biboumi](https://biboumi.louiz.org/) server
connected with our xmpp server. you can join any [irc](irc)
channel as an xmpp MUC (multi user chat) room with the following
channel as an xmpp MUC (multi-user chat) room with the following
format:
#channelname@biboumi.tilde.team