744 karma · joined December 9, 2020
Discord's server/channel/role system is amazing, and I don't know why everyone else isn't replicating it.
For instance, let's take the Pine64 Discord server. It has a grand total of 27 channels split into 10 categories (including top-level). Using Discord's permissions system, some of those channels are read-only like #announcements.
Pine64's server is also bridged to Matrix. Matrix requires every single channel to be bridged individually into their own Matrix chat, just look at this table (https://wiki.pine64.org/wiki/Main_Page#Chat_Platforms)! In fact, some of the channels aren't even bridged at all! Meanwhile on Discord, everything's all in one easy to use place. You just join the server, and that's it.
But what about Matrix spaces? Aren't those the equivalent of Discord servers? The issue is that rather than an integrated experience, Matrix servers are just a built-in version of the table I listed above. You still have to leave/join chats individually and it doesn't even have categories!
But that's all from a user's perspective, what about from a server admin's perspective? Discord's permission system is great and flexible, and Matrix's system is just kind of bad. In case you don't know Matrix's system from what i understand is basically: every user gets a permission level number, and users with certain levels can do certain things. That's it, no flexibility whatsoever.
Meanwhile on Discord, you can create roles which when given to users allow them to do certain things. Like anyone with a "Moderator" role can delete messages or ban people. But you could also make it so "moderators" can't delete messages, only ban people. And you can also make roles behave different on per-channel or per-category basis. You can even make it so users can't see a channel at all without a role (for instance, a server I'm an admin on has a #mod-chat channel and a #admin-chat channel).
Matrix's system just can't do that. And it really doesn't integrate with their Spaces system. There's no way to make it so only certain people can see certain channels in a Matrix Space. In fact, there's no way to manage permissions for an entire Matrix Space at all! It's limited to a per-chat basis.
And that long-winded rant is why I will stick with Discord.
Wait what. Not being able to safely restart the server sounds like a disaster waiting to happen.
If you use Apple, you're just out of luck unless you want to mess with whatever hacky workaround is popular this week.
There doesn't seem to be many general servers that:
1. I can trust won't just shut down in a week.
2. Are accepting signups
3. And won't end up having a negative stigma a in year when the creator goes off a deep end. I know I can just switch to another instance, but I really don't want to have to do that frequently.
Matrix at least solves this by just having an official Matrix home-server. Matrix is still federated, but if you just want to just sign-up and join a chat room, you're not forced to pick a home-server that's specific to you or worry about the factors above.
Even ignoring security issues, all of make getting elevated privileges can cause other issues as well.
All it takes is the incremental build system being a little finicky, and "sudo make install" could rebuild an object as root, and now one or more of your ".o" files are owned by root and your build directory is broken.
I'd argue that's (at least part of) the problem. More code = more surface area for bugs, and sudo has a lot of code.
This seems like a really weird thing for a distro to add themselves rather than upstream.
Why can't we just have a minimal version of sudo that does just that and only that so the majority of smaller servers and home users can run sudo without fear of a security bug ever other month? Preferably using the same executable path so that everything else doesn't break.
It just seems like most of sudo's security bugs come from weird obscure features almost no one uses. Like that time sudoedit had a security issue. I didn't even know that command existed until it broke things, and it still seems pointless when you can just run "sudo nano" or "sudo vi".
Whenever I need to report a bug on a GitLab instance, its UI is a big source of friction (especially since GitLab's UI is still annoyingly slow when loading things like issue comments).
The process is just extracting a ZIP file (omni.ja), editing modules/AppConstants.jsm to have MOZ_REQUIRE_SIGNING set to false, then put the ZIP file back together.
A quick Google search led me to https://udn.realityripple.com/docs/Mozilla/About_omni.ja_(fo..., which seems to have instructions for working with omni.ja on Windows.
If it helps, the biggest issue I had with setting up custom extensions on Firefox Nightly Android using spaces in the collection name.
The main use-case of this is so that Mozilla doesn't have total control over what extensions are allowed to be installed.
It can also be used so you can install extensions you built-from-source.
I always thought it was silly that the best way to embed a resource in a binary using CMake was to either convert it to hexadecimal C array manually or use specific flags with ld to convert it into an object (and good luck getting that to work reliably with cross-compiling!).
(On that note, are there any actual reasons to not just --recurse-submodules by default?)