Kiwi IRC
ircv3-ideas | Kiwi IRC | |
---|---|---|
2 | 12 | |
46 | 830 | |
- | 0.6% | |
10.0 | 8.4 | |
about 5 years ago | 25 days ago | |
Vue | ||
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ircv3-ideas
-
Matrix 2.0: How we’re making Matrix go voom
> "At least as standard" how?
There are 8 people who vote on changes to the Matrix spec (the Spec Core Team), 7 of which are Element employees (including Matthew, Element's CEO). Element also controls the development of clients and servers used by the large majority of users in the public federation.
> A substantial portion of the IRC comunity is actively hostile to the IRCv3 extensions, and in some cases prefer incompatible implementations of the same functionality; Matrix has nothing like that going on.
But any IRC client will work fine on any IRC server, and they can connect to various servers with different implementations.
On Matrix, clients (generally) can only connect to one homeserver at a time; which forces them to converge on following exactly the same spec. And if your server differs ever so slightly from the other ones in how it implements some parts of the spec (room consensus), then it can be split-brained from the rest of the federation. Instead, changes to the room consensus are done by pushing new room versions, and each server implementation needs to explicitly support it or they can't join it. This means Synapse devs (which are a majority of Element employees) get to decide what room versions can get traction.
It is not uncommon for people in the Matrix community to complain about this and Element keeping specs in limbo, and PRs to the flagship clients being stuck in "design review tar".
> And there seem to be more visibly independent implementations of Matrix than IRCv3.
Clients, maybe, at least in the number of implementation. It's hard to find stats of this, but I feel that >95% of people in the public federation use Element even in tech-y rooms; IRC has a healthier mix of major clients (weechat, irssi, IRCCloud, Hexchat, KiwiIRC, The Lounge each have >5% of desktop/web users). But I admit that's just my very subjective point of view.
In terms of servers, Matrix has three open source ones as far as I know: Synapse (controlled by Element), Dendrite (controlled by Element, and almost on par with Synapse according to https://arewep2pyet.com/ ), and Conduit. Based on https://gitlab.com/famedly/conduit/-/milestones/3 , Conduit seems to be far from implementing the spec yet (eg. it doesn't seem to support leaving rooms or respecting history visibility).
> things like: server-side history extensions tended to mess up my client's history implementation (I'd end up with multiple copies of the same messages in my local logs, often with the wrong timestamps)
You can use https://ircv3.net/specs/extensions/message-ids to deduplicate them.
> And if you're in a conversation where people are using embedded gifs, then fundamentally you'll always be a second-class citizen if you're trying to participate in that with a client that can't display embedded gifs.
A conversation where people where people are using embedded gifs will exclude me regardless of client, because they are too distracting. At least on IRC I can expect people not to do it too much, and use words or emojis instead of reaction gifs.
> SSO access control; you just can't do that in a nice way if the client doesn't support it
That's a fair point; IRC is made by hobbyists more than companies, so that's not surprising. There is some discussion around it though: https://github.com/ircv3/ircv3-ideas/issues/74 and Sourcehut is sponsoring implementation (https://emersion.fr/blog/2022/irc-and-oauth2/).
- Ergo – modern IRC server written in Go
Kiwi IRC
-
Matrix 2.0: How we’re making Matrix go voom
> At that point you've just reimplemented a less-standard version of matrix with extra steps though.
There are IRCv3 specifications that allow this richer experience, and they are at least as standard as Matrix. Check out https://ergo.chat/ with modern clients like https://sr.ht/~emersion/goguma/ (Android), https://git.sr.ht/~emersion/gamja/ https://kiwiirc.com/ (web), or https://git.sr.ht/~taiite/senpai (TUI)
> but in practice using your enhanced server from an unenhanced client will always be painful
IRCv3 normally makes sure new specs don't make it worse for older clients. Could you give me some examples to see if we can fix that?
- IRCv3 2022 Spec round-up
-
Long term good standing user account seems to be disabled, is it ok to ask here for advice for what looks like a automated P2P-NET ban?
First try the web-based ones - https://kiwiirc.com/ - https://mibbit.com/
-
y a-t-il encore des utilisateurs de chan IRC ?
Un client en ligne : https://kiwiirc.com/ Un serveur français : https://www.epiknet.org/irc/
-
Looking for a single-room web-based chat client
You can take a look at kiwi irc: https://github.com/kiwiirc/kiwiirc and configure the channels it joins.
-
Looking for some very specific courses. Voice acting, acting, voice over, narrator stuff, I just wanna know how people do this shit!
Their IRC link is on their homepage. If you don't have an IRC client you can use https://kiwiirc.com/ in browser.
-
Ergo IRC Server
It depends. There's a lot of people on/around IRC who really like it (see libera and all the other networks), and yeah there definitely are people spinning up new smaller networks. Especially with things like https://sr.ht/~emersion/gamja/ and self-hosted https://kiwiirc.com/ , as well as really polished client experiences like irccloud, it's easier to convince people to join in.
Right now I'm working with a dev from libera on a client that aims to replicate a lot of things experience-wise from newer chat services. Hoping that with that, smaller self-contained servers can become more of a norm~ But for now, your best bets for finding activity are probably Libera and a couple of the other larger networks.
- Can you build IRC Chats between users into a website chat frame
-
Lispers active anywhere else with a better topical discussion tool?
I use https://kiwiirc.com and it allows me to create a temporary account without an e-mail. I think you need an e-mail if you want to 'reserve' your name
- How to setup web IRC
What are some alternatives?
The Lounge - 💬 ‎ Modern, responsive, cross-platform, self-hosted web IRC client
element-x-android - Android Matrix messenger application using the Matrix Rust Sdk and Jetpack Compose
InspIRCd - A modular C++ IRC server (ircd).
convos - Convos :busts_in_silhouette: is the simplest way to use IRC in your browser
ZNC - Official repository for the ZNC IRC bouncer
znc-push - Push notification service module for ZNC
Convos - Convos :busts_in_silhouette: is the simplest way to use IRC in your browser [Moved to: https://github.com/convos-chat/convos]
element-meta - Shared/meta documentation and project artefacts for Element clients
Shout - Deprecated. See fork @ https://github.com/thelounge
ircv3-specifications - IRCv3 specifications | Roadmap: https://git.io/IRCv3-Roadmap | Code of conduct: http://ircv3.net/conduct.html
ngircd - Free, portable and lightweight Internet Relay Chat server