Other than it being closed garden that isn’t indexable on the web
“Apart from the sanitation, the medicine, education, wine, public order, irrigation, roads, the fresh water system, and public health, what have the Romans ever done for us?”
Discord is great for providing a community chatroom for both voice and text. It started, and still is, as the combination of IRC and Teamspeak/Ventrilo, now just with more bloat and memes. That people are trying to use the “IRCTeamspeak” as the entire information platform for their open source project is just mental, as it puts everything hidden behind a login requirement, unindexable and unsearchable on any search engine in an ever-changing stream of unrelated discussion.
Stick your bug reports and issues in a Github/Gitlab etc tracker, your information into a Wiki, and set up a forum. The discord can exist alongside these, but it cannot properly replace any of them.
I feel it maybe an administration issues. There are third-party bots allowing integration, channel/thread/role permissions which I find great but can be a hassle to set up.
A perfectly setup discord server with automation and webhooks, updates, permissions would be great. But setup of one is too complicated for the masses.
Segregating discord channels bases on roles, and staying on top of it with user influx - that would be perfect. Less than a percent (anectode) of channels can achieve simplicity like this.
Does anyone else have the thought that maybe it’s time to just replace these 30+ year old ancient protocols? Seems like the entire networking stack is held together with string and duct tape and unnecessarily complicated.
A lot of the decisions made sense somewhat in the 80s and 90s, but seems ridiculous in this day and age lmao
I definitely would love to see a rework of the network stack at large but idk how you'd do it without an insane amount of cooperation among tech giants which seems sort of impossible
Seems like the entire networking stack is held together with string and duct tape and unnecessarily complicated.
The more you learn about network technology the more you realize how cobbled together it all is. Old, temporary fixes become permanent standards as new fixes are written on top of them. Apache, which was the most widely used web server for a long time, is literally named that because it was “a patchy” server. It’s amazing that any of it works at all. It’s even more amazing that it’s been developed to the point where people with no technical training can use it.
The open nature of IP is what allows such a varied conglomerate of devices to share information with each other, but it also allows for very haphazard connections. The first modems were just an abuse of the existing voice phone network. The internet is a functional example of building the airplane while you’re flying it. We try to revise the standards as we go, but we can’t shut the whole thing down and rebuild it from scratch. There are no green fields.
It has always been so. It must be so. It will continue to be so.
Same unfortunately goes for a big chunk of the law on a global scale… Constant progress, new possibilities and technologies, changes in general are really outpacing some dusted and constantly abused solutions. Every second goes by and any “somehow still holding” relic is under more pressure. As a species we can have some really great ideas but the long-term planning or future-proofing is still not our strongest suit.
I may be waaaay off here, but the internet as it exists is pretty much built on DNS, isn’t it? I mean, the whole idea of DARPANet back in the 60s and 70s was to build a robust, redundant, and self-healing network to survive nuclear armageddon, and except when humans f it up (intentional or otherwise), it generally does what it says on the tin.
Now, there’s arguments to beade about securing the protocol, but to rip and replace the routing protocols, I think you’d have to call it something other than the Internet.
I have a coworker who always forgets TTL is a thing, and never plans ahead. On multiple occasions they’ve moved a database, updated DNS to reflect the change, and are confused why everything is broken for 10-20 minutes.
I really wish the first time they learned, but every once and a while they come to me to troubleshoot the same issue.
While planning your change (or project requiring such change), check the relevant(* see edit) DNS TTL. Figure out the point in the future you want to do the actual change (time T), and set the TTL to 60 seconds at T-(TTL*2) or earlier. Then when it comes to the point where you need to make your DNS change, the TTL is reasonable and you can verify your change in some small amounts of minutes instead of wondering for hours.
Edit: literally check all host names involved. They are all suspect
This. For example, if you have a DNS entry for your DB and the TTL is set to 1 hour, an hour before you intend to make the changes, just lower the TTL of the record to a minute. This allows all clients to be told to only cache for a minute and to do lookups every minute. Then after an hour, make the necessary changes to the record. Within a minute of the changes, the clients should all be using the new record. Once you’ve confirmed that everything is good, you can then raise TTL to 1 hour again.
This approach does require some more planning and two or three updates to DNS, but minimizes downtime. The reason you may need to keep TTL high is if you have thousands of clients and you know the DNS won’t be updated often. Since most providers charge per thousand or million lookups, that adds up quickly when you have thousands of clients who would be doing unnecessary lookups often. Also a larger TTL would minimize the impact of a loss of DNS servers.
Discord performance is inversely proportional to the number of servers you’re in. Until Discord addresses this, it’s a shit tool for this use case unless you participate in a tiny number of servers in one facet of your life. Unlike chat tools like Slack that allow you to focus one server or community tools like forums, Lemmy, or VCSaaS which don’t consume resources when you don’t use them, Discord just tanks everything. Since you can’t easily hop in and out (something community tools let you do because, you know, you’re not constantly polling the server), you can’t self regulate.
Every single gaming community, coding community, project, store, hobby group, friend group, and professional group (study group too) has their own Discord. It’s a goddamn nightmare because Discord does not prioritize basic community functionality. Voice and streaming kick ass, but I need some server management and resource optimization.
WebCord is a beast! Maybe runs better for you.
Basically Discord desktop client experience, but privacy (well.. as much as you can have with discord) from the browser-version. (minus discord desktop client exclusive features of course)
Do you have trouble in other programs with Discord running, especially resource-intensive ones? That might have been a better way for me to phrase that.
Anectodal, but I do not. Obviously most channels I am not actively engaged on or have muted but I have over 40 servers I am part of - with no impact to other applications.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.