Revista textoplano nro.1: gopher://texto-plano.xyz:70/1/revista

Bloody hell 🤦‍♂️🤦‍♂️

$ jq -r --arg host "gopher.mills.io" '. | select(.request.host==$host) | "\(.request.client_ip) \(.request.uri) \(.request.headers["User-Agent"])"' mills.io.log-au | while IFS=$' ' read -r ip uri ua; do asn="$(geoip -a "$ip")"; echo "$asn $ip $uri $ua"; done | grep -E '^45102.*' | sort | head
45102 47.251.70.245 /gopher.floodgap.com/0/feeds/democracynow/2015/Oct/14/0 ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"]
45102 47.251.84.25 /gopher.floodgap.com/0/feeds/voaheadlines/2014/Mar/09/voanews.com-content-article-1867433.html ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3F0692937396569A52972EB2 ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3F9657307A96569A52974634 ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3FB7571C7896569A529E6603 ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3FB75EF81296569A529E6617 ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3FC6564ADB96569A5A9E660C ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]

Ken Thompson vuela un MiG: gopher://texto-plano.xyz:70/0/~peron/docs/ken_thompson_mig.txt

@andros@twtxt.andros.dev Broke on me for having alt-urls I think 🥲

twtxt---profile-layout: Wrong type argument: char-or-string-p, ("https://aelaraji.com/twtxt.txt" "gemini://box.aelaraji.com/twtxt.txt" "gopher://box.aelaraji.com/0/twtxt.txt")

(I keep thinking that going back go Gopher or Gemini might be a good idea at this point. They don’t care about that, probably. 🫣)

Gopher in Ineternet Explorer 3 works better than in this Dillo LoL

Maybe try somekind version of the Lynx for gopher?

Yes everything fine from it: gopher://shibboleths.org/5/win31/irc.zip Screen of IRC client for Win311: https://dropmefiles.com/DD4t9

I love finding content on Gopher because it’s devoid of paid favoritism, be it in ads or search results.

Gopher can’t be discover because it’s already 34 years old. From Windows 3.11 again…

@f1ee6 Hello, for my part, I’m discovering Gopher :-). Really cool to give a little life to old computers. For the moment, I access Gopher from an old Mac G3/OS9, lynx on linux on an I3 laptop and for fun, Gopher from my old Palm PDA with Overbite. Lots of good things to all, friendship from France ;-)

Gopher Farm: Like Animal Farm, but more succinct.

Who invent gopher, commi?!

Once again, the insane commi are writing to in American gopher, through an American browser, to American server. lol

EdgeGuard Update:

I am now in a position where I’m no longer having any ports open on my firewall at the Mills DC. 🥳 All services (Gopher, SMTP, IRC, SSH, HTTP) are being proxied through my edge network 💪

At least Minnesota won their bowl game. Go Gophers!

Browsing X and fell down a gopher hole. Love it. ✌️ -Steve Galbincea

Happy 2025! My first gopher experience.

This is my first time on gopher. Very cool!

HAPPY NEW YEAR – learning about gopher

thanks man!!! love seeing ppl use gopher -@levelsio

owow. Gopher is still here!

I think best browser for Gopher is Blue skies

Happy New Year colleagues on behalf of the team gopher://shibboleths.org ! :)

Magical.fish looks good in Pocket Gopher.

I mostly use Pocket Gopher on Android, and sometimes Doggy Dog.

Man, I love Gopher. I also love that I can use Termux to get Lynx and Gopher on the go. As much as I like Floodgap, Overbite on Android needs more features (like downloads).

People say http is an outdated protocol from 1992, a bad copy of Gopher. I want to try it sometime.

Coming from https://gopher.floodgap.com/gopher

Read Mark 10,11.12 in gopher://rbfh.de and turn to Jesus, if you are a sinner!

Atualizei meu gopher com meus primeiros passos usando o Guix, gopher://vaphorhole.xyz/1/~orahcio

But first, I gotta setup a propper page for my … well, I still dunno what we call one’s web and gopher pages in this space. but let’s set those up!

Can’t wait to go through the whole web and gopher directories and see what everyone’s up to

Hello from PANDA TOPS-20, using gopher client written in C,

Where all Gophers folks

Very glad for Pocket Gopher app. keeping me connected to gopher space!

Thank you, @eapl.me@eapl.me! No need to apologize in the introduction, all good. :-)

Section 3: I’m a bit on the fence regarding documenting the HTTP caching headers. It’s a very general HTTP thing, so there is nothing special about them for twtxt. No need for the Twtxt Specification to actually redo it. But on the other hand, a short hint could certainly help client developers and feed authors. Maybe it’s thanks to my distro’s Ngninx maintainer, but I did not configure anything for the Last-Modified and ETag headers to be included in the response, the web server just already did it automatically.

