nheko
matrix-docker-ansible-deploy
Our great sponsors
nheko | matrix-docker-ansible-deploy | |
---|---|---|
17 | 198 | |
1,740 | 4,465 | |
2.3% | - | |
9.7 | 9.9 | |
6 days ago | 7 days ago | |
C++ | Jinja | |
GNU General Public License v3.0 only | 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.
nheko
-
PSA: security vulnerability in qBitorrent 4.5.x webUI
Look at this, notice anything different? https://github.com/Nheko-Reborn/nheko/issues/new/choose
-
This Year in Matrix
Nheko has been around for a number of years. Never used it myself though.
-
Matrix was worth the effort to self host.
Matrix clients hit different than pretty much any other chat client I've use before. Theres multiple clients I've found like nheko, moments, element that are a pleasure to look at and smooth as hell. Even better you can have users use web services like Element Web to sign-up and chat. Its sick.
-
What flatpaks are "official" (i.e., directly from the application's developer)?
The Nheko flatpak is official. Just compare the source to the nightlies we build and upload to our nightly repo.
-
GTK4 Matrix Client
Like almost every client out there it has no support for e2ee. I was happy to find https://nheko-reborn.github.io (I'm a KDE user so Qt apps are preferred).
- Mozilla Thunderbird Beta now supports Matrix chat
-
Using Files with Browsers, in Reality
I probably wouldn't have guessed that `e.dataTransfer.items` gets cleared at the first await (since I'm not a proficient web developer), but I would've been extremely wary of this code in general. Additionally (not tied to async-await but race conditions in general), is `item.getAsFileSystemHandle()` a TOCTTOU vulnerability where the type of an item can change between folders and files and symlinks etc., while this code is running?
Rust's & vs. &mut system largely eliminates shared state hazards in both threading and asynchronity (&mut is exclusive/unaliased and can't be mutated by other threads or event loop jobs, and & is difficult and unidiomatic to mutate), though it doesn't solve async cancellation errors (https://carllerche.com/2021/06/17/six-ways-to-make-async-rus..., discussed at https://news.ycombinator.com/item?id=27542504), or filesystem TOCTTOU (https://blog.rust-lang.org/2022/01/20/cve-2022-21658.html as well as user code).
Qt event loop reentrancy is fun(tm) as well. It looks like a blocking call, but spawns a nested event loop which can do anything (but rarely enough to lull you into a false sense of complacency), resulting in segfaults like https://github.com/Nheko-Reborn/nheko/issues/656 (workaround at https://github.com/Nheko-Reborn/nheko/commit/570d00b000bd558..., I didn't look into it). And Qt lacks "easy" await syntax and a framework based on calling red functions (though I didn't look into C++20 coroutines yet, perhaps https://www.qt.io/blog/asynchronous-apis-in-qt-6 or https://github.com/mhogomchungu/tasks or https://blog.blackquill.cc/asynchronous-qtquick-uis-and-thei...?).
- Introducing Native Matrix VoIP with Element Call!
-
How a Single Line of Code Made a 24-Core Server Slower Than a Laptop
> So forcing everyone to think about ownership because maybe they are writing concurrent code (then again maybe they aren't) so that "congrats your memory management problems are solved" seems like a Pyrrhic victory--you've already blown their brain cells on the wrong problem.
https://manishearth.github.io/blog/2015/05/17/the-problem-wi... argues that "[a]liasing with mutability in a sufficiently complex, single-threaded program is effectively the same thing as accessing data shared across multiple threads without a lock". This is especially true in Qt apps which launch nested event loops, which can do anything and mutate data behind your back, and C++ turns it into use-after-free UB and crashing (https://github.com/Nheko-Reborn/nheko/issues/656, https://github.com/Nheko-Reborn/nheko/commit/570d00b000bd558...). I find Rust code easier to reason about than C++, since I know that unrelated function calls will never modify the target of a &mut T, and can only change the target of a &T if T has interior mutability.
Nonetheless the increased complexity of Rust is a definite downside for simple/CRUD application code.
On the other hand, when a programmer does write concurrent code with shared mutability (in any language), in my experience, the only way they'll write correct and understandable code is if they've either learned Rust, or were tutored by someone at the skill level of a Solaris kernel architect. And learning Rust is infinitely more scalable.
Rust taught me to make concurrency tractable in C++. In Rust, it's standard practice to designate each piece of data as single-threaded, shared but immutable, atomic, or protected by a mutex, and separate single-threaded data and shared data into separate structs. The average C++ programmer who hasn't studied Rust (eg. the developers behind FamiTracker, BambooTracker, RtAudio, and RSS Guard) will write wrong and incomprehensible threading code which mixes atomic fields, data-raced fields, and accessing fields while holding a mutex, sometimes only holding a mutex on the writer but not reader, sometimes switching back and forth between these modes ad-hoc. Sometimes it only races on integer/flag fields and works most of the time on x86 (FamiTracker, BambooTracker, RtAudio), and sometimes it crashes due to a data race on collections (https://github.com/martinrotter/rssguard/issues/362).
- Update on beta testing payments in Signal
matrix-docker-ansible-deploy
- The Matrix Trashfire
-
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
-
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.
-
What's the easiest way to use Matrix and add matrix-bridges for Messenger, Instagram, and Telegram etc.
I actually recommend checking out https://etke.cc/ around Matrix setup and more. As someone who's stood up Matrix a couple times in past (including a go-around with the aforementioned matrix-docker-ansible-deploy), I knew some of the pitfalls were still there in setup, and this go-around I lacked the time to manage a Matrix-specific VPS on top of my other local/remote services, esp. since I wanted to use it with friends and family and thus needed it to be bullet-proof (as well as me-proof!)
What are some alternatives?
awesome-selfhosted - A list of Free Software network services and web applications which can be hosted on your own servers
tailscale - The easiest, most secure way to use WireGuard and 2FA.
Synapse - Synapse: Matrix homeserver written in Python/Twisted.
Signal-Server - Server supporting the Signal Private Messenger applications on Android, Desktop, and iOS
caddy-docker-proxy - Caddy as a reverse proxy for Docker
Element - A glossy Matrix collaboration client for the web.
fluffychat
imessage - A Matrix-iMessage puppeting bridge
sydent - Sydent: Reference Matrix Identity Server
Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..
dendrite - Dendrite is a second-generation Matrix homeserver written in Go!
matterbridge - bridge between mattermost, IRC, gitter, xmpp, slack, discord, telegram, rocketchat, twitch, ssh-chat, zulip, whatsapp, keybase, matrix, microsoft teams, nextcloud, mumble, vk and more with REST API (mattermost not required!)