IRC Server as Tor Hidden Service on OpenBSD
xn--gckvb8fzb.com
xn--gckvb8fzb.com
Yea yea I'm old, but dammit in "my day", it was easier to communicate and the "tech" didn't get in your way.
IRC was basically a "done product" and new features were usually spearheaded via "scripts" from users with a need.
It seems the "new features" in discord are product-managers trying to justify their job and keep adding feature-upon-feature and making it more of a xmass-tree-met-a-coder-on-crack situation !
I wished there was a product manager (I'm looking at you Spotify, netflix etc) that said, ok these next few quarters we are going to reward ourselves for 'REMOVING Features'.
We need the area of "Bring your own client" to really take off.
Ok i'm done venting (one should not comment before coffee on HN) :P
I was on euIRC and basically "grew up" with those services.
[1]: https://libera.chat/
Who else started using it in 1996, and never stopped? Lots! Who else never touched any of the social media sites. Lots!
Discord is a frustrating UI experience for me on all levels, so I just can't bring myself to even open the software.
IRC was and is awesome.
Caveat: use it for casual socializing. If you need tools for risky things like political activism, business, security, etc - don't use IRC, for many reasons.
I find it hasn't changed all that much over the years, if at all, so some should be warned - it does remind me of the early wild-west days, which I love.
List all the channels you're in.
> I wished there was a product manager (I'm looking at you Spotify, netflix etc) that said, ok these next few quarters we are going to reward ourselves for 'REMOVING Features'.
What is needed is to avoid adding bad features and avoid removing good features.
> We need the area of "Bring your own client" to really take off.
Yes, I agree. Allow that you can bring your own client, with your own features.
Make a protocol and file formats that is simple (but not too simple) and capable of better end user controlling, and then make the implementations, too.
(Also, some features can be made optional if that would help, too.)
True, but reading change logs (I really like reading them), i very very seldom see "Removed feature xyz" but I do see "added abc X 10..n". I'm pretty sure no-one gets promoted by removing features in the current work-job-boss-promotion-setup.
1. Pinned messages. Yes, to an extent Channel topics can serve this way, but the limited space in IRC leads to "Use !jabberbot help for a list of commands, and !jabberbot faq so we don't ban you for asking the same thing for the 40th time." Slack and Discord suffer from people who don't read pinned messages but it can at least help deflect repeat stuff.
2. Threading. In some contexts, it makes sense to take a follow-up loosely "private" in the sense of not messaging to everyone else in the channel.
Other than these IRC is superior in basically every other way.
However, never, EVER change your root login shell in OpenBSD. You've just opened a can of worms. Set up doas for that, and keep using zsh as your regular user if you want. Simple /etc/doas.conf:
permit :wheel
Use nvi from packages (it's nvi2 actually, base vi it's nvi) instead of nvim, much faster. It's basically base vi with UTF-8 support. Run :exusage and :viusage from within nvi. Also, my ~/.exrc: set showmode ru ts=2
set sw=2
set iclowerAt a behavioral level, you don't want to make root's environment so comfortable that you use it more than you should. By keeping it vanilla /bin/sh you encourage admins to log off and do their usual work in their usual environment.
At a technical level, as soon as you start customizing the root env you open a lot of doors for dynamically linked dependencies to whatever shell+goodies you switch to, which expose root to potential vulnerabilities.
You also increase the risk that updates will break root in some obscure way, which will not have been tested by the OS Q/A process.
man afterboot
I've always felt setting up the server is the easy part. The more complicated bit is setting up the clients, especially for friends who aren't as tech savvy, or just don't want to bother figuring out all the moving parts.
I see you mention client setup in passing at the end, but do you have a suggestions for a more complete guide for setting up things client-side? I've yet to find one.
https://irssi.org/documentation/help/otr/
https://github.com/onezero1/xchat-otr
There's more listed here from the people who built and designed the libraries:
https://otr.cypherpunks.ca/software.php
NB, OTR is old and I can't vouch for its crypto, do your research if for some reason you're connecting to an irc server with a hostile admin where you absolutely have to exchange compromising information. (Duh)
It isn't that bad tho when its your friends IRC server.
That said, I'm told almost the majority of traffic observed through tor is IRC. For botnet control.
"Everywhere you go, even when you're not actively using your phone, it's still listening." - Edward Snowden
With a SIM card, you are by definition always tracked and identified individually. It's how the technology is designed to function. You can remove the SIM card, harden your OS, randomize your Wifi MAC but at that point you aren't really using a _cell phone_ anymore.
They require crutches and compromises to be made to participate in the internet. Usually this is in the form of a incorporated entity doing the hand holding.
There are areas where residential internet is fast and reliable, but if you’re building a service that sucks on bandwidth/energy/throughput constrained links, you’re building a service that’s not viable for tons of users.
The idea that to make something that works for those people we have to make systems that are worse for people with fast internet is a false dichotomy. We can (and should) make services and systems that work well for everybody.