I just ordered a Mojito 🍹 because I got ZNC to run from my Raspberry Pi, all the way across the country, opened the correct ports, did the port forwarding, configured it, and then launched it, and configured ERC/ZNC to run automatically in Emacs. 👩🏼‍💻

All while tanning by the pool.

#linux #irc #znc #server #erc #Emacs

I'm so pleased with myself that imma be insufferable for a little while. 🤣

I'm currently configuring #znc on my #raspberrypi and got it working from the outside (cuz, obvs, I'm not at home). I hope to get it working in the next hour or two so that I can use #irc in #erc with #Emacs. 👩🏼‍💻

Sooooo. Installed #tailscale on a VM. The only thing that really runs on it is #irssi connecting to my #znc (which runs in the cloud).

Before tailscale: average cpu use 0.05%

After tailscale: 1.15%.

Ok, it still isn't much, but that is quite the jump.

It adds up. I think I'll stick to wireguard on the edge.

I've been running #thelounge for #IRC on my SBC, and it's generally worked well, except that it holds the chat history in memory and the SBC is running out. I'm wondering if I should switch to #ZNC, if it will use less memory, or if I should just give up on IRC persistence.

@h3artbl33d I host some email (moved my own to mailbox.org), a family #Nextcloud instance, #NNCP relay, #Ampache server, personal #Matrix server, #MoinMoin wiki, personal website, #gopher server, my #Wordpress blog, some nonprofit websites, personal #ikiwiki instance, various ssh tunnels, #APRS gateway, my #ZNC instance, mailing list archives, #weather station

It's a multi-layered approach: Bitlbee connects to Mastodon (and other services), and I connect to Bitlbee via #ZNC. All home on a local Raspberry Pi.

@charly J'utilise l'austère mais vénérable #Irssi dans un terminal détachable #tmux sur un serveur (pour ne pas perdre de messages).
Mon ~/.irssi/config : https://git.sourcephile.fr/julm/home-julm.git/blob/HEAD:/.config/nixpkgs/home/irssi/config
Avec qqs plugins installés via le home.nix parent.

Dans le genre, #WeeChat est pas mal aussi.
Sinon en GUI, #HexChat je dirais. Avec éventuellement un bouncer (#ZNC ou #Bip). Tu peux aussi passer par un serveur #XMPP ou #Matrix qui a une passerelle #IRC. Et https://webchat.freenode.net peut dépanner aussi.

I finally ditched #ZNC. It had three new releases since I last checked, and two of them fixed RCE. I now only have #XMPP, and thanks to #biboumi, I can just reach all my IRC channels from XMPP like native MUCs. And now I even have history, across my devices, thanks to #MAM!

The only reason I didn't do it earlier is that #biboumi crashed on #SPARC64 as soon as it would throw and catch an exception. But I finally found the reason: It linked against botan2, which used a different libstdc++.

My #raspberryPi keeps crashing the past couple of days :(

I noticed the problem after installin #znc (the #IRC bouncer) but I don't know if that's related or if it just made me notice more.

IRC question:

(After getting advice on here) I'm using #weechat as my #IRC client and connecting via #znc running on my #raspberryPi. I've been logging out with `/quit`, but I just noticed that, for some reason, this isn't freeing up my nick on freenode—it's still showing me logged in and won't let me have that nick again. So, two questions:

- How do I tell freenode that I've logged out so I can get my nick back?
- How do I stop this from happening again in the future?

@puffinux Oh, this is fun—I'll try to stick to your format:
Programs I use with #linux (#arch) as my OS:

#dwm + dmenu (display manager)
#qutebrowser (browser)
#neovim (text editor)
#vim + qutebrowser (mastodon)
#weechat + #znc (IRX)
#keybase + vim (encrypted chat)
#mutt (email)
#feh (image viewer)
#scrot (screenshots)
#simpleTerminal (terminal emulator)
#tmux (terminal multiplexer)
#mupdf (PDF viewer)
#pass + #passgen (password manager)

#FOSS #FLOSS #openSource #freeSoftware

@shellkr @chozron @hund@linuxrocks.online

What are the advantages/disadvantages of using #tmux/#abduco versus using a bouncer (like #znc) to keep a persistent connection? They seem pretty similar as far as I can tell, except that I can keep #IRC in the same (local) tmux session if I use a bouncer.

But I'm totally open to the idea that I'm missing something key!

I’m quite happy with #Terraform for small deployments but don’t have a sense of how to scale up.

How do people structure their Terraform deployments? Separate repos? One big un? Then how are the directories laid out?

I’d been thinking I’d type `make` and deploy all servers at once, the way I would for a client. Maybe that’s not actually desirable. When I’m working on the #ZNC bouncer I don’t want to mess with #Tor relays. Or do I? Should I be able to remake the world with one command?

datacenters do not imbue computers with special powers. if you own a desktop less than a decade old, congrats! you already own a server more than capable of hosting any and/or all of these:

- #gogs
- #nextcloud
- #pleroma
- #rocketchat
- #discourse
- #prestashop
- #funkwhale
- #hugo
- #radicale
- #standardnotes
- #prosody
- #wallabag
- #wordpress
- #etherpad
- #dokuwiki
- #ttrss
- #kanboard
- #pixelfed
- #loomio
- #pihole
- #taiga
- #kodi
- #searx
- #homeassistant
- #znc

(for free, forever)

I am setting up a couple #Tor relays and automating everything so it is reproducible. The host OS is #FreeBSD since that's the only BSD #DigitalOcean offers.

I've got existing automation which provisions a #ZNC via #Terraform / #Chef. ZNC runs inside #Docker. This all works great though Chef annoys me in some ways.

For the Tor boxen I'm considering two changes:
- Swap Docker for BSD jail
- Swap Chef for #Ansible or a straight shell script.

Thoughts?