Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

IRC necromancy

virtuallyfun.com

Post reply on HN
Print view View original

51–60 of 78 posts

Re: IRC necromancy

#51

Post by 0xVi »

SOLAR_FIELDS wrote: post #36
astrobe_ wrote: post #35

Earlier quoted context omitted.

> The barrier to entry's too high I don't understand this statement. One finds IRC clients everywhere. One literally has to know just one command at the beginning: /join. And then if you Google "IRC commands" or something like that, you get the rest of them easily (if your client lacks in the help area). > the feature set's extremely limited I don't understand this mindset. Why should a program have an extra-large se…

I’ve been a software engineer for several years now and I still have trouble with MiRC and Adium. I tried Irssi and eventually gave up with it. The problem with IRC is that even the “simple” clients never just work. There’s always some little infuriating quirks that you have to dive super deep into configs to figure out if it’s even possible to resolve without some sort of PR to the repository.

I"m a big fan of irccloud. It's the simplest client I've found and it's free, aside from subscribing for power-user features.

Re: IRC necromancy

#52

Post by jiggunjer »

Linuturk wrote: post #47
astrobe_ wrote: post #35

Earlier quoted context omitted.

> The barrier to entry's too high I don't understand this statement. One finds IRC clients everywhere. One literally has to know just one command at the beginning: /join. And then if you Google "IRC commands" or something like that, you get the rest of them easily (if your client lacks in the help area). > the feature set's extremely limited I don't understand this mindset. Why should a program have an extra-large se…

Having setup and attempted to administer an IRC server, I'd say that's where the barrier exists for someone wanting to create a new community outside of the huge Freenode network.

Why would you want to go outside freenode? They're run by a charity promoting free communication and have encryption for registered users.

Re: IRC necromancy

#53

Post by scruffyherder »

lowglow wrote: post #43
scruffyherder wrote: post #32

Earlier quoted context omitted.

Unixgod? Lol long long time ago. ... But I'm just hosting this post, it's not mine. The rest of the blog ramblings are.

It was SOOOO Long ago I don't even remember my handle back then. That was a long time ago. What are you up to now?

Changed jobs a few times, changed cities, then continents and then finally settled down. But I'm much older than you!

Started a blog over 10 years ago as a place to record my crazy experiments and to remember obsolete stuff. Not that I think many people care about ancient Unix, Novell or OS/2... I never really have much time to go back to the old chat.taucher.net thing... With the wife / kids / work it's hard to find the time.

Re: IRC necromancy

#54

Post by abhirag »

e12e wrote: post #22
scaryclam wrote: post #16

Earlier quoted context omitted.

