# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 5
# self = https://watcher.sour.is/conv/n66yp3q
@movq What happened to your Gopher server?
@mckinley I shut it off. It became increasingly difficult to decide where to put which content. Does it go into the phlog, the weblog, just twtxt, Mastodon, something else, … ? I wanted to reduce the number of “channels” that I use. And Gopher is the hardest for people to access – not from a technical point of view, of course, but _regular_ clients basically don’t support it anymore. Aside from a small “elite” group, nobody could access it (and I’d rather not have to point people to Gopher proxies all the time).
I’d rather focus on keeping my website compatible with older/retro clients. Not having a forced redirect to HTTPS and sticking to a simple layout is mostly enough.
Netscape 4.07 on WfW 3.11:
[](https://movq.de/v/10948b8de6/ns4.jpg)
Netscape 2.02 on OS/2 Warp 4 (only 16 colors in QEMU at the moment):
[](https://movq.de/v/10948b8de6/ns2.jpg)
(Those older clients tend to extend HTTP/1.0 a bit by sending a Host: header. Without that, my webserver wouldn’t be able to find the correct vhost.)
Really, having my _exact same website_ accessible with those browsers feels more rewarding than having to resort to Gopher. 🤔
@mckinley I shut it off. It became increasingly difficult to decide where to put which content. Does it go into the phlog, the weblog, just twtxt, Mastodon, something else, … ? I wanted to reduce the number of “channels” that I use. And Gopher is the hardest for people to access – not from a technical point of view, of course, but _regular_ clients basically don’t support it anymore. Aside from a small “elite” group, nobody could access it (and I’d rather not have to point people to Gopher proxies all the time).
I’d rather focus on keeping my website compatible with older/retro clients. Not having a forced redirect to HTTPS and sticking to a simple layout is mostly enough.
Netscape 4.07 on WfW 3.11:
[](https://movq.de/v/10948b8de6/ns4.jpg)
Netscape 2.02 on OS/2 Warp 4 (only 16 colors in QEMU at the moment):
[](https://movq.de/v/10948b8de6/ns2.jpg)
(Those older clients tend to extend HTTP/1.0 a bit by sending a Host: header. Without that, my webserver wouldn’t be able to find the correct vhost.)
Really, having my _exact same website_ accessible with those browsers feels more rewarding than having to resort to Gopher. 🤔
@mckinley I shut it off. It became increasingly difficult to decide where to put which content. Does it go into the phlog, the weblog, just twtxt, Mastodon, something else, … ? I wanted to reduce the number of “channels” that I use. And Gopher is the hardest for people to access – not from a technical point of view, of course, but _regular_ clients basically don’t support it anymore. Aside from a small “elite” group, nobody could access it (and I’d rather not have to point people to Gopher proxies all the time).
I’d rather focus on keeping my website compatible with older/retro clients. Not having a forced redirect to HTTPS and sticking to a simple layout is mostly enough.
Netscape 4.07 on WfW 3.11:
[](https://movq.de/v/10948b8de6/ns4.jpg)
Netscape 2.02 on OS/2 Warp 4 (only 16 colors in QEMU at the moment):
[](https://movq.de/v/10948b8de6/ns2.jpg)
(Those older clients tend to extend HTTP/1.0 a bit by sending a Host: header. Without that, my webserver wouldn’t be able to find the correct vhost.)
Really, having my _exact same website_ accessible with those browsers feels more rewarding than having to resort to Gopher. 🤔
@movq That makes a lot of sense. I agree it's probably a better use of time to maintain a nice, simple website.