Serving Gossips: Difference between revisions

Revision as of 16:21, 18 January 2026

afternoon timeline

hour	session
14h00-14h30	🖐️ your first TMUX session
14h30-15h00	🗨️ presenting tmux2web2print, a tool made by Kaa
15h00-15h15	⏳ small break
15h15-16h00	🖐️ collective TMUX pedagogy
16h00-16h15	🗨️ sharing how it went
16h15-17h00	🖐️ web2print zine of our session

what is SSH

From wikipedia, we learn that:

The Secure Shell Protocol (SSH Protocol) is a cryptographic network protocol for operating network services securely over an unsecured network. Its most notable applications are remote login and command-line execution.

In 1995, Tatu Ylönen, a researcher at Helsinki University of Technology in Finland designed the first version of the protocol (now called SSH-1) prompted by a password-sniffing attack at his university network. The goal of SSH was to replace the earlier rlogin, TELNET, FTP and rsh protocols, which did not provide strong authentication nor guarantee confidentiality. He chose the port number 22 because it is between telnet (port 23) and ftp (port 21).

What do we mean? I am on my computer, using it's keyboard and it's screen, but when I SSH, it's like i am on another computer: the server I SSHed into. So even though I am not typing stuff on the server by plugin a keyboard, or screen on it (maybe it's in a datacenter and I don't have access to it physically even...), I can use that computer, through my computer, using SSH.

Communal servers can be said to be like shared space, a colocation. In order to feel good in a colocation we need shared rules as much as shared agency. However if we connect at many on a server there isn't a chat room to share links or explain things to each others. For shared rules and shared agency, we resort to:

naming the folder/file in a way that convey a meaning, and standard naming practice, like what's hosted is it /var/www/, and /home/ contain one folder per users with their 'home' directory. Things like this already induce that some spaces are more intimate and other more shared.

what is TMUX

(15min)

astral projection but we merged our souls

collaboration become "character granular", also we are the same person.

TMUX was created in ... by ...

your first TMUX session

(20min)

small exercice to write, one big session started by us.

(put basic command so students can follow along)

we show 2 things:

kaa show a command
doriane show a command
we asked if a student want to show a command.

tmux2web2print: serving gossips

(20min)

What are the server gossiping about?

teletype and RTTY, telex machine, the first "terminal" print recipe instead of having a screen
feminist server, documentation is hard, can we have documentation generated on the go, with all the organic chaos that comes from it as part of the pedagogy
tmux hook activating using bash script
HTML/CSS are generated immediatly on the served folder to acces it online
we can print them using ctrl+p !

The zine capture what is send, so if you write things in the prompt but remove it, it's not going to be there. Think about the outcome, it's nice to use echo: if you type some interesting comment collectively in the prompt zone, someone can just write echo in front and send it so the interesting comment is saved in the zine later.

quick starting guide

...

styling and printing the fanzine

...

tmux cheatsheet

...

merged soul pedagogy

by group of max 4 persons.

1. you start a tmux session together.

  (put back the command to do so)

2. once we made sure that the setup is working for everyone. you have to first select at least 3 command that some people of the group don't know about and at least one person know about. 3. the groups split in space. 4. then teach them to each others by showing how they work inside of a tmux session. warning 30min goes fast, try to not spend more than 10min on a command.

moving around

cd
ls

displaying stuff

echo
cat
tree
figlet

grabbing stuff

grep
history

changing authority

chmod
chown

network

ifconfig
ping
traceroute
curl

yours!!!

...

zine printing and CSS!

@@ Line 22: / Line 22: @@
 == what is SSH ==
-(15min)
+* [https://en.wikipedia.org/wiki/Secure_Shell Secure Shell on wikipedia]
+* [[SSH cookbook | SSH on xpub wiki]]
-astral projection: i am on my computer but it's like i am on another computer
+<blockquote>
+From wikipedia, we learn that:
+* The Secure Shell Protocol (SSH Protocol) is a cryptographic network protocol for operating network services securely over an unsecured network. Its most notable applications are remote login and command-line execution.
+* In 1995, Tatu Ylönen, a researcher at Helsinki University of Technology in Finland designed the first version of the protocol (now called SSH-1) prompted by a password-sniffing attack at his university network. The goal of SSH was to replace the earlier rlogin, TELNET, FTP and rsh protocols, which did not provide strong authentication nor guarantee confidentiality. He chose the port number 22 because it is between telnet (port 23) and ftp (port 21).
+</blockquote>
-communal server are like shared space, a colocation!
+[[File:Remote-login-is-a-lot-like-astral-projection.png | 350px | thumb | right | ]]
-in order to feel good in a colocation we need shared rules as much as shared agency.
-however if we connect at many on a server there isn't any chat room to share thing or explain things to each others.
-we resort to
-* naming the folder/file in a way that
+What do we mean? I am on my computer, using it's keyboard and it's screen, but when I SSH, it's like i am on another computer: the server I SSHed into. So even though I am not typing stuff on the server by plugin a keyboard, or screen on it (maybe it's in a datacenter and I don't have access to it physically even...), I can use that computer, through my computer, using SSH.
-SSH was created in ... by ...
+Communal servers can be said to be like shared space, a colocation.
+In order to feel good in a colocation we need '''shared rules''' as much as '''shared agency'''.
+However if we connect at many on a server there isn't a chat room to share links or explain things to each others.
+For '''shared rules''' and '''shared agency''', we resort to:
+* naming the folder/file in a way that convey a meaning, and standard naming practice, like what's hosted is it <code>/var/www/</code>, and <code>/home/</code> contain one folder per users with their 'home' directory. Things like this already induce that some spaces are more intimate and other more shared.
+*
 == what is TMUX ==