(DIR) web -2.0 -- root
(DIR) ingles -- special pages
Осенние...краски....Бу...⣀⣠⣴⣶⣾⣿⣿⣿⣶⢶⡴⣔⢄⡀...утылка...к...обеду....Мне...х
очется...ласки....Я....⠔⣔⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣶⣵⣂⢄......к...матери...еду....Осенн
ие...краски....Буты...⢀⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣟⣦⠢...ылка...к...обеду....Мне...х
очется...л .к...матери...еду....О
сенние...к Ph1o6 3ntry 170718_0904 тылка...к...обеду....М
не...хочет ски....Я...к...матери.
..еду....Осенние.....⣴⢿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⢿⣿⣿⣿⣿⣷⢿⣟⠽⡪.....краски....Бутылка...к
...обеду....Мне......⢜⡿⢿⠿⠝⠻⢻⣿⣿⣿⣿⡟⠛.⠈⠢⠋⠉⠙⠊⠩⠐⠐....хочется...ласки....Я...
к...м краски....Бутылка
...Я. #gopher ду....Осенние...к
...Я. ду....Осенние...к
раски Do you read all these tl;dr ramblings? ..обеду....Мне...
хочет OK, here you go. ...матери...еду..
хочет ...матери...еду..
As I see contemporary definition of gopher - it is stateless web
protocol which enforces content without extra design and graphics,
perfectly suitable for remote terminal sessions. Limitations, such as
"one link per line", make its representation utterly standardized.
On personal note, I dislike embedded pictures - you may see well
aknowledged example of such attitude at hacker news @ ycombinator. What
I like is "information retrieval system" concept: think of wikipedia,
manual pages, library queries.
Is gopher expandable? Surely, even safely expandable in terms of gopher
- you may add new element types and expand element arguments with extra
tabs. I don't remember anything substantial from single time I reviewed
gopher+ proposal and don't think following notes will intersect with
gopher+.
So. Does gopher lack anything?
=== Markup
You may deliver some markdown/pandoc/asciidoc dialect and put
representation task on client entirely. This way you get math listings
and whatever else.
CONCLUSION: nothing new here, no gopher improvement.
=== Internal navigation
Imagine manpage. You read it, encounter something like "see at
`Patameters expansion' section". So you search for "parameters
expansion", when you could just follow anchored link (it's reason you
may in general follow link in gopher instead of typing link URL using
curl).
Of course you may break document into sections, even on the fly. But
anchoring is still good feature, e.g. to follow bulletin board-styled
replies tree.
Another simple approach will be addressing TOC by line number, which
doesn't really need any gopher improvement.
CONCLUSION: anchor can be prolly implemented on top of "i" element
accompanied by any other link element adding anchor name.
=== Fold/collapse
This one is really preferred feature. Think of discussion threads
(hacker news again). And again, it can be much simple approach like
VIM's foldmethod "marker" using "{{{" and "}}}" per line. These
fold/unfold markers could be hidden as link extra arguments.
Other way of answering is asking it different way: what gopher lacks to
let it implement particular sites.
CONCLUSION: extra argument for "i" element
=== Search suggestion
It's certainly a must-have feature. You surely may have separate page
with each search-type element returning suggestions for what you need.
What's desired is some behaviour of search field when it will return
suggestions, possibly wrapped in fold/collapse elements. That will come
handy with multiple field search.
CONCLUSION: to be proposed; probably again - extra argument on search
element denoting "suggestion requests allowed", this obviously needs
extra client support.
=== Multiple field search
Not sure if it makes sense to maximize compatibility with regular
gopher, but required elements are "input" and "button" with grouping
argument.
CONCLUSION: do it yourself.
=== Final words
Why did I put here these thoughts? To say hai 2 thx1138 and share what
I personally want within provided vision of gopher. What I tried to
describe is terminal oriented web with most uniform design/layout
(clear text). And it can be much compatible with base gopher. Maybe if
someone work around set of features, which are required to provide more
feature-rich user experience on gopher (gopher is serious business),
maybe take some necessary interactive elements - assuming there are
about 200 active gopher servers, it won't be hard to introduce
community approved next step gopher.
Other important improvements will be authentication and encryption.
Maybe server side popups also?
Last note: IIRC gopher line is length limited so possibly all extra
arguments to element require compact synthax.
раски....Бутылка....⠐⣟⣿⣿⣿⣿⣿⣿⣿⣿⣿⣲⢉⣎⣽⣿⣿⣿⣿⣿⣿⣿⢟⣛⠕⠄......к...обеду....Мне...
хочется...ласки......⢨⣿⣿⣿⣿⣿⣿⣿⣿⣿⣯⢗⡻⣽⣿⣿⣿⣿⣿⣿⣿⣫⠩.....Я...к...матери...еду..
(QRY) Leave comment
..обеду....Мне...хочетс...⠩⢷⣿⣾⣶⣶⣤⡥⣖⠜⡠⠳.⠉...ся...ласки....Я...к...матери
...еду....Осенние...крас...⠈⢿⣿⣿⣿⣿⢟⢔⠉⠒...ски....Бутылка...к...обеду....М
Осенние...краски....Бу...⣀⣠⣴⣶⣾⣿⣿⣿⣶⢶⡴⣔⢄⡀...утылка...к...обеду....Мне...х
очется...ласки....Я....⠔⣔⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣶⣵⣂⢄......к...матери...еду....Осенн
Post categories:
(DIR) #gopher
ие...краски....Буты...⢀⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣟⣦⠢...ылка...к...обеду....Мне...х
очется...ласки.......⢀⢬⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣟⠧⡣⡀....Я...к...матери...еду....О
не...хочется...лас...⣰⢜⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷⣳⢷⣪⢖⠬⠄...ски....Я...к...матери.
..еду....Осенние.....⣴⢿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⢿⣿⣿⣿⣿⣷⢿⣟⠽⡪.....краски....Бутылка...к
...обеду.. очется...ласки....Я...
к...матери 2017/2065 // ulcer@sdf.org ие...краски....Бутылка
...к...обе .не...хочется...ласки.
...Я...к...матери...⢐⣾⣷⣮⣭⣥⣤⣼⣯⣿⣿⢇.⠢⣽⣾⣮⣭⣼⣤⣴⣾⣿⣻⣿⢈...и...еду....Осенние...к
раски....Бутылка....⠐⣟⣿⣿⣿⣿⣿⣿⣿⣿⣿⣲⢉⣎⣽⣿⣿⣿⣿⣿⣿⣿⢟⣛⠕⠄......к...обеду....Мне...
хочется...ласки......⢨⣿⣿⣿⣿⣿⣿⣿⣿⣿⣯⢗⡻⣽⣿⣿⣿⣿⣿⣿⣿⣫⠩.....Я...к...матери...еду..
..Осенние...краски...⢈⢽⣿⣿⣿⣿⣯⣿⣿⣿⡲⠥⡆⢺⣿⣿⣿⣿⣿⣟⢟⠢⠁...и....Бутылка...к...обеду
....Мне...хочется.....⢈⢫⢯⢿⣿⣮⡹⠟⠁...⢸⣿⣿⣿⠿⣽⡩⠂⠂.....ласки....Я...к...матери
...еду....Осенние.....⢀⠄⣓⢹⢿⣿⣿⡧...⢄⠬⡛⠓⠯⢫⡣⣊⡀⠂.....краски....Бутылка...к..
.обеду....Мне...хоч...⠐⠔⡞⣆⠉⣙⣙⡛⠋.⠁..⡀⣠⡺⣵⢭⡪⠔...чется...ласки....Я...к...м
атери...еду....Осенни...⠩⢚⣿⣿⣿⠿⠛⠛⠊⢀⠉⠮⢒⡚⢗⡓⠤...ие...краски....Бутылка...к.
..обеду....Мне...хочетс...⠩⢷⣿⣾⣶⣶⣤⡥⣖⠜⡠⠳.⠉...ся...ласки....Я...к...матери
...еду....Осенние...крас...⠈⢿⣿⣿⣿⣿⢟⢔⠉⠒...ски....Бутылка...к...обеду....М
не...хочется...ласки....Я....⠈⠙⠊⠈......к...матери...еду....Осенние...кр
(DIR) GTFO -- special pages
(DIR) vector hypertext -- root
Page views: 10