I probably heard of gopher in middle school but also dismissed it since ‘oh something not immediately accessable from web brower’ as we used internet explorer (yet i was also big into muds at the time gofigure.) My real introduction was roughly when I had gotten my cr48 chromebook.
At the time I was on a metered connection, and I wanted to see what this little browser in a box could do that streached past the usual. This lead me to floodgap and project overbite, and while I only occasionally poke at the gophersphere and would like to see both clients with a more friendly festure set (if nothing else being able to bookmark would be nice, but I am wholly unhappy with android clients lack of user adjustability in rendering,) I see gopher as a promising low bandwidth option that could comfortably live beside the more commercial web, as it takes comparitively next to nothing resource-wise, and while exceedingly limited? It is also dead simple.
I imagine many of my complaints could be addressed by clients that can do things like render image links as images, allow for parsing of markdown or at least a subset of, And othr formatting bits and bobs alongside actual festures like bookmarking and intelligant handing offof whatneeds to render the thing if it doesnt inherently knowhow the file works.
If nothing else, the fact is it’s text centric and my eyesight is only getting worse over time is appealing.
Fine, it’s limited and cannot natively do forums, but those limits surely can be worked around. I like the idea of it getting a bigger foothold in the retro community if nowhere else due to the relatively lightweight nature of it.