Irssi 1.0.0 Released
irssi.org
irssi.org
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 living in the future! /s
I even have push notifications when I get tagged or a add a special keyword.
I can get push notifications to my phone with a ZNC module so that's not really the hold up.
Requires Quassel server
ircv3 specification is shaping up to have even better capabilities there too.
I remember having problems with this in the past using ZNC and separate mobile/laptop clients.
> Why but just run a bouncer
> like znc
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.
In addition, there are a lot of nice little channels out there that are just fun to hang out in.
Other than that, I just see people mention channels sometimes and I join them.
In these channels there's people who've been there for almost 20 years. Sadly I parted ages ago from the channels I was chatting in the 90's. But I guess they're still there.
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.
IE: sid655585@<unique_ipv6>
or: uid555512@<unique_ipv6>
s = subscriber, paid member
u = unsubscriped, free member.
It's possible, of course, to use this service to register many names and launch a spam attack using it. But, in that case you can just block all `u<star>@<star>.irccloud.com`[0] (assuming you can rdns properly)
Like I said, I'm not a super large advocate of irccloud, but just as webchat passes on the originating IP via cgi module extensions, irccloud fixes problems with abuse for operators.
I know this, because I have been running a large irc network for over 10 years.
[0]: I tried everything to make asterisks appear, but hackernews is doing something funky:
u*@*.irccloud.comYou allude to a problem by suggesting blocking u*, these accounts can be created when the old one is blocked. Even subscriber accounts can be created at will & higher cost, though are likely less of an issue.
There is a problem that irc.example.net can't say "These users all seem to be originating from this single open proxy, lets block it." They need irccloud to do that.
https://riot.im with it's excellent IRC bridge is a solid alternative now (and fully open source).
[1] https://riot.im/
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...
Here are the highlights:
First commit: https://github.com/irssi/irssi/commit/770ae45
Time to finally switch from ircII?? /s
I know it doesn't always jive with the current fad of "move fast, throw in a bunch of js and break things" where everything is obsolete by the time it's released, but there's frankly no need for irssi development to proceed at an urgent pace. The 0.x versions were perfectly usable.
No I don't.
Three version control systems later, that commit has hints of git, svn (git-svn-id) and cvs (.cvsignore) all in one!
Good on them for fighting the good fight and not discarding history.
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-...
My book (link in profile) offers a free chapter on finding clients if you sign up for the mailing list. IRC is discussed in depth.
The most underused Linux service to the rest of the community. So glad they are using this.
[Disclaimer: I work for SUSE and am an openSUSE contributor.]
> 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).
Irsii was my daily communications hero for many years.
1) I misread the name of something that merely looked like irssi, or 2) there was a new project names irssi that unfortunately used a name of a much older project.
There was a several year period of my life where the vast majority of my online communication took place inside irssi. And that time was not particularly recent!
Congrats to the team, awesome to see it still going.
Nah, that's when you hear BitchX has done a new release.
Relatedly to this happy news, a gentle plug for a project I was involved in: https://github.com/rburchell/irssi-relay
irssi-relay allows you to connect weechat's relay clients to an irssi instance. I don't think it's gotten much use outside the few of us that work on it, more eyes are of course welcome.
Thanks!
Please file an issue if you don't mind (and if you can dig in and try to find the problem or even fix it, so much the better!)
UPDATE: I stand corrected.
i understand that Perl5, isn't really exciting anymore
but .. i think it's ok
Sorry if this makes you feel old, but that's a literal decade ago.
Man, I _am_ old.
Devs these days, so spoiled
And you really want something that has to support all those language stacks? Ew.
I've tried sooooo many different IRC clients. I always end up coming back to irssi.
It's "wee" - so it's minimal. Does a good job for its niche.
Cli chat clients are more flexible, with all the complexity that brings with it - but they're usually robust. Command line graphics don't change much :)
gui ones less so, but learning curve is not as steep. That said Xchat is hard to compare to weechat again, as it's a full fledged gui IRC client, rather than a minimal one. (multi network, multi server, dcc/xdcc and scriptability) and it's robust in its own niche.
Been using irssi for years now, and can't say I know/utilise all it offers, but it's great to log in to my server and screen -x into my irssi session.
I had an old java based chat client in mind that I used a long time ago and had a similar name.
[1]: https://weechat.org/
Hell even xchat is now hexchat. Weechat seems to be a pretty good client.
The nick list on the side does have its drawbacks when it comes to small screen realestate- but for a newbie (and beyond really. It seems to be very extedable) Friendly client it's impressive.
https://github.com/irssi/irssi/pull/181/commits/0494925a465b...
Also, +1 for Ruby support.
Now we got phones with internet though, so it's no longer that hard to look up stuff when your computer is half down :)
I guess that goes to show how much I pay attention to versions.
I certainly can't seem to find anything in the istore...
Coming from android, that was such a surprise, and similarly, a massive downer.
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.
(seriously though, not really, I could never figure out how to actually use that client)
I stopped using BX after a few IRC friends badgered me into switching to irssi and I haven't looked back. I'm on IRC every day and the VPS -> screen -> irssi config has worked for years, so I'm sticking to it.
Wait, what?
That was what everyone in my 'hood was using, back in the golden age of IRC.