this post was submitted on 18 Sep 2024
773 points (99.6% liked)
Microblog Memes
5726 readers
2406 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
To be honest, I wouldn't have been much impressed by the HTML specifications, either. An open source alternative for gopher? Oh, how cute. Be sure to tell all your geek friends.
Gopher wasn't open source? There were linux clients.
https://en.wikipedia.org/wiki/Gopher_(protocol)#Decline
It's probably not quite right to call it an open source alternative, though. I don't think that gopher or anything was established in a monopolistic way, but that was before my time. Besides, the internet was all universities back then.
It's true that Gopher never really went anywhere. It was convenient for what it was and it had Veronica (a basic search engine) which made it useful. But hyperlinks were a killer feature.
Berners-Lee didn't come up with that idea, though, did he? I thought he got the idea from Ted Nelson's Project Xanadu.
Gopher itself is spec'd out in RFC-1436. It's not a particularly difficult protocol to implement. It's easier than HTTP/1.1 (though not necessarily pre-1.0 versions; those are basic in an under-designed way, and I'd say the same about Gopher). I don't know if that licensing fee claim holds up. People may have been worried about it at the time, but UMN never had a patent on it or anything, and RFC's are public. If there were fees charged, it'd be the creators themselves charging them.