club
/
site
mirror of https://github.com/tildeclub/site
2
0
Fork 0
Code Issues Releases Wiki Activity

stop tracking html build artifacts, add header permalinks

This commit is contained in:
Ben Harris 2019-09-22 19:41:13 -04:00
parent 6fb23fa2f6
commit 25e3ed3757
32 changed files with 15 additions and 1461 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
wiki/.gitignore vendored Normal file
View File

@ -0,0 +1 @@
*.html

38
wiki/Editing-your-index.html-file.html
View File

@ -1,38 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>Editing your index.html file</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">Editing your index.html file</h1>
</header>
<p>Type: <code>nano</code> index.html to open your index.html file and begin editing</p>
<figure>
<img src="http://tilde.club/~annika/static/nano.png" alt="screenshot of the nano editor" /><figcaption>screenshot of the nano editor</figcaption>
</figure>
<p>Edit your file, willy nilly</p>
<p>When done editing, use <code>CTRL+X</code> to close the file</p>
<p>You’ll be asked if you want to save; say y and [return] to return to the command line</p>
<p>Refresh your tilde page in your browser to see your new website</p>
<p>Note: If at any time you feel you made a mistake in editing, you can exit and n to not save.</p>
<p>There’s more info here about the [[nano]] editor; if you’re familiar with [[emacs]] or [[vim]] they are here too.</p>
</body>
</html>

35
wiki/Finding-your-index.html-file.html
View File

@ -1,35 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>Finding your index.html file</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">Finding your index.html file</h1>
</header>
<p>There are some basic command line commands you’ll want to Google and learn, but for this tutorial you only need a few:</p>
<p><code>ls</code> = list files and folders in current directory</p>
<p><code>cd</code> = change directories</p>
<p><code>vim</code>, <code>emacs</code>, <code>nano</code> = a text editor</p>
<p>Type: <code>ls</code> to see where you are; you should see a directory called “public_html”</p>
<p>Type: <code>cd public_html</code> to browse into that folder</p>
<p>Type: <code>ls</code> to see where you are; you should see your index.html file</p>
</body>
</html>

33
wiki/JSON.html
View File

@ -1,33 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>JSON</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">JSON</h1>
</header>
<p>JSON is the “Javascript Object Notation”, basically a file format for data that’s suitable for easy processing by most modern web-based tools.</p>
<p>Several tilde.club programs expose APIs essentially by spitting out JSON as their output, including e.g. the list of recently updated home pages at</p>
<p>http://tilde.club/~delfuego/tilde.24h.json</p>
<p>If you’re looking to parse JSON from the command line with a minimum of code, the <code>jq</code> program may be your thing. <code>jq</code> is a filter that takes JSON on standard input and produces JSON on standard output. Along the way in the middle you can do various standard sorts of file munging on a field by field basis.</p>
<p><a href="http://stedolan.github.io/jq/manual/">Documentation for <code>jq</code> is in its manual.</a></p>
</body>
</html>

32
wiki/Resetting-your-editor-view-when-chat-interrupts.html
View File

@ -1,32 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>Resetting your editor view when chat interrupts</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">Resetting your editor view when chat interrupts</h1>
</header>
<p>You may have been caught off guard while editing and had some random chat messages muss up your view. It didn’t actually edit your HTML page but you need to reset your editor view.</p>
<p><code>CTRL+L</code> will reset your view</p>
<p><code>mesg n</code> at the command prompt will turn off chat messages in that window.</p>
<p>If you don’t ever want to see wall messages on your screen, put <code>mesg n</code> into your startup file (details of how to do that needed here).</p>
</body>
</html>

83
wiki/Safe-Scripting-the-Tilde-Way.html
View File

@ -1,83 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="author" content="michaelcoyote" />
<title>safe scripting the tilde way</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">safe scripting the tilde way</h1>
<p>authors:</p>
<p class="author"><a href="/~michaelcoyote/">~michaelcoyote</a></p>
</header>
<p>Welcome to tilde.club. For many of you this may be your first multi-user host and for even more of you this may be your <em>first</em> host. Welcome to all of you.</p>
<p>Whether you are used to Unix, Linux and programming or a complete beginner please consider this an invitation to create and build new things.</p>
<p>It’s important when creating however that we respect the shared environment and that we respect the boundaries of others.</p>
<p>As Paul says:</p>
<blockquote>
<p>no drama. be respectful. have fun.</p>
</blockquote>
<p>What does that mean with respect to scripting and programming on a shared host?</p>
<ul>
<li>DOs
<ul>
<li>Respect shared CPU/Disk/Network resources</li>
<li>Keep things that require a tilde.club login local to the server (don’t post publicly) :
<ul>
<li>Finger info</li>
<li>local home directory files such as <code>~/.plan</code> and <code>~/.profile</code> files</li>
<li>Note that exceptions could include an opt-in file or special permissions from the user.</li>
</ul></li>
<li>Respect <code>robots.txt</code> when writing web crawlers</li>
</ul></li>
</ul>
<p>In short use your common sense and consider how your actions may affect others.</p>
<p>If you are unsure if something is a good idea or not, head to irc or message using the <code>wall</code> command and ask others what they think.</p>
<p>If you want a conclusive answer, contact one of the system operators.</p>
<h5 id="thinking-privacy">Thinking privacy</h5>
<p>Consider the source of the data.</p>
<p>E.g. We know that finger data might contain personal data such as phone numbers, and other identifying information and is not generally available without a tilde.club login.</p>
<p>Before exposing data such as this to the world, it should check for an opt in file such as the .public file file test before presenting info to the outside world.</p>
<h4 id="shared-resources">Shared Resources</h4>
<ul>
<li>In general
<ul>
<li>Consider executing long running processes during overnight hours when fewer users are on the system</li>
</ul></li>
<li>CPU
<ul>
<li>Use the <code>nice</code> command to keep intensive processes from affecting others
<ul>
<li>The <code>nice -n19 -p$$</code> placed in a script will make sure it runs at the lowest priority.</li>
<li>Run a long command at the lowest CPU priority: <code>nice -n 19 ~/bin/command</code></li>
<li>Change the priority of process 923 (also known as “re-nicing a process”) : <code>renice -17 -p923</code></li>
</ul></li>
</ul></li>
<li>Disk
<ul>
<li>On any commands that will heavily use disk, consider using the <code>ionice</code> command so that scripts will not affect interactive users
<ul>
<li>By adding the <code>ionice -c3 -p$$</code> command to any script, it will only use disk when idle.</li>
<li>You can also run a command or script: <code>ionice -c3 -t ~/bin/command</code></li>
</ul></li>
</ul></li>
</ul>
</body>
</html>

32
wiki/Time-zone.html
View File

@ -1,32 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>time zones</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">time zones</h1>
</header>
<p>The timezone by default on the server is UTC.</p>
<p>If you want to make it so that your shell prints out dates in localtime for you, run <code>tzselect</code> to find the correct timezone name that you’ll need to export as the <code>TZ</code> environment variable.</p>
<p>for example, if you’re in eastern time, add something like this <code>export TZ=&quot;America/Detroit&quot;</code></p>
<p>to your <code>.bashrc</code> .</p>
</body>
</html>

35
wiki/Usenet-news.html
View File

