Notices tagged with irc

Man, all the stuff that people say they don't like about #IRC (no persistent connection, no notifications, no embedded images) are precisely the things I like the most about it.

We don't have to be all the time online, notified, and imaged.

And now, #IRC comedy:

<Mikael_Kreoss> reminded me of the time as a kid I saw a pic of the pope's bubble car thing
<Mikael_Kreoss> and thought it was meant to keep him in
<Mikael_Kreoss> like he was a monster or w/e
<Mikael_Kreoss> on display
<Mikael_Kreoss> "WE CAUGHT THE POPE" and then celebration time

http://qdb.us/308875

Got a lot of help from the #debian channel in #IRC. Thanks guys! You make me look smarter than I am and you made me very happy that it all worked out.

I don't get people that join #irc channels for 3 minutes, ask a question and then leave after 2 minutes.

Did you know that you can get a cool #FreeBSD cloak on #freenode?

For example: freebsd/hacker/{nickname}

It's fun and it proves that #BSD systems are not dying. ;)

More here: https://wiki.freebsd.org/IRC/Cloaks

#IRC

If I were setting up a chat network for local peeps, would it be better to do #IRC or #jabber/#XMPP?

IRC is easier to onboard peeps, but is kinda weird and has no real mobile support. It would feel more intimate, and focused.

Jabber is more useful with talking to the wider world. Better clients, #OMEMO all over the place. But takes a while to create accounts, to convince others to use it.

Whatcha think? My goal is better tools to communicate with neighbors. ^_^

I updated the #Mastodon ticket at https://github.com/tootsuite/mastodon/issues/6072 to include #ftp and #irc. Are there other protocols we ought to include? That is all I can think of.

I'll put this out there: I don't consider #IRC to be a candidate for team chat.

* How does IRC develop?
* External system for archiving and search
* File sharing is weird
* Clients are weird
* Prefers commands over clicking

Super fun tech! But the teams that use it either depend on a third-party (which is fine in many cases), or have an engineer (or likely an IRC fan) to run the whole stack for them.

I run a #snap for #RocketChat. It auto-updates, as does Ubuntu. Dope.

I can't quite put my finger on it, but something about the UI/paradigm of web-based #IRC is really compelling.

A friend here once told me in person that Slack was just a UI shift, and IRC could be improved by copying that (my paraphrase, it was obviously more elegant than that).

If that were the case, we are really talking about the client. Because IRC is weird, and the more we can hide it, the sooner people can do boring business things.

Slack, et al, make boring business easy. 🤔

We have web-based chat options, from Slack to the good ones like #RocketChat and #Mattermost.

But they take up a lot of resources, as they scale. Compared to dedicated servers and protocols, such as #IRC and #XMPP, you end up throwing a lot of resources per user.

This makes me think that the web-based ones work for teams (as a shared space for ambient documentation and file sharing), but not as a public service.

Of course #jabber exceeds at scale due to federation. Like email.