121–130 of 137 posts
all said, duck yeah, irssi remains one of my fav pieces of software. watching the rise of slack and so forth has been quite amusing to me, as a longtime irc chick. my barometer for new chat networks being good or not is "can i somehow use it in irssi?"
awaiting a good and proper discord-irc bridge to make up for all the funtimes tryin to make twitch/ustream/hitbox chat work via irc.
BitchX forever!! :P (seriously though, not really, I could never figure out how to actually use that client)
BitchX isn't that hard, it's got all the ircII stuff plus a few changes to how you do a few things. I used graphical IRC clients for years until I started working more and switched around devices too much. I'm not a fan of ZNC/BNC, so now I have a few VPS's for plex and storage that I just have irssi running inside of a screen and it works great. I stopped using BX after a few IRC friends badgered me into switching t…
Earlier quoted context omitted.
palaver (iOS) and ZNC do the server-time playback quite nicely as long as you use up to date versions. (and also push notifications) ircv3 specification is shaping up to have even better capabilities there too.
I use Android
This release fixes a couple of vulnerabilities, some of them found via fuzzing: https://irssi.org/security/irssi_sa_2017_01.txt I hope I'll find time to write up a blogpost how I fuzzed irssi later.
https://blog.fuzzing-project.org/55-Fuzzing-Irssi-with-Perl-...
Happy to see IRC still going strong. While I switched to irccloud.com a couple years ago--persistent session is so nice, especially for mobile!--I used CLI clients for years before. Amusing blast from the past: back in the 90's I worked at General Magic, and wrote my own IRC client [1] for our handheld devices. I attached a Metricom wireless modem to the bottom of mine and could be on IRC from anywhere ; it was like…
Quassel and Smuxi.im are GUI-based ones, where you can start them one one computer and connect from another. (I've never tried them, so can't say how they fare.)
I used ZNC for a while, that's a "pure bouncer" that just connects to your irc network and then you connect your client of choice to your ZNC. Simple and easy to set up, but not very featureful.
I recently switched to Weechat, which comes with a nice CLI interface, as well as letting you connect from regular IRC clients, or from special Weechat-clients (their own protocol which gives some more control I suppose). There's an HTML5 client https://www.glowing-bear.org/ that a lot of people like. I use the Android client https://github.com/ubergeek42/weechat-android#weechat-androi... a lot, it's very nice, though from my laptop I connect from Emacs's built in client (M-x erc). I run Weechat on a Raspberry Pi 1 that I had lying around, just connected it to my router, ran "apt install weechat weechat-plugins tmux" and set "tmux new-session -d weechat -s chat" to run on startup, and added a relay: http://www.weechat.org/files/doc/stable/weechat_user.en.html...
Earlier quoted context omitted.
I wanted to use irccloud, but many IRC networks ban it in a blanket policy against "browser-based clients" because they can't get an IP address to ban if you misbehave.
That's not true, if the network is ipv6 aware, each user gets his own ipv6 with irccloud. Not to mention the hardcoded usernames. I'm against irccloud (you're paying to be man in the middled) but they definitely sorted the "can not ban" problem.
The problem with things like irccloud from a network operator perspective isn't that it's difficult to distinguish between users. It's that these systems often subvert protections the network has deemed necessary.
Imagine example.net runs an open proxy scanner on anyone that connects. They find this reduces abuse considerably. If (e.g. irccloud) either 1) doesn't pass the originating user's ip 2) isn't trusted to pass the originating user's ip or 3) doesn't run a similar open proxy scanner, then example.net's open proxy scanner solves nothing.
1) isn't always technically trivial. 2) isn't for us to decide and 3) is probably never going to happen as the network will likely always be ahead.
If you do manage to solve 1&2 between a mitm & a network then awesome. The problem is that this requires buy in from both sides. Just because irccloud.com support it doesn't mean it will automatically work on any irc network you try and connect to.
Earlier quoted context omitted.
For those who don't know, the Open Build Service is a project mainly maintained by the openSUSE community. Aside from building all of the packages for openSUSE and SUSE's enterprise distributions, it also can build Ubuntu, Debian, Arch Linux, Red Hat and Fedora packages. It also has a collaboration system which is the primary way that openSUSE and SUSE Linux Enterprise are built. [Disclaimer: I work for SUSE and am a…
Is there a similar service (paid perhaps) to build for macOS?
> Support for any OS and architecture due to the use of VM's for building the packages. This includes Windows (experimental) and Mac OS X (if anyone would want to work on that).
Earlier quoted context omitted.
Why but just run a bouncer like znc? I even have push notifications when I get tagged or a add a special keyword.
> Why but just run a bouncer > like znc Same reason I stopped running my own mailserver and mutt; there are a limited number of things I have bandwidth for, and I'd much rather pay a tiny amount of money for someone else to Just Do It, and do it right. Also mobile.
With Weechat, as long as you manage to add a server from the UI and then `/relay add ssl.irc 8000`, you typically just need a script that runs `tmux new-session -d weechat` on startup. And it has mobile clients.
Happy to see IRC still going strong. While I switched to irccloud.com a couple years ago--persistent session is so nice, especially for mobile!--I used CLI clients for years before. Amusing blast from the past: back in the 90's I worked at General Magic, and wrote my own IRC client [1] for our handheld devices. I attached a Metricom wireless modem to the bottom of mine and could be on IRC from anywhere ; it was like…
Here are the highlights: