android finger client

(I added a p.s. to this post)

I was in deedum and saw a finger link, like:

finger://thebackupbox.net/epoch

and it made me happy that someone actually used a link instead of saying

"finger epoch@thebackupbox.net"

(yes, I know weird things make me happy)

but when I went to open it, deedum didn't know what it was

and I didn't have any finger clients installed.

:[

I looked for android finger clients and only found two. One from

like, 2010, and the other being:

https://github.com/sirjofri/fingerlist

fingerlist almost did what I wanted. It didn't have finger URI support

and it also didn't have anything in its manifest to let other apps

know that it was able to handle finger URIs.

So I installed android studio to see if it'd be as much of a pain

as I was hoping it wasn't.

Took me a bit to get into a good work loop of write, build, test

using python3 -m http.server to re-download it to my phone after each

apk build.

My computer is new enough to run the studio, but it has a really hard

time trying to run a phone emulator at the same time.

Anyway, I have an apk that seems to work how I want now. :)

So, have some links to the apk and the source.

/~epoch/fingerlist.apk

https://thebackupbox.net/~epoch/fingerlist.apk

git://git.thebackupbox.net/fingerlist

https://git.thebackupbox.net/fingerlist/

gemini://git.thebackupbox.net/fingerlist/

p.s.

saw this

gemini://ruario.flounder.online/journal.gmi

mention this page. that's a good point of using a gopher client

to act as finger client. one of the things I'd tested the finger client on

was a whois request.

finger://thebackupbox.net:43/AS4141

and after reading about using gopher for finger, I figured I might as

well test it the other way around.

finger://thebackupbox.net:70/now-playing.txt

This one comes in handy, because the finger client will auto-reload,

and I can see what is playing on my computer using it.

I know there's probably some more "request\r\n" protocols that we're missing.

anything that silent eats requests and returns a response might work too.

daytime protocol.

finger://thebackupbox.net:13/

echo

finger://thebackupbox.net:7/this-gets-echod

All those should be reachable from the internet now too.

I expect qotd should work too. (port 17)

I seem to have not forwarded my finger port to the internet until just now too.

was just testing what this app does with percent encoded characters.

looks like it decodes them :]

This /should/ mean it can be used to send whatever we want to a server and

wait for a response. we should be able to do dumb stuff like this:

finger://thebackupbox.net:80/GET%20/cgi-bin/title.cgi%3fREMOTE_ADDR%20HTTP/1.1%0d%0aHost:%20thebackupbox.net%0d%0a