The more that I think about it while typing this reply, the more I think your recommendation suggestion is actually really great. It will definitely beneficial for client developers. In almost all client implementation cases I’d say one has to actually do something specifically in the code to send the If-Modified-Since and/or If-None-Match request headers. There is no magic that will do it automatically, as one has to combine data from the last response with the new request.

But I also came across feeds that serve zero response headers that make caching possible at all. So, an explicit recommendation enables feed authors to check their server setups. Yeah, let’s absolutely do this! :-)

Regarding section 4 about feed discovery: Yeah, non-HTTP transport protocols are an issue as they do not have User-Agent headers. How exactly do you envision the discovery_url to work, though? I wouldn’t limit the transports to HTTP(S) in the Twtxt Specification, though. It’s up to the client to decide which protocols it wants to support.

Since I currently rely on buckket’s twtxt client to fetch the feeds, I can only follow http(s):// (and file://) feeds. But in tt2 I will certainly add some gopher:// and gemini:// at some point in time.

Some time ago, @movq@www.uninformativ.de found out that some Gopher/Gemini users prefer to just get an e-mail from people following them: https://twtxt.net/twt/dikni6q So, it might not even be something to be solved as there is no problem in the first place.

Section 5 on protocol support: You’re right, announcing the different transports in the url metadata would certainly help. :-)

Section 7 on emojis: Your idea of TUI/CLI avatars is really intriguing I have to say. Maybe I will pick this up in tt2 some day. :-)

@eapl.me@eapl.me here are my replies (somewhat similar to Lyse’s and James’)

1. Metadata in twts: Key=value is too complicated for non-hackers and hard to write by hand. So if there is a need then we should just use #NSFS or the alt-text file in markdown image syntax ![NSFW](url.to/image.jpg) if something is NSFW

2. IDs besides datetime. When you edit a twt then you should preserve the datetime if location-based addressing should have any advantages over content-based addressing. If you change the timestamp the its a new post. Just like any other blog cms.

3. Caching, Yes all good ideas, but that is more a task for the clients not the serving of the twtxt.txt files.

4. Discovery: User-agent for discovery can become better. I’m working on a wrapper script in PHP, so you don’t need to go to Apaches log-files to see who fetches your feed. But for other Gemini and gopher you need to relay on something else. That could be using my webmentions for twtxt suggestion, or simply defining an email metadata field for letting a person know you follow their feed. Interesting read about why WebMetions might be a bad idea. Twtxt being much simple that a full featured IndieWeb sites, then a lot of the concerns does not apply here. But that’s the issue with any open inbox. This is hard to solve without some form of (centralized or community) spam moderation.

5. Support more protocols besides http/s. Yes why not, if we can make clients that merge or diffident between the same feed server by multiples URLs

6. Languages: If the need is big then make a separate feed. I don’t mind seeing stuff in other langues as it is low. You got translating tool if you need to know whats going on. And again when there is a need for easier switching between posting to several feeds, then it’s about building clients with a UI that makes it easy. No something that should takes up space in the format/protocol.

7. Emojis: I’m not sure what this is about. Do you want to use emojis as avatar in CLI clients or it just about rendering emojis?

Coffee and Gopher with Windows 95, what could be better?

For .onion gophersites you can install Orbot App on android for VPN, than go by lynx or overbite app to gopher://magical.fish, then you can open the .onion site of magical.fish.

I can open any Gopher except Onion from Windows95. What am I doing wrong?

Lynx can’t do gophers and bitreich has no fallback. Great…

Simplified twtxt - I want to suggest some dogmas or commandments for twtxt, from where we can work our way back to how to implement different feature like replies/treads:

1. It’s a text file, so you must be able to write it by hand (ie. no app logic) and read by eye. If you edit a post you change the content not the timestamp. Otherwise it will be considered a new post.

2. The order of lines in a twtxt.txt must not hold any significant. The file is a container and each line an atomic piece of information. You should be able to run sort on a twtxt.txt and it should still work.

3. Transport protocol should not matter, as long as the file served is the same. Http and https are preferred, so it is suggested that feed served via Gopher or Gemini also provide http(s).

4. Do we need more commandments?

How’s everyone? I go on Gemini/gopher for a hobby. Still learning.

Solution found for viewing TLS 1.3 sites in Win95, more details gopher://shibboleths.org/1/browsers98

Read the Bible in English. gopher.rbfh.de

Publicado no site Vaporhole tutorial gopher e git.

Atualizaei meu gopher com um artigo sobre a saída do Plasma para o mundo dos tiling managers no wayland, gopher://vaporhole.xyz:70/1/~orahcio

@doesnm@doesnm.p.psf.lt No.

iirc in twtxt v2 it starts prohibited

This is not true. There are no issues supporting fetching feeds via Gemini/Gopher. This is totally fine. What will likely happen is “recommendations” and “drawbacks of using Gemini/Gopher”

Happy Gopher, fridayspace :)