-
discordIRCd
Discontinued A node.js script that allows you to connect to discord with your irc client.
Looking at the statistics I can't help but notice how small irc is these days. The biggest channels have a few thousand people in them but those seem to be rare.
One of the biggest channels ironically is one for an irc client called "the lounge". Which is a very nice webbased client with bouncer build in. Though I might be biased as I did contribute to the project years ago.
I was a dedicated IRC user for a long time, even going as far as developing this monstrosity: https://github.com/creesch/discordIRCd
At some point I didn't see the point anymore, as it clearly was just old guard sticking around with no one new joining.
It is a shame that discord as a closed platform is the defacto standard though. I am not sure things could have gone differently. Considering how glacial irc development was at the time and the convenience and features discord offers over alternatives like Matrix. I know that Matrix these days has a lot of the same features but certainly is not there as far as convenience goes.
-
Stream
Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.
-
ircv3-specifications
IRCv3 specifications | Roadmap: https://git.io/IRCv3-Roadmap | Code of conduct: http://ircv3.net/conduct.html
-
For those looking for an IRC client; there's;
* The lounge (web based) :
* Halloy (rust, native) : https://github.com/squidowl/halloy
* Tiny (rust, TUI; easier to configure than weechat) : https://github.com/osa1/tiny
* Weechat (TUI; the goat but harder, here's a good guide to setting it up) : https://newblood.anonops.com/weechat.html
-
For those looking for an IRC client; there's;
* The lounge (web based) :
* Halloy (rust, native) : https://github.com/squidowl/halloy
* Tiny (rust, TUI; easier to configure than weechat) : https://github.com/osa1/tiny
* Weechat (TUI; the goat but harder, here's a good guide to setting it up) : https://newblood.anonops.com/weechat.html
-
There's also http://irccloud.com, it's paid and includes a bouncer and mobile apps but I've switched to that from my self-hosted ZNC + Textual (https://www.codeux.com/textual/) setup and it's very worth the money. Just having push notifications on mobile and full backlog everywhere makes this a way better experience.
-
zulip-archive
Generate a static HTML archive of messages in any combination of streams in a Zulip organization.
Search engines are great at rendering content using JavaScript, they're just not able to explore the Zulip web application's URL structure, so they tend to index one page per Zulip installation.
The current solution is that projects that want their publicly available content to be search engine indexed set up https://github.com/zulip/zulip-archive, which usually involves hooking a GitHub action up to GitHub Pages for a 0-infrastructure deployment. Ultimately, that's the same model as an IRC indexing project like this one: a separate tool from the chat server is responsible for search engine indexing.
Lean runs one here: https://leanprover-community.github.io/archive/, but it looks like it hasn't updated in a year, so likely whoever in the Lean community needs to investigate why it isn't updating.
https://github.com/zulip/zulip/issues/21881 tracks our goal of making the server natively offer search engine indexing. The current separate archive tool model has some advantages (search engine load can't break the server, for example), but I think it'll be worth doing the native version when we can find the resources for it.
Source: I lead the Zulip project.
-
Zulip
Zulip server and web application. Open-source team chat that helps teams stay productive and focused.
Search engines are great at rendering content using JavaScript, they're just not able to explore the Zulip web application's URL structure, so they tend to index one page per Zulip installation.
The current solution is that projects that want their publicly available content to be search engine indexed set up https://github.com/zulip/zulip-archive, which usually involves hooking a GitHub action up to GitHub Pages for a 0-infrastructure deployment. Ultimately, that's the same model as an IRC indexing project like this one: a separate tool from the chat server is responsible for search engine indexing.
Lean runs one here: https://leanprover-community.github.io/archive/, but it looks like it hasn't updated in a year, so likely whoever in the Lean community needs to investigate why it isn't updating.
https://github.com/zulip/zulip/issues/21881 tracks our goal of making the server natively offer search engine indexing. The current separate archive tool model has some advantages (search engine load can't break the server, for example), but I think it'll be worth doing the native version when we can find the resources for it.
Source: I lead the Zulip project.
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.