updated my finger client to support finger:// URIs

going to email the author of this draft spec, which was written 26 years ago. together, I believe we can get it finalized and continue the revival

· · Web · 2 · 2 · 6

He emailed me back: “ I note that there is still a strong chance of failure, but I suspect there is a moderate chance of success.”

Let’s do this

@aw i never really understood the finger protocol. is it basically a way to query /about-type information at a specific resource?

@cblgh well, technically, it’s a simple protocol where you send a string and get back some plain text, so you could call it a gopher precursor since it doesn’t specify gopher maps. All it has is a main directory. Culturally, the resources are people names, and the text contains info about them, and their plan. In my case, I let the gopher server answer the finger port. 😅 @aw

@cblgh @aw finger originates from a time where lots of people had accounts on the same Unix system.

With 'finger username' you could get infos about another user including room or telephone number. Until today, /etc/passwd has gecos fields (see for exactly that purpose. Try running finger on your own user.

Additionally, you could query .plan and .project files which contained things people were working on. Like old school mastodon :D

Sign in to participate in the conversation

Revel in the marvels of the universe. We are a collective of forward-thinking individuals who strive to better ourselves and our surroundings through constant creation. We express ourselves through music, art, games, and writing. We also put great value in play. A warm welcome to any like-minded people who feel these ideals resonate with them.