matrix-docker-ansible-deploy
ircv3-ideas | matrix-docker-ansible-deploy | |
---|---|---|
2 | 198 | |
46 | 4,533 | |
- | - | |
10.0 | 9.9 | |
about 5 years ago | 6 days ago | |
Jinja | ||
- | GNU Affero General Public License v3.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
matrix-docker-ansible-deploy
-
The Matrix Trashfire
Check out https://github.com/spantaleev/matrix-docker-ansible-deploy/
-
Ask HN: Recommendations for an alternative native chat client? (Slack, Discord)
As some others have said, matrix is great at this.
I use this ansible playbook to set it all up: https://github.com/spantaleev/matrix-docker-ansible-deploy it supports slack and discord too.
You can also use beeper which is hosted if you don't want to self host. They employ one of the major bridge Devs so they know what they're doing.
There's also element one from the Devs of matrix but they don't support all services you're looking for.
-
Second Phone, Same Signal
Exactly yeah, I used this bridge with this playbook
- Matrix 2.0: The Future of Matrix
-
Having trouble installing self-hosted on Debian
Check the ansible instructions first: https://github.com/spantaleev/matrix-docker-ansible-deploy/tree/master
-
Local development environment advice
matrix-docker-ansible-deploy looks like a good way to go.
-
Self Hosting Matrix Server
You could maybe check out this URL about setting up Oracle free tier but it could be outdated. I just recommend using the Matrix Ansible Playbook
- FOSS Discord Alternatives
-
How to access the synapse-admin web ui?
I installed my home server via the ansible playbook, gave myself admin privileges and then enabled the api in the playbook. The playbook sets up the server with a reverse proxy and im geting an error 'NetworkError when attempting to fetch resource' when i enter in my credentials.
-
KDE is ready to deprecate IRC, XMPP, and Telegram in favor of Matrix
Yeah sorry I was on mobile when I wrote that so I didn't have it to hand.
Here it is: https://github.com/spantaleev/matrix-docker-ansible-deploy
What are some alternatives?
The Lounge - π¬ β Modern, responsive, cross-platform, self-hosted web IRC client
awesome-selfhosted - A list of Free Software network services and web applications which can be hosted on your own servers
element-x-android - Android Matrix messenger application using the Matrix Rust Sdk and Jetpack Compose
tailscale - The easiest, most secure way to use WireGuard and 2FA.
convos - Convos :busts_in_silhouette: is the simplest way to use IRC in your browser
caddy-docker-proxy - Caddy as a reverse proxy for Docker
znc-push - Push notification service module for ZNC
Synapse - Synapse: Matrix homeserver written in Python/Twisted.
element-meta - Shared/meta documentation and project artefacts for Element clients
Element - A glossy Matrix collaboration client for the web.
ircv3-specifications - IRCv3 specifications | Roadmap: https://git.io/IRCv3-Roadmap | Code of conduct: http://ircv3.net/conduct.html
Signal-Server - Server supporting the Signal Private Messenger applications on Android, Desktop, and iOS