@ -1,35 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>usenet news</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">usenet news</h1>
</header>
<h2 id="this-is-out-of-date-and-the-netnews-server-is-down">this is out of date and the netnews server is down</h2>
<p>We’re working on it. You’ll need a news server to read news, and it’s up; it’s <code>news.tilde.club</code>.</p>
<p>[[slrn]] is a newsreader; see http://slrn.sourceforge.net/ for details.</p>
<p>[[pine]] can read news; this <a href="tutorial">http://www.chebucto.ns.ca/Help/News/PineNews.html</a> might help. You can also read the <a href="http://www.washington.edu/pine/faq/news.html">FAQ from U Washington</a>.</p>
<p>In Pine do ‘S’ for setup, ‘C’ for config, then set ‘NNTP Server (for news)’ to news.tilde.club Then go back to the main menu, and pick Folder List, A for add, ^t for list</p>
<p><code>M-x gnus</code> in [[emacs]] can read news, but you better know [[emacs]] first before you start.</p>
<p>[[lynx]] reads news, a la <code>lynx news://news.tilde.club/tilde.general</code>. It can even post news, but you have to design your own headers.</p>
</body>
</html>

31
wiki/VPN-Gate.html
View File

@ -1,31 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>VPN Gate</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">VPN Gate</h1>
</header>
<p><code>VPN Gate</code> is a project from U Tsukuba in Japan that allows you to evade censorship and filtering by setting up VPN tunnels. It was designed with the Great Firewall of China in mind.</p>
<p>http://www.vpngate.net/en/</p>
<p>You may need client side software to make this work; [[tunnelblick]] is one such service on the Mac.</p>
</body>
</html>

29
wiki/archive.org.html
View File

@ -1,29 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>archive.org</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">archive.org</h1>
</header>
<p>archive.org has an archive of tilde.club at http://web.archive.org/web/*/http://tilde.club</p>
</body>
</html>

9
wiki/build-wiki.sh
View File

