Some terminal emulators – e.g., kitty – can show images inline. I use `toot` and `tooi` to read the Fediverse in kitty, and the images are there alright.
Also, a service port is always qualified by its protocol. There are separate port namespaces for each IP protocol that uses ports. "8483" is not a service port, until you spell it out:
Me too, but not for usenet. The server-to-server protocol is a low ceremony, high observability, standardised and battle-proven gossip-flood protocol with hierarchical channelisation and robust mature tooling, ideal for eventually-consistent distribution of telemetry and control messages over a node mesh of uncertain reliability up to global scale. What's not to like?
I'm sorry, it's only for people I know personally. Also, it only holds minor Usenet hierarchies like the vestigial dk.*.
It's not too difficult to set up INN2, and it's easy to get an external feed. It uses minimal resources, and there is hardly any maintanance once it has been installed and configured.
Does anything happen in the dk. hierarchy anymore. Last time I check, probably 10 years ago, it was either spam or one crazy person.
It's a bit of a shame, I really want something like dk.city.copenhagen and dk.city.copenhagen.noerrebro to replace Facebook groups. That's probably never going to happen, it's seems like a missed opportunity.
reply