Comment by 🐙 norayr
Re: "I’m pondering about self hosting a small gopher hole on my…"
there's old good chroot, back in decades ago people were running servers in chroots when they weren't sure. and chroots could be very small.
if the binary was statically compiled it basically needed just a kernel and its own configs.
but i am much more interested in how do you run a gopher bbs for meshtastic?
can i guess? you have a program that presents itself as socks proxy for your gopher browser. then instead of proxying it talks to a meshtastic device. on the other side a similar program gets a request and passes it to a gopher server.
i am writing such a program, have it half baked, need to concentrate and continue. how do you do this? can you explain what you do?
Apr 20 · 3 weeks ago
1 Later Comment
🚀 astrowat [OP] · Apr 20 at 11:24:
I’m using MeshGopher (not mine - https://github.com/jmansell90/meshgopher) which has a very basic gopher server built in, the builtin client chats via DM and will chunk text to get around the 200 byte limit. I was thinking about using gophernicus to add a bit of dynamic content (weather, etc).
Original Post
I’m pondering about self hosting a small gopher hole on my raspberry pi. It’s mostly for #meshtastic (I’m using it as a BBS), but I’d like to show it off to people without a mesh of their own. Would it be a bad idea to open port 70 on my firewall? I’m intentionally avoiding any cgi so the surface area of attack in smallish.