Live data from Hacker News

Freenode IRC logging archive Echelog is shutting down

echelog.com

101–110 of 137 posts

Re: Freenode IRC logging archive Echelog is shutting down

#101
Sad to see GDPR still slowly killing anything too small to pay a legal team (basically anything that can be sued that hasn't incorporated, ie, human persons).

> Furthermore, the cost (financially, mentally and legally (GDPR)) of running the site, no longer makes sense for me.

Re: Freenode IRC logging archive Echelog is shutting down

#102
post #41

I don't really use IRC anymore but at the time I remember really hating loggers. Chats were informal and I really didn't like them showing up in google results and elsewhere. Not everything needs to be saved.

Yes, I agree. Lots(most?) of channels on freenode are explicitly not publicly logged anywhere, and the freenode staff are pretty helpful at helping chanops enforce this. None of the channels I help run have any public logs available.

Perhaps a naive question, but how do chanops enforce this? What's to stop someone lurking in a channel and publishing a log. You can't obviously connect an individual lurker to a log and busy channels have dozens of 24/7 clients connected.

Re: Freenode IRC logging archive Echelog is shutting down

#103

Earlier quoted context omitted.

Unfortunately Facebook and Google also log everything. At least Facebook lets you delete your copy, but Google does not allow even this.

I kinda doubt that Facebook actually deletes, as opposed to setting a DB flag... weren't they caught logging comments that were typed in but then modified / deleted / not actually posted?

The other party, i.e. the recipient still has an copy, so it could be a DB flag indeed. Although when both persons delete the message it might still lay around for who knows how long.

Re: Freenode IRC logging archive Echelog is shutting down

#104

Earlier quoted context omitted.

For the record, careful with doing private investigations. It might look good on Netflix, but can turn sour real fast.

What can happen?

You can be killed, or worse, someone you care about.

Re: Freenode IRC logging archive Echelog is shutting down

#105

I just wanted to take a moment and share with the HN community that IRC is definitely very alive and kicking! There are great channels for thousands of amazing projects, communities and teams spread across so many great IRC Networks, from Freenode [1] to OFTC [2], to Rizon [3], to DALnet [4], to tildeverse [5], Snoonet [6], Quakenet [7], EFnet [8], IRCnet [9] among other networks [10]. IRC is no longer difficult to u…

IRC is where you go to play the idle game, right?

Re: Freenode IRC logging archive Echelog is shutting down

#106
post #102

Earlier quoted context omitted.

Yes, I agree. Lots(most?) of channels on freenode are explicitly not publicly logged anywhere, and the freenode staff are pretty helpful at helping chanops enforce this. None of the channels I help run have any public logs available.

Perhaps a naive question, but how do chanops enforce this? What's to stop someone lurking in a channel and publishing a log. You can't obviously connect an individual lurker to a log and busy channels have dozens of 24/7 clients connected.

> You can't obviously connect an individual lurker to a log

I don't think that's necessarily true.

While I don't know if the IRC Server software supports it, there's no reason you couldn't encode some kind of unique tag into the stream of IRC messages sent to each client. Unless you were running two clients and diffing their logs you wouldn't notice.

It could be as simple as seeing additional events, or modified whois/client information on join/leave, or even completely fake client join/leaves.

Re: Freenode IRC logging archive Echelog is shutting down

#107
post #52

Earlier quoted context omitted.

I would have shared the same sentiment. I never came across a logger, though, when I was still active on IRC. Are loggers a more recent (as in this millenium) development?

I would say chat history and asymmetrical scheduling for chat are expectations in this day and age, and the lack of them is one of the biggest reasons people find IRC irritating or difficult. (I ask a question, and if the person fit to answer it isn't logged in right now, it never gets even responded to.) Every fairly modern chat solution, Skype, Discord, Slack, etc. allows you to see messages while you were offline.…

ZNC and earlier implementations have been around for 15+ years to provide queuing proxies. Pretty much all of the "unique" features found in current chat systems were also implemented in one fashion or another in the IRC ecosystem decades ago. Ease of use has definitely improved, in exchange for for-profit company control over communications in these systems. IRC's decentralized nature still argues for its relevance even now.

Re: Freenode IRC logging archive Echelog is shutting down

#108
post #15
post #2

So, I'm too young to have ever used IRC. This must be a biggish deal to make it #2 on HN homepage. But can someone put this in perspective of how big a deal this is? On a scale of 'Rando County Legacy ISP-provided email service' to 'Gmail' is shutting down, where does this lie? IRC is not email, etc. but again, never seen this community.

First of all, you're not too young for IRC, it's still out there! Lots of people! Lots of channels! Depending on your interests your usage could resemble a live-action Reddit. Second, I don't think this is necessarily a big deal, though I could imagine that channel users liked the convenience of having their channel logged for them. There may even have been an ersatz Slack use-case there that people could easily get…

there are dozens of us! dozens!

Re: Freenode IRC logging archive Echelog is shutting down

#110

I just wanted to take a moment and share with the HN community that IRC is definitely very alive and kicking! There are great channels for thousands of amazing projects, communities and teams spread across so many great IRC Networks, from Freenode [1] to OFTC [2], to Rizon [3], to DALnet [4], to tildeverse [5], Snoonet [6], Quakenet [7], EFnet [8], IRCnet [9] among other networks [10]. IRC is no longer difficult to u…

On DOS, there's mtcp's ircjr.

On AmigaOS, amirc (which many clients cloned the UI of) and wookiechat.

Even kolibriOS ships an irc client.

It's a nice, simple protocol that's human readable and imposes very little overhead on the clients.

Post reply on HN