Weechat
ircv3-ideas | Weechat | |
---|---|---|
2 | 22 | |
46 | 2,827 | |
- | 0.4% | |
10.0 | 9.8 | |
about 5 years ago | 7 days ago | |
C | ||
- | GNU General Public License v3.0 only |
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
Weechat
-
Neonmodem: TUI for Lobsters, HN, etc.
WeeChat[0] with Bitlbee[1] supports a metric assload of services, albeit by pretending they're IRC (which does work - I spent years in weechat/irssi with bitlbee talking to various people on disparate services.)
Or if you're just after Telegram/WhatsApp, nchat[2] is ok (I can vouch for the Telegram half only.)
[0] https://weechat.org
[1] https://wiki.bitlbee.org
[2] https://github.com/d99kris/nchat
-
Wave of Spam Hits IRC
And UnrealIRCD still rocks. For a quick-and-dirty setup I've deploy ng-ircd but Unreal has always been my go-to for anything serious. If nothing else it can be useful as a backup or internal platform during the rare events that Slack or Discord are having an incident. The common complaint is a lack of channel back-log but it can be front-ended with TheLounge [1] or Convos [2]. I personally prefer to handle that with gnu screen or tmux and WeeChat [3].
[1] - https://github.com/thelounge
[2] - https://github.com/convos-chat/convos/
[3] - https://weechat.org/
- mIRC i början av 2000?
-
WeeChat Version 4.0.0
The link posted was to the dev blog, the actual website can be found at [0]. On the blog, the right side menu under "Links" also links to the website.
[0] - https://weechat.org/
-
Can you help me login or get my WeeChat back?
I’m afraid you’re in the wrong subreddit. This subreddit is dedicated to WeeChat the IRC client., not the proprietary messaging app built by Tencent.
-
DPReview.com is shutting down
First off, grab yourself an IRC client. On their connection info page Hackint has information for both WeeChat and Hexchat, but you could use any IRC client.
-
Discord has updated their privacy policy.
That's nothing to do with weechat? https://weechat.org/
-
IRC Chat?
Gajim is for XMPP. For IRC you need Hexchat or Weechat or something like that.
-
Tell HN: Linux Mint support IRC appears to me captured by juvenile moderators
I am not familiar with HexChat but you might consider using a different IRC client that allows you to silence anything/everything by default and only alert you on specific keywords you are interested in. If you like command line tools, consider trying out WeeChat IRC client [1] It is very customizable and there are many scripts for it.
[1] - https://weechat.org/
- Ask HN: Is there other software similar to Vim and Emacs?
What are some alternatives?
The Lounge - 💬 Modern, responsive, cross-platform, self-hosted web IRC client
irssi - The client of the future
element-x-android - Android Matrix messenger application using the Matrix Rust Sdk and Jetpack Compose
convos - Convos :busts_in_silhouette: is the simplest way to use IRC in your browser
Quassel IRC - Quassel IRC: Chat comfortably. Everywhere.
znc-push - Push notification service module for ZNC
ZNC - Official repository for the ZNC IRC bouncer
element-meta - Shared/meta documentation and project artefacts for Element clients
wee-slack - A WeeChat script for Slack.com. Supports threads and reactions, synchronizes read markers, provides typing notification, etc..
ircv3-specifications - IRCv3 specifications | Roadmap: https://git.io/IRCv3-Roadmap | Code of conduct: http://ircv3.net/conduct.html
Convos - Convos :busts_in_silhouette: is the simplest way to use IRC in your browser [Moved to: https://github.com/convos-chat/convos]