# self-hosted "status" things

## finger
=> urn:ietf:rfc:1288 RFC (use this link if your computer can dereference urn:ietf:rfc URIs.)
=> https://tools.ietf.org/html/rfc1288 https back up link to the finger RFC
put the status into a plan file.

## webfinger
=> urn:ietf:rfc:7033
=> https://tools.ietf.org/html/rfc7033
put the status into your webfinger response somehow
as a property? or maybe a link... a link would allow you to use a URI as your status
and if you don't want it to load another page just have it be a data URI
yep.
link rel=status
=> https://www.iana.org/go/rfc8631
should hopefully work.
```
wget -qO- https://thebackupbox.net/.well-known/webfinger?resource=acct:epoch@thebackupbox.net \
  | jq -r '.links[] | if .rel == "status" then .href else empty end'
```
this will return a URI for the status of epoch@thebackupbox.net
the 'status' rel for links in a webfinger is specified in...
=> https://tools.ietf.org/html/rfc8631#section-6.4
which is vague enough I'm gonna use it this way.

## twtxt
=> https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html

## matrix status
=> https://matrix.org/docs/spec/client_server/latest#get-matrix-client-r0-presence-userid-status
(this needs an access token to view so... not very helpful for public status info)

## xmpp status
I dunno yet.
probably needs some access token like matrix does

## fmrl
here, read some shit:
=> https://thebackupbox.net/cgi-bin/fmrl-client.cgi
=> https://git.thebackupbox.net/fmrl_spec/