tootik is a federated nanoblogging service for the small internet.
tootik allows people to participate in the fediverse using their Gemini, Gopher or Finger client of choice and makes the fediverse lighter, more private and more accessible. tootik's interface strips content to bare essentials (like text and links), puts the users in control of the content they see and tries to "slow down" the fediverse to make it more compatible with the slower pace of the small internet.
It's a single executable that handles both the federation (using ActivityPub) and the frontend (using Gemini) aspects, while sqlite takes care of persistency. It should be lightweight and efficient enough to host a small community even on a cheap server, and hopefully, be easy to hack on.
tootik implements only a small subset of ActivityPub, and probably doesn't really conform to the spec.
My initial inquiries in the #gopher and #gemini world reveal a surprising number of parallels. Anyone who is enthusiastic about an Internet away from the colorful, blinking surveillance industry is probably more willing to explore new avenues in this area. Although "gopher" is the older protocol, I sympathize with the new "gemini" - also for personal reasons 😉 With the #Linux#Terminal program #amfora I will now take a closer look there.
What platforms were used in the 80s up to about 1993 or 1994 for Internet servers? It can be #FTP, #Gopher, #telnet, #USENET, the #OldWeb, or anything else that was on the Internet in that era.
My research indicates Solaris was very popular for web servers until Linux took over, and so I suspect it (and SunOS before it) was very popular for the Internet in general, but I'd like to hear from anyone with this sort of experience.
Stop Electron, stop using a browser as if it was an Operating System!!! Go #terminal#cli#TUI use your OS, not the browser for everything! And be liter, more ethical, your computer will love you! Use #Gemini#gopher#usenet#matrix#fediverse on TUI apps #vim#neovim as your text/IDE #mpv for videos and more... !!!
Rather, it's the space full of little #telnet#BBS, #gopher, little websites, game servers, mumble servers, IRC servers, NNTP servers, etc running on home boxes and such.
It's underneath all the cruft. Blinking and chugging along and existing nicely.
In my quest for an easier emacs on ramp, I made an org file for adding templated elisp source block sections to itself, which tangles to an elisp file, to be loaded on startup.
If you have time, please report any issue, bug, memory problem, crash and anything strange :)
In the archive there is a read-me file with many informations and hints.
Is there a service for viewing HTTPS pages via the #gopher protocol, or should I make it?
Also, is there a gopher reverse proxy? I have two gopher services already and I want to map them to different domains or paths but I want them all on port 70.
Made various fixes and optimizations, I also got rid of a Guru that sometimes was crashing the system. I think there is still something within the #BSDSocket library because if I try to call a proc while doing network stuff sooner or later the system ... BOOM! 😁
Anyway I can only thanks @TopazRabbit for this game-changer lib.
My #Gopher client for #Amiga is getting configuration files 😁
You can see the 'color scheme' file and the 'key map' file, but I still need another one for the misc options and fine tuning like buffer sizes, color depth, etc...