2/

#acctURI has a way of representing user accounts on other hosts — sort of similar to the #fingerProtocol

For example —

acct:reiver%40mastodon.social@calckey.social

(Notice that the "@" in "reiver@mastodon.social" gets percent-encoded as "%40".)

#WebFinger uses acct-URIs.

And the #Fediverse used WebFinger.

This is how you could represent a user on one Fediverse instance being used on another Fediverse instance without necessarily having to create a new account.

You guys can #finger me now at musky@sevenmusky.one

#fingerprotocol #fingerme #selfhosting #smolnet #lowtech

I have now a page on the #Finger protocol : emmanuel@flounder.online

#FingerProtocol

@pmevzek

Using a DNS SRV record instead of a DNS TXT record —

To make it so you can change the TCP-port and host of a finger-protocol request —

Seems like a reasonable modification to what I was proposing.

( #dns #dnsTxt )

( #finger #fingerHole #fingerProtocol #fingerverse )

( #smallInternet #smallNet #smallWeb )

( #smolInternet #smolNet #smolWeb )

1/

The finger-protocol could make use of DNS TXT records.

You could use it to change the TCP-port connected to for a finger-request.

You could use it to change the host connected to for a finger-request.

This has a lot of potential!

🧵

( #dns #dnsTxt )

( #finger #fingerHole #fingerProtocol #fingerverse )

( #smallInternet #smallNet #smallWeb )

( #smolInternet #smolNet #smolWeb )

1/

The finger-protocol could make use of DNS TXT records.

You could use it to change the TCP-port connected to for a finger-request.

You could use it to change the host connected to for a finger-request.

This has a lot of potential!

🧵

( #dns #dnsTxt )

( #finger #fingerHole #fingerProtocol #fingerverse )

( #smallInternet #smallNet #smallWeb )

( #smolInternet #smolNet #smolWeb )

@orangeacme

The way you are talking — I suspect you didn't #finger see when it was popular —

(Maybe you were too young. Or you are old enough, but just didn't get exposed to it for some reason.)

So — I can add some information — as not only was I on the Internet when #fingerProtocol was popular — I was a heavy finger user back in the 1990s —

@orangeacme

One big difference between #finger and #webFinger is —

The output from a #fingerProtocol response is human-legible.

The output from a WebFinger response is — NOT human-legible.

The output from a WebFinger response is — programmer-legible and machine-legible (but not human legible).

@orangeacme

Some other relevant tags for your thread:

https://fosstodon.org/@orangeacme/109483350342825311

#finger #fingerHole #fingerProtocol #fingerverse

#smallInternet #smallNet #smallWeb

#smolInternet #smolNet #smolWeb

@orangeacme

#finger has an origin at least going back to 1971.

#IETF #RFC742 was written to document the existing #fingerProtocol , as it was (implicitly) defined by software.

I.e., finger had been around and was evolving AT LEAST 6 years before RFC-742 was published.

( #fingerHole #fingerverse )

3/

This quotation from the GNU #finger documentation suggests that —

Image support had already (historically) been added to the #fingerProtocol .

And keep in mind that GNU finger is one of the historic finger-protocol clients — and that it was last updated October 15th, 1992. But that the GNU finger code-base is way older than that.

( #fingerHole #fingerverse )

3/

This quotation from the GNU #finger documentation suggests that —

Image support had already (historically) been added to the #fingerProtocol .

And keep in mind that GNU finger is one of the historic finger-protocol clients — and that it was last updated October 15th, 1992. But that the GNU finger code-base is way older than that.

( #fingerHole #fingerverse )

2/

Quotation continued —

(GNU #finger is one of the historic #fingerProtocol clients — last updated October 15th, 1992.)

“[…] The conversion of graphic data from one format to another is done through GNU Finger; no site need know where or how such images are stored on any other site to be able to display those images. You should ask your system administrator to find out whether he has chose to include this functionality on your network.”

https://www.gnu.org/software/finger/manual/html_mono/finger.html

( #fingerHole #fingerverse )

2/

Quotation continued —

(GNU #finger is one of the historic #fingerProtocol clients — last updated October 15th, 1992.)

“[…] The conversion of graphic data from one format to another is done through GNU Finger; no site need know where or how such images are stored on any other site to be able to display those images. You should ask your system administrator to find out whether he has chose to include this functionality on your network.”

https://www.gnu.org/software/finger/manual/html_mono/finger.html

( #fingerHole #fingerverse )

1/

A quote from the GNU finger documentation —

(GNU #finger is one of the historic #fingerProtocol clients — last updated October 15th, 1992.)

“An optional and currently unsupported feature is passing of graphic images. This is built on the new protocol. A user at site A (e.g. MIT) may see the picture of a user at site B (e.g. UCSB), by typing a finger request. […]”

https://www.gnu.org/software/finger/manual/html_mono/finger.html

( #fingerHole #fingerverse )

1/

A quotation from the GNU finger documentation —

(GNU #finger is one of the historic #fingerProtocol clients — last updated October 15th, 1992.)

“An optional and currently unsupported feature is passing of graphic images. This is built on the new protocol. A user at site A (e.g. MIT) may see the picture of a user at site B (e.g. UCSB), by typing a finger request. […]”

https://www.gnu.org/software/finger/manual/html_mono/finger.html

( #fingerHole #fingerverse )

3/

If a concept of files & directories were added to the #fingerProtocol then — it would need to be attached to the user, not the host.

I.e.,:
"joeblow/a/b/c.txt" + "\r\n"

"joeblow/a/b/c.txt@example.com" + "\r\n"

Or from the command line:

finger joeblow/a/b/c.txt@example,com

finger joeblow/a/b/c.txt@example,com@changelog.ca

( #finger #fingerHole #fingerverse #HTTP )

3/

If a concept of files & directories were added to the #fingerProtocol then — it would need to be attached to the user, not the host.

I.e.,:
"joeblow/a/b/c.txt" + "\r\n"

"joeblow/a/b/c.txt@example.com" + "\r\n"

Or from the command line:

finger joeblow/a/b/c.txt@example.com

finger joeblow/a/b/c.txt@example.com@changelog.ca

( #finger #fingerHole #fingerverse #HTTP )

2/

But (unlike #HTTP) with the #fingerProtocol — you can actually make a request on a user.

Ex:
"joeblow" + "\r\n"

And:
"joeblow@example.com" + "\r\n"

So, what if you wanted to extend the finger-protocol, and add a concept of files & directories‽ —

( #finger #fingerHole #fingerverse )

2/

But (unlike #HTTP) with the #fingerProtocol — you can actually make a request on a user.

Ex:
"joeblow" + "\r\n"

And:
"joeblow@example.com" + "\r\n"

So, what if you wanted to extend the finger-protocol, and add a concept of files & directories‽ —

( #finger #fingerHole #fingerverse )