Not sure why you're getting voted down. I'm looking for something to replace hip chat at the moment (we replaced slack with hipchat as slack didn't work well for us either), so I'm genuinely curious why a suggestion for riot is unpopular. Anyone care to comment?

What part of slack didn't work out for you? We're using slack at my workplace - and I think it's okish. Not a fan of it being a web app - but not frustrated enough yet to try the irc bridge with weechat (which is on my todo-list. Seems like a sane way forward, the last irc client I used was BitchX, and I don't think I'll likely to trust such an old c codebase with anything if I can help it..). Now that everyone "know…

Try the wee-slack plugin[https://github.com/wee-slack/wee-slack], it uses the Slack API and I have been using it on my Android phone(using Termux) and my Linux laptop, works great :)

Re: IRC necromancy

#55

Post by lowglow »

scruffyherder wrote: post #53
lowglow wrote: post #43

Earlier quoted context omitted.

It was SOOOO Long ago I don't even remember my handle back then. That was a long time ago. What are you up to now?

Changed jobs a few times, changed cities, then continents and then finally settled down. But I'm much older than you! Started a blog over 10 years ago as a place to record my crazy experiments and to remember obsolete stuff. Not that I think many people care about ancient Unix, Novell or OS/2... I never really have much time to go back to the old chat.taucher.net thing... With the wife / kids / work it's hard to find…

Can I just email you through your site? Is there contact info there?

Re: IRC necromancy

#56

Post by kakarot »

pavel_lishin wrote: post #31
kakarot wrote: post #23

Earlier quoted context omitted.

I just wish this wasn't a battle of decentralization vs centralization. Discord seems cool and all but channel operators lack reasonable amount of ownership over their channels and Discord touches every message that comes through its network.

I'm not necessarily disagreeing, but do you mean ownership over Discord channels or Discord servers ?

I mean servers. The protocol is locked to the platform.

Re: IRC necromancy

#57

Post by emmelaich »

astrobe_ wrote: post #35
LocutusOfBorges wrote: post #18

Earlier quoted context omitted.

Discord, overwhelmingly. Every IRC community I used to be a part of even a year ago has made the jump. It's just more convenient for all concerned- the only holdouts are people clinging to their CLIs and people objecting for ideological reasons. I wish it hadn't come to this, but IRC's just stagnated for too long. The barrier to entry's too high, using it on mobile devices is a chore, the feature set's extremely limi…

> The barrier to entry's too high I don't understand this statement. One finds IRC clients everywhere. One literally has to know just one command at the beginning: /join. And then if you Google "IRC commands" or something like that, you get the rest of them easily (if your client lacks in the help area). > the feature set's extremely limited I don't understand this mindset. Why should a program have an extra-large se…

> /join

and /password or was that /msg notify something or ??? If you get it wrong, congrats, you've just published your password to the world.

IRC wasn't even very good compared to other cli oriented programs such as the Unix shell or muds/moos.

Re: IRC necromancy

#58

Post by vldr »

I love trips down the memory lane to, what I call "the old internet" (before facebook etc), like this.

I also had to check if "my" bot was involved somehow. I wrote a C-bot called VladBot in the early 90's, stopped working on it somewhere in '97 but it's seen all kinds of reincarnations (good and bad) since then.

Re: IRC necromancy

#59

Post by CJefferson »

kuschku wrote: post #39
CJefferson wrote: post #17

Earlier quoted context omitted.

For me, it is the fact that most people connect with multiple devices, and want to have a smooth transition between them, and to be able to see history on all of them. There is no easy way of doing that with IRC, which kills it for me.

> There is no easy way of doing that with IRC, which kills it for me. Yes, there is! This is exactly what Quassel is made for. Just run the core anywhere (we’re looking into offering it hosted, too), connect with the web ui, the desktop client (Linux, Mac, Windows - uses Qt5, and is only a few megabytes, uses almost no RAM at all. A true native client), or the Android client. As many devices as you want under one acc…

I'm glad you are working on that, but "Just run the core anywhere (we’re looking into offering it hosted, too), connect with the web ui," really doesn't count as easy to use -- now everyone on my IRC channel needs to run a server which is is accessable to the internet, worry about security updates, both for the server and your software specifically.

Whereas with slack, I just do "make account, login, done". Until it's as easy as slack, I can't pursade people I work with to move over.

Re: IRC necromancy

#60

Post by metabrew »

kuschku wrote: post #38
na85 wrote: post #20

Earlier quoted context omitted.

Change aversion killed IRC. A lot of the opers on the big networks are extremely conservative and default to poo-pooing ideas because it's simpler. IRC with good mobile/push support could have taken off, but using it from a mobile device is painful because of the constant drops and the need to have your device responding to ping pongs every few seconds kills your battery.

> IRC with good mobile/push support could have taken off, but using it from a mobile device is painful because of the constant drops and the need to have your device responding to ping pongs every few seconds kills your battery. You mean, something like IRCCloud, or what I’m moving Quasseldroid to right now?

Random irccloud/quassel anecdote for you: when I started working on what is now irccloud, I was originally just going to write a (mobile-)web front end for quassel core, since I was using Quassel on KDE at the time (and had been for some time). This predates Quasseldroid I think, at least I don't remember there being a good mobile app for quassel back then.

The protocol between the quassel core and clients looked to be some sort of serialized Qt objects (iirc), so I abandoned that idea and wrote the irc client backend in erlang, with a json protocol.

Post reply on HN