@ -2,6 +2,13 @@
for page in source/*.md; do
pagename=$(basename $page ".md")
pandoc --template pandoc-template.html -o "$pagename.html" "source/$pagename.md"
printf "building %s wiki article\n" "$pagename"
pandoc \
--template wiki.tmpl \
--lua-filter header-permalinks.lua \
-T "tilde.club wiki | " \
-o "$pagename.html" \
"source/$pagename.md"
done

46
wiki/chat.html
View File

@ -1,46 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="author" content="emv" />
<meta name="author" content="benharri" />
<title>Socializing and chat</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">Socializing and chat</h1>
<p>authors:</p>
<p class="author"><a href="/~emv/">~emv</a></p>
<p class="author"><a href="/~benharri/">~benharri</a></p>
</header>
<h2 id="irc">irc</h2>
<p>run <code>chat</code> to open <a href="https://weechat.org">weechat</a> auto-connected to our irc server.</p>
<p>other clients like irssi are available as well! just connect to localhost on port 6667 and <code>/join #club</code>.</p>
<p>feel free to use tilde.chat’s <a href="https://web.tilde.chat/?join=club">webchat</a> too</p>
<h2 id="mailing-list">mailing list</h2>
<p>we now have an official mailing list!</p>
<p>if your account is old (pre sept 2019), you should be subscribed with the email you originally signed up with. if your account is newer (post sept 2019), then you should be subscribed with your <span class="citation" data-cites="tilde.club">@tilde.club</span> address. if you don’t fit either of those categories, you can subscribe by visiting the <a href="https://lists.tildeverse.org/postorius/lists/tildeclub.lists.tildeverse.org/">web portal</a> or by sending a mail to tildeclub-subscribe@lists.tildeverse.org with “subscribe” in the subject line. in either case, you can change the email you’re subscribed with on the web portal or by unsubscribing and re-subscribing from the other address.</p>
<p>list archives are available <a href="https://lists.tildeverse.org/hyperkitty/list/tildeclub@lists.tildeverse.org/">on the web here</a>.</p>
<p>as of september 17, 2019, we’re still seeing quite a few pending mails to gmail, yahoo, and fastmail. help get our list delivered by making sure to mark list messages as not spam and adding the list address to your contacts. if you’re feeling especially motivated, please reach out to the support on your mail provider and ask them to look into why you’re not receiving the messages.</p>
<h2 id="chat-from-the-command-line">chat from the command line</h2>
<p>Back on the command line, you may want to participate in chat. There is some great chat, likely, or you have questions.</p>
<p>Type: <code>wall</code> and <code>[return]</code> to tell Terminal you are ready to chat Type your message to the world and <code>[return]</code> <code>CTRL+D</code> to post or <code>CTRL+C</code> to change your mind and cancel Have fun!</p>
<p>If you’re tired of reading chats in a window, <code>mesg n</code> will turn it off, and <code>mesg y</code> will turn it back on again. And if you want to see more people, look for IRC.</p>
</body>
</html>

98
wiki/code-of-conduct.html
View File

@ -1,98 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="author" content="benharri" />
<title>code of conduct</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">code of conduct</h1>
<p>authors:</p>
<p class="author"><a href="/~benharri/">~benharri</a></p>
</header>
<blockquote>
<p><strong>tl;dr</strong> learn by doing and helping. be excellent to each other. have fun!</p>
</blockquote>
<h2 id="purpose">1. purpose</h2>
<p>a primary goal of tilde.club 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.</p>
<p>this code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.</p>
<p>we invite all those who participate in tilde.club to help us create safe and positive experiences for everyone.</p>
<h2 id="tilde.club-mission">2. tilde.club mission</h2>
<p><strong>tilde.club exists to foster an engaged community for socializing, learning, and making cool stuff</strong></p>
<p>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.</p>
<p>to that end, tilde.club 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.</p>
<h2 id="expected-behavior">3. expected behavior</h2>
<p>the following behaviors are expected and requested of all community members:</p>
<ul>
<li>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.</li>
<li>refrain from demeaning, discriminatory, or harassing behavior and speech.</li>
<li>be mindful of your surroundings and of your fellow participants. * teach when people need help. don’t do it for them.</li>
</ul>
<h2 id="unacceptable-behavior">4. unacceptable behavior</h2>
<p>the following behaviors are considered harassment and are unacceptable within our community:</p>
<ul>
<li>violence, threats of violence or violent language directed against another person.<br />
</li>
<li>sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.<br />
</li>
<li>posting or displaying sexually explicit or violent material.<br />
</li>
<li>posting or threatening to post other people’s personally identifying information (“doxing”).<br />
</li>
<li>personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.<br />
</li>
<li>unwelcome sexual attention. this includes sexualized comments or jokes.<br />
</li>
<li>deliberate intimidation, stalking or following.</li>
</ul>
<h2 id="consequences-of-unacceptable-behavior">5. consequences of unacceptable behavior</h2>
<p>unacceptable behavior from any community member, including sponsors and those with decision-making authority (sudo), will not be tolerated.</p>
<p>anyone asked to stop unacceptable behavior is expected to comply immediately.</p>
<p>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.club without warning (meaning your account will be terminated and all user data deleted).</p>
<h2 id="reporting-guidelines">6. reporting guidelines</h2>
<p>if you are subject to or witness unacceptable behavior, or have any other concerns, please contact an admin (see info below).</p>
<p>additionally, help engaging with law enforcement is available.</p>
<h2 id="addressing-grievances">7. addressing grievances</h2>
<p>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.</p>
<h2 id="scope">8. scope</h2>
<p>we expect all tilde.club members to abide by this code of conduct while:</p>
<ul>
<li>engaging with other members</li>
<li>publishing content on tilde.club</li>
</ul>
<h2 id="contact-info">9. contact info</h2>
<p>tilde.club admins:</p>
<p>you can also send a mail to <a href="mailto:root@tilde.club">root@tilde.club</a> to make sure we all get it.</p>
<ul>
<li><a href="https://tilde.club/~benharri/">benharri</a>:
<ul>
<li><a href="mailto:benharri@tilde.club">benharri@tilde.club</a></li>
<li>on irc <code>/query ben hello</code></li>
</ul></li>
<li><a href="https://tilde.club/~deepend/">deepend</a>:
<ul>
<li><a href="mailto:deepend@tilde.club">deepend@tilde.club</a></li>
<li>on irc <code>/query deepend hello</code></li>
</ul></li>
</ul>
<h2 id="license-and-attribution">10. license and attribution</h2>
<p>this code of conduct is based on <a href="http://citizencodeofconduct.org/">citizencodeofconduct.org</a> and <a href="http://tilde.town/wiki/conduct.html">tilde.town coc</a> under the terms of the <a href="http://creativecommons.org/licenses/by-sa/3.0/">creative commons attribution-sharealike license</a>.</p>
</body>
</html>

41
wiki/edit_index.html
View File

@ -1,41 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="author" content="vielmetti" />
<title>Editing your index.html file</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">Editing your index.html file</h1>
<p>authors:</p>
<p class="author"><a href="/~vielmetti/">~vielmetti</a></p>
</header>
<p>Type: <code>nano</code> index.html to open your index.html file and begin editing</p>
<figure>
<img src="https://tilde.club/~annika/static/nano.png" alt="screenshot of the nano editor" /><figcaption>screenshot of the nano editor</figcaption>
</figure>
<p>Edit your file, willy nilly</p>
<p>When done editing, use <code>CTRL+X</code> to close the file</p>
<p>You’ll be asked if you want to save; say y and [return] to return to the command line</p>
<p>Refresh your tilde page in your browser to see your new website</p>
<p>Note: If at any time you feel you made a mistake in editing, you can exit and n to not save.</p>
<p>There’s more info here about the nano editor; if you’re familiar with emacs or vim they are here too.</p>
</body>
</html>

44
wiki/email.html
View File

@ -1,44 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="author" content="benharri" />
<title>email</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">email</h1>
<p>authors:</p>
<p class="author"><a href="/~benharri/">~benharri</a></p>
</header>
<p>Your shiny, new tilde.club account comes with an email account. <code>alpine</code> is a command-line email application to use it, as is <code>mutt</code>. Good old-fashioned <code>mail</code> works too, although it’s a little cryptic.</p>
<p><code>alpine</code> is menu driven, and the menus are self-explanatory; it’s surprisingly easy to learn, and surprisingly powerful when you want to customize it.</p>
<p>From the command line (after logged in via SSH), type: <code>pine</code> and <code>[return]</code> Follow instructions and use the menus at the bottom and top. (Note: When you see the ^ in front of the letter it means you need to use CTRL, otherwise just use the letter.)</p>
<h2 id="non-cli-options">non-cli options</h2>
<p>alternatively, you can use the <a href="https://webmail.tilde.club/">webmail</a> or standard imap/smtp.</p>
<p>some clients will automatically detect the right settings (tested with thunderbird).</p>
<p>connection settings: - imap.tilde.club port 993 with ssl - pop3.tilde.club port 995 with ssl - smtp.tilde.club port 587 with starttls</p>
<p>if you’d like your <span class="citation" data-cites="tilde.club">@tilde.club</span> mail forwarded elsewhere, you can put an email address in a file called <code>~/.forward</code></p>
<h2 id="sieve-filtering">sieve filtering</h2>
<p>our dovecot configuration supports <a href="http://sieve.info/">sieve</a> and <a href="https://wiki1.dovecot.org/ManageSieve">managesieve</a>.</p>
<p>this means that you should put your scripts in a <code>~/sieve/</code> directory, symlink the active script to <code>~/.dovecot.sieve</code>, and make sure to compile it with <code>sievec ~/.dovecot.sieve</code>.</p>
<p>you can find some example sieve scripts <a href="https://wiki.dovecot.org/Pigeonhole/Sieve/Examples">here</a>.</p>
<p>alternately, you can use webmail’s <a href="https://webmail.tilde.club/#/settings/filters">filter settings</a> to configure your filters.</p>
</body>
</html>

81
wiki/faq.html
View File

@ -1,81 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="author" content="ford" />
<title>faq</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">faq</h1>
<p>authors:</p>
<p class="author"><a href="/~ford/">~ford</a></p>
</header>
<pre><code> _______________________________________
/ WELCOME TO TILDE.CLUB A place for web \
\ pages /
---------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||</code></pre>
<h2 id="looking-to-join-we-cant-wait-to-meet-you">Looking to join? We can't wait to meet you!</h2>
<p>Sign-ups will be re-launching on September 20th, 2019. Can’t wait to meet you all!</p>
<p><a href="http://tilde.club/%7Epfhawkins/othertildes.html">Several alternate sites have sprouted up</a></p>
<h2 id="how-did-this-accidentally-awesome-thing-get-started">How did this accidentally awesome thing get started?</h2>
<p><a href="https://medium.com/message/tilde-club-i-had-a-couple-drinks-and-woke-up-with-1-000-nerds-a8904f0a2ebf">Paul wrote an explanation on Medium</a> and you can follow along with his thinking <a href="http://tilde.club/~ford/">on his tilde blog</a>.</p>
<h2 id="im-on-tilde-now-what">I'm on Tilde, now what?</h2>
<p>Tilde has a great community culture and we're trying hard to keep it that way. We're working on some netiquette outlines for people who are new to all of this. In the meantime...</p>
<ul>
<li>DON'T HACK THE GIBSON.</li>
<li>no drama. be respectful. have fun. we're all trying, and we're all in this together :)</li>
</ul>
<h2 id="got-it-dont-be-a-jerk.-but-how-do-i-like-do-things">Got it, don't be a jerk. But how do I, like, do things?</h2>
<p>Here are some good places to start</p>
<ul>
<li><a href="http://tilde.club/~anthonydpaul/primer.html">the unofficial official tilde primer</a></li>
<li><a href="http://tilde.club/~procload/">some quick tips</a></li>
<li><a href="http://tilde.club/~pfhawkins/tipsntricks.html">some more quick tips</a></li>
<li><a href="http://tilde.club/~cortex/usenet_in_pine.txt">how do I usenet in Alpine</a>?</li>
<li><a href="http://tilde.club/~jonathan/screen/">help me understand 'screen'</a></li>
</ul>
<h2 id="who-are-all-these-folks-and-what-are-they-up-to">Who are all these folks and what are they up to?</h2>
<ul>
<li><a href="http://tilde.club/~joeld/tildelore.html">tell me some lore</a>?</li>
<li><a href="http://tilde.club/~whitneymcn/whoville.shtml">who is online right now</a>?</li>
<li><a href="http://tilde.club/~delfuego/tilde.24h.html">who updated their websites recently</a>?</li>
<li><a href="http://tilde.club/~ford/social.html">who links to each other</a>?</li>
<li><a href="http://tilde.club/~_/">can you give me a blogroll</a>?</li>
</ul>
<h2 id="other-links">Other links</h2>
<ul>
<li><a href="https://github.com/tildeclub/tilde.club">Github</a></li>
<li><a href="http://tilde.club/~harper/link.html?action=join">Webring</a></li>
<li><a href="http://goo.gl/forms/LT2bDgtmwH">Skillswap</a></li>
</ul>
<h2 id="how-do-you-pronounce-tilde">How do you pronounce &quot;tilde&quot;?</h2>
<p>Tilde the word is pronounced TIL-duh. Tilde the community is pronounced TIL-dee.</p>
<p>We can't wait to meet you. Seriously.</p>
<pre><code> __ .&#39; &#39;.
_/__) . . .
(8|)_}}- . . .
`\__) &#39;. . &#39; &#39; . . &#39;</code></pre>
</body>
</html>

35
wiki/finding_index.html
View File

@ -1,35 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>finding your index.html</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">finding your index.html</h1>
</header>
<p>There are some basic command line commands you’ll want to Google and learn, but for this tutorial you only need a few:</p>
<p><code>ls</code> = list files and folders in current directory</p>
<p><code>cd</code> = change directories</p>
<p><code>vim</code>, <code>emacs</code>, <code>nano</code> = a text editor</p>
<p>Type: <code>ls</code> to see where you are; you should see a directory called “public_html”</p>
<p>Type: <code>cd public_html</code> to browse into that folder</p>
<p>Type: <code>ls</code> to see where you are; you should see your index.html file</p>
</body>
</html>

64
wiki/git.html
View File

@ -1,64 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>git usage</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">git usage</h1>
</header>
<p><code>git</code> is a version control system. It’s pretty confusing at first, but once you sort out what it can do and can’t do, it starts to get better.</p>
<p>This tutorial is pretty good: http://git-scm.com/docs/gittutorial</p>
<p>The best way to learn <code>git</code> is to find someone who knows <code>git</code> really well and sort out issues with them. Ask on [[IRC]] if you get stuck. (There should be a better buddy system for this, but until there is, we do what we can.)</p>
<p>A good introduction to <code>git</code> is to create a repository for your <code>public_html</code> directory. This will allow you to back up your public web directory.</p>
<p>First thing you will want to do is set up git.</p>
<p>If you don’t have a <a href="http://github.com">GitHub</a> account, you will want one for this exercise. If you choose another Git host, you will need to work out some parts of this setup on your own.</p>
<p>Once you have a git account, you will want to set up <code>git</code> for your tilde.club account. Use the email address that you used to create your GitHub account. You can register multiple accounts with GitHub if needed.</p>
<pre><code>git config --global user.name &quot;Your Name Here&quot;
git config --global user.email youremail@example.org</code></pre>
<p>You will also want to create a <code>.gitignore</code> file. This file defines what things you want git to ignore, such as editor temporary files or directories you may not want to keep in <code>git</code> such as generated files or private files you upload to a public repository. The <code>.gitignore</code> file can be created in your home directory, but I like to create it in the project directory.</p>
<p>Here is an example <code>.gitignore</code> file:</p>
<pre><code># files being edited
*~
*swp
# Generated files
tilde_graphs
# Private files
diary.txt</code></pre>
<p>Now go create a repository on GitHub. In our examples we are using mytildeweb as the repo name, but you can choose whatever name works for you. If you do change the repository name be sure to update the commands with the proper one.</p>
<p>Now we should be ready to create and upload the repository.</p>
<pre><code>cd public_html/
# This will initialize public_html as a repository
git init
# Adds all files to the repo. &quot;.&quot; means &quot;the current directory&quot; (public_html, in this case)
# Note: you can also add files one at a time
git add .
# Commits files to local repo
git commit -m &quot;first commit of tildeweb&quot;
# Tells git where your remote repo is
git remote add origin https://github.com/&lt;yourgithubuser&gt;/mytildeweb.git
# Uploads to the remote repo
git push -u origin master</code></pre>
<p>Your files should now be on GitHub. If you make a change and you want to update, do the following after making your edits:</p>
<pre><code>git add index.html
git commit -m &quot;updated blog&quot;
git push origin master</code></pre>
</body>
</html>

6
wiki/header-permalinks.lua Normal file
View File

@ -0,0 +1,6 @@
function Header(elem)
table.insert(elem.content, pandoc.Space())
table.insert(elem.content, pandoc.Link("🔗", "#" .. elem.identifier))
return elem
end

30
wiki/leafnode.html
View File

@ -1,30 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>Leafnode</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">Leafnode</h1>
</header>
<p><code>leafnode</code> is a news client suitable for “leaf” nodes, that is nodes that have no downstream feeds.</p>
<p>http://leafnode.sourceforge.net/</p>
</body>
</html>

44
wiki/netiquette.html
View File

@ -1,44 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>tilde.club netiquette</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">tilde.club netiquette</h1>
</header>
<h2 id="two-phrases-we-use-a-lot">Two phrases we use a lot</h2>
<ul>
<li>DON’T HACK THE GIBSON</li>
<li>No drama. Be respectful. Have fun. We’re all trying, and we’re all in this together :)</li>
</ul>
<h2 id="details">Details</h2>
<p>First things first, explore and have fun! But remember, this is a single linux server trying to support the weight of several hundred nerds. Don’t host servers, don’t run heavy processes, don’t host giant files. In short, be gentle.</p>
<p>More about <a href="http://tilde.club/#WHEREISTHIS">scripting netiquette here</a></p>
<p>Now let’s talk about drama. There is a Mary J. Blige song called “No More Drama.” If Mary J. Blige would think it was drama, it is drama. No flamewars about emacs/vi, no matter how historically accurate they may be. No guilting people, shaming them, or making them feel bad. More benefit of the doubt and less “are you kidding me?”</p>
<h2 id="fords-sacred-vows-to-the-community">~ford’s SACRED VOWS to the community</h2>
<p>I will do my best to do the following things:</p>
<ol type="1">
<li><p>I will make a weekly backup of the <code>public_html</code> directories so when some teen in Estonia decides to hack in and ruin everything we can bring up a new server and limp back to life.</p></li>
<li><p>I won’t shut things down without a month of warning and once it’s shut down I’ll make sure a file with all the <code>public_html</code> directories is uploaded to archive.org.</p></li>
<li><p>If any community forms at all (DUBIOUS BUT SURPRISE ME) I promise I won’t blow up the community without, like, first pointing everyone to some free IRC channel or something.</p></li>
</ol>
</body>
</html>

31
wiki/screen.html
View File

@ -1,31 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>terminal multiplexers</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">terminal multiplexers</h1>
</header>
<p><code>screen</code> is a unix utility that lets you manage multiple shells from within a single window. You switch between them with a few keystrokes. When you disconnect it keeps the processes alive, and you can reconnect from another login.</p>
<p>It’s pretty handy. [[tmux]] does a similar set of things.</p>
<p>a nice <a href="http://tilde.club/~jonathan/screen/">screen tutorial</a> from ~jonathan will walk you through it.</p>
</body>
</html>

134
wiki/security.html
View File

@ -1,134 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="author" content="michaelcoyote" />
<title>Editing Basic UNIX Security the Tilde way</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">Editing Basic UNIX Security the Tilde way</h1>
<p>authors:</p>
<p class="author"><a href="/~michaelcoyote/">~michaelcoyote</a></p>
</header>
<blockquote>
<p>“Unix is public by default. This means that other people who use the server can see your files. You can change that on a file-by-file basis. You can also change the default behavior for you. It is totally okay to keep your stuff private. Let us show you how.”</p>
</blockquote>
<p>Unix was built with a fairly open security policy. It’s the kind of system you might expect a bunch of Berkley hippies to design. That said, if it bugs you that someone might be able to look the files in your home directory and you don’t want to read any more of this document then run these commands:</p>
<pre><code>cd ~
chmod 711 .</code></pre>
<p>Those will keep anyone on the system from looking at your directory while still allowing your <code>~youruser</code> site to work. If you want to have more control over who can view what in your directory, then please read on. You can even come back and read this later, we’ll be here.</p>
<h3 id="users-and-groups">Users and Groups</h3>
<p>What is a user? For starters, you are a user and so is every other person on the system. Sometimes special user accounts are used for running specific processes (such as the web server) or for handling special administrative tasks.</p>
<p>There are several attributes that define a user.</p>
<ul>
<li>username This is your login id and the name of your homedir</li>
<li>user id (or uid) This is your unique numerical id number on the system. This is how the system keeps track of you, your processes, and your files.</li>
<li>group id (or gid) This is a unique numerical id number for your primary user group on the system. User groups are the traditional way that users would colaberate on large projects.</li>
</ul>
<p>For now we only need to know about the username.</p>
<h4 id="welcome-to-tilde.club-your-new-home-and-homedir">Welcome to tilde.club, your new home (and homedir)</h4>
<p>When you registered for the system, you got an email that contained many things. One of those things was a username, and another was a password. When you logged into the server you were presented with what we call a prompt, and it looked a bit like this:</p>
<pre><code>sh-4.1$</code></pre>
<p>That’s boring so type the command <code>ls -l public_html/index.html</code></p>
<pre><code>sh-4.1$ ls -l public_html/index.html
rw-rw-r-- 1 youruser youruser 177 Oct 13 04:51 public_html/index.html</code></pre>
<p>You’ll notice that your login shows up, but what does this actually show us?</p>
<p>First of all <code>ls</code> is a command to list files and directories. We’ve given it the command line switch <code>-l</code> that tells the <code>ls</code> command that we want a long listing of the file or directory attributes, and finally we’ve given it the filename <code>my_file</code> so that we can see its file attributes.</p>
<p>What does this long file listing of <code>my_file</code> show us?</p>
<pre><code>-rw-rw-r-- 1 youruser youruser 177 Oct 13 04:51 my_file
---------- --- ------- -------- ----- ------------ -------------
| | | | | | |
| | | | | | File Name
| | | | | +--- Modification Time
| | | | +------------- Size (in bytes)
| | | +----------------------- Group owner
| | +-------------------------------- User owner
| +-------------------------------------- Number of links
+---------------------------------------------- File Permissions</code></pre>
<p>This seems like a lot to take in, but for the purpose of talking about files and security, we’ll only need three things: the file permissions, the group owner and the user owner.</p>
<ul>
<li>Homework
<ul>
<li>Run <code>ls -la</code> in your home directory and note the users and permissions of the various files</li>
<li>Run <code>ls -l /etc/passwd</code> and <code>ls -l /var/log/messages</code> and compare the permissions and ownership to that of your homedir</li>
</ul></li>
</ul>
<h3 id="basics-about-file-and-directory-permissions">Basics about file and directory permissions</h3>
<pre><code>-rwxrwxrwx
----------
| | | |
| | | +--- Other Read/Write/Execute permissions
| | +------ Group Read/Write/Execute permissions
| +--------- User Read/Write/Execute permissions
+----------- Directory/Special flag</code></pre>
<p>The first column at first glance looks like a bunch of alphabet soup, however if you look over a few of them, a pattern begins to emerge. Some lines begin with <code>d</code> and there are repeating instances of <code>r</code>, <code>w</code> and <code>x</code>. You might notice that the lines beginning with <code>d</code> refer to directories and that many files have <code>rw-</code> at the start of the column and <code>r--</code> or even <code>---</code> at the end of the column. These are important and indicate to the computer and to users how that file can be accessed.</p>
<h4 id="types-of-permissions">Types of permissions</h4>
<p>There are three major types of permissions (and a hand full of others) - Read Read permission is represented as an <code>r</code> and will allow a listing of a directory and reading a file. - Write Write permission is represented with a <code>w</code> and allows a file or directory to be written to or deleted. - Execute Execute permission is represented as an <code>x</code> and allows a file (such as a script) to be executed and it allows for a directory to be “traversed”</p>
<ul>
<li>Other special permissions and notations in <code>ls -l</code>
<ul>
<li><code>-</code> means that the permission for that place isn’t set. If it’s at the beginning of the line, it means it’s a normal file.</li>
<li><code>d</code> at the start of a line isn’t a permission really. It just denotes a directory.</li>
<li><code>b</code> or <code>c</code> isn’t a permission either, it probably means you did an <code>ls -l</code> of the <code>/dev</code> directory as those indicate block or character devices.</li>
<li><code>s</code> is a setuid/setgid permission. It’s a special setting that allows you to run a script file or program as a user or a group. It can be used on a directory to make sure files are written as a user/group It’s rare to see.</li>
</ul></li>
</ul>
<h4 id="three-classes-of-access-permissions">Three classes of access permissions</h4>
<ul>
<li><p>User permissions This set of access controls define what an owner can do to her own files or directories. These controls are most often useful to set on a script file you want to run or a file you want to protect from deletion or overwriting.</p></li>
<li><p>Group permissions This set of access controls define what the group can do to a file or directory. This tends not to matter much in your homedir, but it can matter a lot when working with other users on shared projects.</p></li>
<li><p>Others These access controls are what you use to allow and others who are not listed as an owner or group member to do to a file or directory. For example, if you remove read permissions from others on your ~/public_html/index.html`, the webserver process will be unable to read your web page.</p></li>
</ul>
<h4 id="changing-file-and-directory-permissions-using-chmod">Changing file and directory permissions using <code>chmod</code></h4>
<p>Examples</p>
<ul>
<li>Homework
<ul>
<li><code>mkdir -p test/01</code> and then try the following <code>chmod</code> commands chmod u+rwx test echo “hello world” &gt; test/a_file ls -l test chmod ugo-rw test ls -l test ls -l test/a_file</li>
</ul></li>
</ul>
<h4 id="basics-about-the-finger-and-chfn-commands">Basics about the <code>finger</code> and <code>chfn</code> commands</h4>
<p>How to see others in the system using <code>finger</code></p>
<pre><code>Type the command `finger`
Type the command `finger $USER`</code></pre>
<p>How others see you.</p>
<p>Changing the information people see about you using <code>chfn</code></p>
<p>creating a <code>~/.plan</code> and <code>~/.project</code> file that’s readable</p>
<h4 id="more-advanced-topics">More advanced topics</h4>
<p>Let’s look at the <code>/etc/passwd</code> file. What is it? It’s a file that contains most of the information about users in the system.</p>
<ul>
<li>Homework
<ul>
<li><code>head -10 /etc/passwd</code></li>
<li><code>grep $USER /etc/passwd</code></li>
<li>Note the columns in the <code>/etc/passwd</code> file. Note the columns and the <code>:</code> separator between them.</li>
</ul></li>
</ul>
<p>Back at our command line, lets type the command <code>id</code>:</p>
<pre><code>sh-4.1$ id
uid=501(youruser) gid=501(youruser) groups=501(youruser)`</code></pre>
<p>The <code>id</code> command is a tool to show us how the system keeps track of us. From this we can see that according to the system, our user ID (or uid) is 501, and our group id is also 501.</p>
<pre><code>- Homework
- Run `id` in your own directory, then run
- Run `id -u root`
- use the `grep` command to find your uid in the `/etc/passwd` file</code></pre>
</body>
</html>

31
wiki/slrn.html
View File

@ -1,31 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>slrn</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">slrn</h1>
</header>
<p><code>slrn</code> is a news reader for [[Usenet]].</p>
<p>Documentation for slrn can be found at http://slrn.sourceforge.net</p>
<p>Tilde-specific slrn info is on http://tilde.club/~joeld/slrn.html</p>
</body>
</html>

221
wiki/ssh.html
View File

@ -1,221 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="author" content="benharri" />
<title>ssh</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<style type="text/css">
a.sourceLine { display: inline-block; line-height: 1.25; }
a.sourceLine { pointer-events: none; color: inherit; text-decoration: inherit; }
a.sourceLine:empty { height: 1.2em; }
.sourceCode { overflow: visible; }
code.sourceCode { white-space: pre; position: relative; }
div.sourceCode { margin: 1em 0; }
pre.sourceCode { margin: 0; }
@media screen {
div.sourceCode { overflow: auto; }
}
@media print {
code.sourceCode { white-space: pre-wrap; }
a.sourceLine { text-indent: -1em; padding-left: 1em; }
}
pre.numberSource a.sourceLine
{ position: relative; left: -4em; }
pre.numberSource a.sourceLine::before
{ content: attr(title);
position: relative; left: -1em; text-align: right; vertical-align: baseline;
border: none; pointer-events: all; display: inline-block;
-webkit-touch-callout: none; -webkit-user-select: none;
-khtml-user-select: none; -moz-user-select: none;
-ms-user-select: none; user-select: none;
padding: 0 4px; width: 4em;
color: #aaaaaa;
}
pre.numberSource { margin-left: 3em; border-left: 1px solid #aaaaaa; padding-left: 4px; }
div.sourceCode
{ }
@media screen {
a.sourceLine::before { text-decoration: underline; }
}
code span.al { color: #ff0000; font-weight: bold; } /* Alert */
code span.an { color: #60a0b0; font-weight: bold; font-style: italic; } /* Annotation */
code span.at { color: #7d9029; } /* Attribute */
code span.bn { color: #40a070; } /* BaseN */
code span.bu { } /* BuiltIn */
code span.cf { color: #007020; font-weight: bold; } /* ControlFlow */
code span.ch { color: #4070a0; } /* Char */
code span.cn { color: #880000; } /* Constant */
code span.co { color: #60a0b0; font-style: italic; } /* Comment */
code span.cv { color: #60a0b0; font-weight: bold; font-style: italic; } /* CommentVar */
code span.do { color: #ba2121; font-style: italic; } /* Documentation */
code span.dt { color: #902000; } /* DataType */
code span.dv { color: #40a070; } /* DecVal */
code span.er { color: #ff0000; font-weight: bold; } /* Error */
code span.ex { } /* Extension */
code span.fl { color: #40a070; } /* Float */
code span.fu { color: #06287e; } /* Function */
code span.im { } /* Import */
code span.in { color: #60a0b0; font-weight: bold; font-style: italic; } /* Information */
code span.kw { color: #007020; font-weight: bold; } /* Keyword */
code span.op { color: #666666; } /* Operator */
code span.ot { color: #007020; } /* Other */
code span.pp { color: #bc7a00; } /* Preprocessor */
code span.sc { color: #4070a0; } /* SpecialChar */
code span.ss { color: #bb6688; } /* SpecialString */
code span.st { color: #4070a0; } /* String */
code span.va { color: #19177c; } /* Variable */
code span.vs { color: #4070a0; } /* VerbatimString */
code span.wa { color: #60a0b0; font-weight: bold; font-style: italic; } /* Warning */
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">ssh</h1>
<p>authors:</p>
<p class="author"><a href="/~benharri/">~benharri</a></p>
</header>
<p><em>or, how to tell other computers to do cool things</em></p>
<hr />
<blockquote>
<p>all users are required to use an ssh keypair for login, or will be required to proceed with manual account recovery</p>
</blockquote>
<h2 id="tilde.club-details">tilde.club details</h2>
<p>for example, to connect to tilde.club, you can do:</p>
<pre><code>ssh user@tilde.club
mosh user@tilde.club</code></pre>
<hr />
<h2 id="intro">intro</h2>
<p>** if you just want to get right to a tutorial you can <a href="#how-to-make-an-ssh-key">skip over this background info</a>**</p>
<p>while <a href="https://tilde.club">tilde.club</a> is accessible on the web and features lovely web pages written by its users, most interaction with tilde.club takes place <strong>inside the machine</strong> that runs tilde.club as opposed to via web forms that have an effect from <strong>outside</strong> tilde.club’s computer.</p>
<p>this is what sets tilde.club apart from most other online communities. you connect directly to another computer from yours alongside other people and then write your web pages, chat, and play games all via text-based interfaces right on tilde.club’s computer.</p>
<p>prior to the web (which debuted in 1995) this is how pretty much all computer stuff got done. you connected directly to a machine (usually over a direct, physical phone line) and did your work there.</p>
<p>for a long time, people used a tool called <a href="https://en.wikipedia.org/wiki/telnet"><code>telnet</code></a> to connect to other computers. these days we use a tool called <strong>ssh</strong>.</p>
<p><code>ssh</code> is a text-based tool that provides a direct connection from your computer to another. ssh is an acronym that stands for secure shell. the <em>shell</em> part refers to the fact that it’s a text-based tool; we use the word shell to refer to a text-based interface that you give commands to. the <em>secure</em> part refers to the fact that, when you’re using ssh, no one can spy on your connection to another computer (unlike the old <code>telnet</code> command).</p>
<p><strong>why bother with all of this?</strong> passwords are really insecure and hard to manage. using keys makes life easier for you, fair user (your account is less likely to be hacked) and for me, your humble sysadmin (less administration than passwords).</p>
<hr />
<h2 id="how-to-make-an-ssh-key">how to make an ssh key</h2>
<p>SSH supports a handful of types of cryptographic keys. The most used are <a href="%3Chttps://en.wikipedia.org/wiki/RSA_(cryptosystem)%3E">RSA</a> and the more modern <a href="https://en.wikipedia.org/wiki/EdDSA#Ed25519">Ed25519</a>.</p>
<p>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 smaller withouth sacrificing security, so is best suited for embedded devices or machines with low resources. It’s supported on tilde (and really on any modern system) but you may find older systems which do not support it.</p>
<p>Below you’ll find instructions to generate either type (or both if you want).</p>
<p>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 <a href="https://man.openbsd.org/ssh-agent.1">ssh-agent</a> (a bit more complex)</p>
<p>pick your fighter: [<a href="#mac">mac</a>] | [<a href="#windows">windows</a>] | [<a href="#linux">linux</a>]</p>
<hr />
<h3 id="mac">mac</h3>
<h4 id="generating-your-keypair">generating your keypair</h4>
<ol type="1">
<li><p>open terminal (it’s in <code>/Applications/Utilities</code>)</p></li>
<li><p>create your .ssh directory:</p></li>
</ol>
<div class="sourceCode" id="cb2"><pre class="sourceCode bash"><code class="sourceCode bash"><a class="sourceLine" id="cb2-1" title="1"><span class="fu">mkdir</span> -m 700 ~/.ssh</a></code></pre></div>
<ol type="1">
<li>create your keys:</li>
</ol>
<p>for rsa keys:</p>
<div class="sourceCode" id="cb3"><pre class="sourceCode bash"><code class="sourceCode bash"><a class="sourceLine" id="cb3-1" title="1"><span class="fu">ssh-keygen</span> -t rsa -b 4096</a></code></pre></div>
<p>for dd25519 keys:</p>
<div class="sourceCode" id="cb4"><pre class="sourceCode bash"><code class="sourceCode bash"><a class="sourceLine" id="cb4-1" title="1"><span class="fu">ssh-keygen</span> -t ed25519 -a 100</a></code></pre></div>
<ol type="1">
<li><p>if you press enter to accept the defaults, your public and private key will be located at <code>~/.ssh/id_rsa.pub</code> and <code>~/.ssh/id_rsa</code> respectively (or <code>~/.ssh/id_ed25519.pub</code> and <code>~/.ssh/id_ed25519</code> if you chose ed25519 type)</p></li>
<li><p><code>cat ~/.ssh/id_rsa.pub</code> (or <code>cat ~/.ssh/id_ed25519.pub</code> for ed25519)</p></li>
<li><p>copy the output of the last command and paste it in the sshkey field on the signup form (or email it to <a href="mailto:root@tilde.club">~root</a> if you already have an account)</p></li>
</ol>
<h4 id="using-your-keypair">using your keypair</h4>
<p>once an admin approves your signup, you can join the tilde.club</p>
<ol type="1">
<li><p>open terminal (it’s in <code>/Applications/Utilities</code>)</p></li>
<li><p><code>ssh</code> to tilde.club:</p></li>
</ol>
<div class="sourceCode" id="cb5"><pre class="sourceCode bash"><code class="sourceCode bash"><a class="sourceLine" id="cb5-1" title="1"><span class="fu">ssh</span> username@tilde.club</a></code></pre></div>
<p>where username is your username (~benharri would use <code>ssh benharri@tilde.club</code>)</p>
<ol type="1">
<li>profit???</li>
</ol>
<hr />
<h3 id="windows">windows</h3>
<p>there are a couple options for using ssh on windows these days. i like to use <a href="https://git-scm.com">git bash</a>.</p>
<h4 id="generating-your-keypair-1">generating your keypair</h4>
<p>choose from any of the following options:</p>
<ul>
<li><a href="https://docs.microsoft.com/en-us/windows/wsl/install-win10">windows subsystem for linux</a></li>
<li><a href="http://www.msys2.org/">msys2</a></li>
<li><a href="https://git-scm.com">git bash</a></li>
</ul>
<ol type="1">
<li><p>open your new shell</p></li>
<li><p>create your .ssh directory</p></li>
</ol>
<div class="sourceCode" id="cb6"><pre class="sourceCode bash"><code class="sourceCode bash"><a class="sourceLine" id="cb6-1" title="1"><span class="fu">mkdir</span> .ssh</a></code></pre></div>
<ol type="1">
<li>create your keypair</li>
</ol>
<p>for rsa keys:</p>
<div class="sourceCode" id="cb7"><pre class="sourceCode bash"><code class="sourceCode bash"><a class="sourceLine" id="cb7-1" title="1"><span class="fu">ssh-keygen</span> -t rsa -b 4096</a></code></pre></div>
<p>for ed25519 keys:</p>
<div class="sourceCode" id="cb8"><pre class="sourceCode bash"><code class="sourceCode bash"><a class="sourceLine" id="cb8-1" title="1"><span class="fu">ssh-keygen</span> -t ed25519 -a 100</a></code></pre></div>
<ol type="1">
<li><p>if you press enter to accept the defaults, your public and private key will be located at <code>~/.ssh/id_rsa.pub</code> and <code>~/.ssh/id_rsa</code> respectively (or <code>~/.ssh/id_ed25519.pub</code> and <code>~/.ssh/id_ed25519</code> if you chose ed25519 type)</p></li>
<li><p><code>cat ~/.ssh/id_rsa.pub</code> (or <code>cat ~/.ssh/id_ed25519.pub</code> for ed25519)</p></li>
<li><p>copy the output of the last command and paste it in the sshkey field on the signup form (or email it to <a href="mailto:root@tilde.club">~root</a> if you already have an account)</p></li>
</ol>
<h4 id="using-your-keypair-1">using your keypair</h4>
<p>once an admin approves your signup, you can join the tilde.club</p>
<ol type="1">
<li><p>open terminal (it’s in <code>/Applications/Utilities</code>)</p></li>
<li><p><code>ssh</code> to tilde.club:</p></li>
</ol>
<div class="sourceCode" id="cb9"><pre class="sourceCode bash"><code class="sourceCode bash"><a class="sourceLine" id="cb9-1" title="1"><span class="fu">ssh</span> username@tilde.club</a></code></pre></div>
<p>where username is your username (~benharri would use <code>ssh benharri@tilde.club</code>)</p>
<ol type="1">
<li>profit???</li>
</ol>
<hr />
<h3 id="linux">linux</h3>
<p>there are a lot of linux distros, but <code>ssh</code> and <code>ssh-keygen</code> should be available in almost all cases. if they’re not, look up how to install ssh for your distro.</p>
<h4 id="generating-your-keypair-2">generating your keypair</h4>
<ol type="1">
<li>make sure you have a <code>~/.ssh</code> directory</li>
</ol>
<div class="sourceCode" id="cb10"><pre class="sourceCode bash"><code class="sourceCode bash"><a class="sourceLine" id="cb10-1" title="1"><span class="fu">mkdir</span> -m 700 ~/.ssh</a></code></pre></div>
<ol type="1">
<li>create your keys</li>
</ol>
<p>for rsa keys:</p>
<div class="sourceCode" id="cb11"><pre class="sourceCode bash"><code class="sourceCode bash"><a class="sourceLine" id="cb11-1" title="1"><span class="fu">ssh-keygen</span> -t rsa -b 4096</a></code></pre></div>
<p>for ed25519 keys:</p>
<div class="sourceCode" id="cb12"><pre class="sourceCode bash"><code class="sourceCode bash"><a class="sourceLine" id="cb12-1" title="1"><span class="fu">ssh-keygen</span> -t ed25519 -a 100</a></code></pre></div>
<ol type="1">
<li><p>if you press enter to accept the defaults, your public and private key will be located at <code>~/.ssh/id_rsa.pub</code> and <code>~/.ssh/id_rsa</code> respectively (or <code>~/.ssh/id_ed25519.pub</code> and <code>~/.ssh/id_ed25519</code> if you chose ed25519 type)</p></li>
<li><p><code>cat ~/.ssh/id_rsa.pub</code> (or <code>cat ~/.ssh/id_ed25519.pub</code> for ed25519)</p></li>
<li><p>copy the output of the last command and paste it in the sshkey field on the signup form (or email it to <a href="mailto:root@tilde.club">root@tilde.club</a> if you already have an account)</p></li>
</ol>
<h4 id="using-your-keypair-2">using your keypair</h4>
<p>once an admin approves your signup, you can join the tilde.club</p>
<ol type="1">
<li><p>open a terminal (this depends on your distro)</p></li>
<li><p><code>ssh</code> to tilde.club:</p></li>
</ol>
<div class="sourceCode" id="cb13"><pre class="sourceCode bash"><code class="sourceCode bash"><a class="sourceLine" id="cb13-1" title="1"><span class="fu">ssh</span> username@tilde.club</a></code></pre></div>
<p>where username is your username (~benharri would use <code>ssh benharri@tilde.club</code>)</p>
<ol type="1">
<li>profit???</li>
</ol>
<hr />
<p>this tutorial is based on and uses parts of <a href="https://github.com/tildeclub/tilde.club/blob/master/docs/ssh.md">the tilde.club ssh primer</a> and <a href="https://tilde.town/wiki/ssh.html">the tilde.town ssh guide</a>.</p>
</body>
</html>

30
wiki/sshfs.html
View File

@ -1,30 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>SSHFS</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">SSHFS</h1>
</header>
<p>With <code>sshfs</code> you can mount your tilde directory as a drive.</p>
<p>See http://tilde.club/~jeffbonhag/sshfs.txt for a tutorial.</p>
</body>
</html>

32
wiki/tin.html
View File

@ -1,32 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>tin</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">tin</h1>
</header>
<p>tin is a threaded NNTP and spool based UseNet newsreader for a variety of platforms.</p>
<p>http://www.tin.org/</p>
<p>it’s under active development, with a last release on October 3, 2014. It is installed on <code>tilde.club</code>, and should be invoked as <code>tin -r</code> to read from the remote news spool. Use <tab> to go to the next unread article and <code>w</code> to write a new article.</p>
<p>if you have <code>tin</code> on your local box and can do [[ssh port forwarding]], you can read news using it. (details forthcoming).</p>
</body>
</html>

47
wiki/tmux.html
View File

@ -1,47 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>tmux</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">tmux</h1>
</header>
<p>TMUX IS THE BEST. Here’s a super basic primer.</p>
<p>to start a new session, type <code>tmux new -s tildemux</code>.</p>
<p>A yellow bar will appear at the bottom of your terminal. You’re now in TMUX!</p>
<p>TMUX has sessions, windows, and panes. Each of these things will have a terminal in it. If you actually typed what I told you to earlier, you’ll be in a session named <code>tildemux</code>. That session has one window, <code>0</code>. That window has one pane, also named <code>0</code>. (Computers start counting at 0, not 1.)</p>
<h2 id="windows">windows</h2>
<p>Your tmux bar should look like:</p>
<p><code>[tildemux] 0:bash*</code></p>
<p>…which means that you’re in a session named <code>tildemux</code>, which has a window <code>0</code>, running the command <code>bash</code>. <code>*</code> means that window 0 is active, and the pane running bash is currently active.</p>
<p>To create a new window within this session, type <code>PREFIX c</code>. PREFIX?!? By default, it’s <code>control-b</code>. Now you should see:</p>
<p><code>[tildemux] 0:bash- 1:bash*</code></p>
<p><code>1:bash*</code> means you’re in a pane running <code>bash</code> inside window 1. To change back to pane 0, type <code>PREFIX 0</code>. The <code>*</code> should be back on <code>0:bash</code>.</p>
<p>Run a cool interactive command, such as <code>htop</code> (to see how many of system resources we’re eating up) or <code>vim</code> (to write some awesome webpages). Your tmux status bar should update to <code>0:&lt;name of the current process&gt;</code>. So now instead of saying <code>bash</code> it will say <code>htop</code> or <code>vim</code>.</p>
<h2 id="panes">panes</h2>
<p>Panes are great. TMUX panes let you run more than one terminal inside your one, actual terminal. To “split” a new pane, <code>PREFIX &quot;</code>. That makes a horizontal split. You’ll notice there are now two panes open one on top of the other. <code>PREFIX %</code> makes a vertical split, for side-by-side panes. Did I mention that panes are great?</p>
<p>To move between panes in the current window, use <code>PREFIX &lt;up,down,left,right&gt;</code>. That’s right, the arrow keys.</p>
<h2 id="more">more</h2>
<p>I not the best writer or teacher. Just google anything that doesn’t make sense.</p>
<p><a href="http://robots.thoughtbot.com/a-tmux-crash-course">Or take a look at this tmux guide</a></p>
<p>But definitely use tmux.</p>
</body>
</html>

31
wiki/tunnelblick.html
View File

@ -1,31 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>Tunnelblick</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">Tunnelblick</h1>
</header>
<p><code>tunnelblick</code> is an application for your Mac that allows you to configure and manage VPN sessions. You can use this e.g. if you are connecting to tilde.club via a network that does not allow high UDP ports; with a properly configured tunnel, you can still run [[mosh]] as your shell and keep on truckin.</p>
<p>https://code.google.com/p/tunnelblick/</p>
<p>To find a VPN endpoint, see the [[VPN Gate]] project.</p>
</body>
</html>

32
wiki/vimrc.html
View File

@ -1,32 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>.vimrc file</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">.vimrc file</h1>
</header>
<p>The file <code>.vimrc</code> in your home directory has instructions for [[vim]] to load every time it runs. Customizations go there.</p>
<p>For instance, you might want to use [[Markdown]] to edit files that end in <code>.md</code>. The system default for some reason is to treat these as [[Modula-2]] files, though we don’t have a Modula-2 compiler running (yet). So the contents of <code>.vimrc</code> should read</p>
<p><code>au BufRead,BufNewFile *.md set filetype=markdown</code></p>
<p>For more suggestions in deep depth on how to set up your <code>.vimrc</code> please read <a href="http://dougblack.io/words/a-good-vimrc.html">this tutorial from Doug Black</a>.</p>
</body>
</html>

40
wiki/wiki.html
View File

@ -1,40 +0,0 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="author" content="benharri" />
<title>how to contribute to this wiki</title>
<link rel="stylesheet" href="/style.css">
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<a href="/wiki/">&lt; back to wiki home</a>
<header>
<h1 class="title">how to contribute to this wiki</h1>
<p>authors:</p>
<p class="author"><a href="/~benharri/">~benharri</a></p>
</header>
<ol type="1">
<li><p>grab a copy of the site’s source code</p>
<p>git clone https://github.com/tildeclub/site tilde.club &amp;&amp; cd tilde.club/wiki</p></li>
<li><p>make a new article or update an existing one (only change the markdown source)</p></li>
<li><p>generate the wiki pages. you need to be in the wiki directory. run <code>./build-wiki.sh</code> to create the html.</p></li>
<li><p>submit the code via a PR on github or with git-send-email(1) to root@tilde.chat see <a href="https://git-send-email.io">git-send-email.io</a> for more info on how to use it. if you’re working locally on tilde.club, you won’t have to configure anything; git will use the system’s sendmail to handle the email.</p></li>
<li><p>profit???</p></li>
</ol>
<p>ask on irc if you have questions!</p>
</body>
</html>

0
wiki/pandoc-template.html → wiki/wiki.tmpl
View File