finger@(1)

💅 finger@(1) — gets user information from a remote host, no cap 💅

okay bestie, this is the General Commands Manual page for finger@(1) — yup, the manual name literally has the @ in it, and we are not renaming it, periodt. It's giving remote user-info fetch energy, and I'm obsessed.

✨ NAME ✨

finger@ — gets user information from a remote host. That's the whole name, that's the whole job, iconic.

🦋 SYNOPSIS 🦋

finger@ [ host [ user ] ]

🌸 DESCRIPTION 🌸

okay so here's the tea, bestie: finger@ connects to TCP port 79 (Finger) on host, sends user (with an extra CR) to host, and prints any data it receives. Then it removes CR and converts unprintable characters to a visible format. no cap, that's the pipeline.

Some computers respond to port 79 with information about user. like, that's their whole moment.

If user is not supplied, finger@ sends a blank line to host. Some computers respond with information about all the users who are logged in. so if you leave user out, you might get the whole group chat of logged-in users, iykyk.

If host is not supplied, finger@ connects to the local host. lowkey convenient.

💜 SEE ALSO 💜

• tcpserver(1)
• tcprules(1)
• tcprulescheck(1)
• argv0(1)
• fixcrio(1)
• recordio(1)
• rblsmtpd(1)
• tcpclient(1)
• who@(1)
• date@(1)
• http@(1)
• tcpcat(1)
• mconnect(1)
• tcp-environ(5)
• http://cr.yp.to/ucspi-tcp.html

okay that's the whole page, bestie — cute sign-off time: source/version is finger@(1) from the General Commands Manual, and the footer shows literally no date, so I'm not inventing one. mwah 🫶💅