Discord in Early Talks With Bankers for Potential I.P.O.
-
I can't wait for Discord to enshittify so that lazy devs can't say "join our Discord for updates and support!" anymore.
Hate that shit.
It's quite shit already
-
Could we add Zulip? I think it even has IRC integration if I’m not mistaken.
-
Its the closest thing I've found to the discord experience, but it still feels young (I.e. buggy and laggy, UI feels off in a few places). Other than that its almost 1:1
-
Unfortunately this is probably going to be a buy for me.
Seeing how the market reacted to the enshittification of Reddit, means that Discord probably has a lot of upside on the share price. The parallels between the two services can’t be ignored.
reddit and discord goes hand in hand, since they often are used in conjuction with each other, where they are censured on reddit they go and complain discord.
-
That explains all the AI crap they've been chasing for a while now. They've been trying to juice up the value to make it look appealing to potential buyers because you can basically slap "AI" on anything and it instantly shoots up in value.
Discord is effectively dead if this goes through.
much like reddit its other counterpart is doing right now. Juicing up its value by "eliminating tons of accts regardless of the status of those acc"
-
This post did not contain any content.
Duuude. Discord is a dumpster fire right now. I'm interested to see how much hotter that fire can get.
-
That explains all the AI crap they've been chasing for a while now. They've been trying to juice up the value to make it look appealing to potential buyers because you can basically slap "AI" on anything and it instantly shoots up in value.
Discord is effectively dead if this goes through.
It has been in the works from the very beginning. They dropped their mask when things got put behind paywalls and they started censoring criticism. Hell they artificially pumped up emote slots on servers they were secretly running just to get the most users on them. why? To control the narrative. Those servers had the most users for this reason and their owners were thrilled about becoming essentially redundant over night which was more than just a little suspicious until they got found out. They also run their subreddit where they also censored any criticism for this weird bait and switch.
To those who say „who cares about emotes?“ I can only reply: You‘re missing the point. It‘s not about the what but the how. Discord is a sleazy company that gaslights their users to an extreme degree sometimes.
-
Welp, there goes the neighborhood. If they want to do an IPO they'll probably enshittify the hell out of the platform and jettison all remotely raunchy communities. Because nothing says "good investment" than a service that just drove out a fair chunk of its user base.
I just hope Enshittification will cause devs to ditch it and start using proper forums instead. It‘s always tragic when a software has no other way of giving feedback and answering questions than Discord where you can‘t find anything, let alone with an external search engine. The abandonment of internet forum culture and searchable discussions has been one of the biggest losses in the virtual space.
-
I can't wait for Discord to enshittify so that lazy devs can't say "join our Discord for updates and support!" anymore.
Hate that shit.
Fiiiiiiiiiinally.
How can it not be awful for them too? Like users may even try to
️search Discord️ for their issue only to come up short and have fo ask a question asked a million times already. Gross. -
I really wish Matrix had been more successful, but it has some pretty core problems that prevented it from gaining more traction.
It fell into the same trap as XMPP, though perhaps even worse, with a focus more on its protocol and specification than a single unified product vision.
The reference server implementation is slow, and using a language not optimal for its purpose, with alternative server implementations left incomplete and unsupported.
It took a long time for them to figure out voice and video and for it to work well, and the "user flow" still isn't at Discord levels.I've rooted for Matrix for a long time, but as a former XMPP evangelist, to me the writing on the wall says it isn't suited for success either. I'd love to be wrong, but I don't see a way through.
What do you think the main problems are?
In terms of performance, there's Rust in the synapse repo already, and both Conduit (Rust) and Dendrite (Go) seem viable. If one of those projects reaches parity with Synapse, do you think that'll "fix" matrix?
If not, are there other issues core to matrix design? I'm not that familiar with matrix except as an occasional user that follows a few tech rooms, but I'd love to help out if I'm pointed in the right direction. I'm comfortable with Rust and Go (and do Python at my day job), so if backend performance is a bottleneck, I could make help out.
But if the problems are fundamental to how it's designed or how the project operates, I'd rather work on other things.
-
This post did not contain any content.
It's good timing that I've been learning Docker to run Jellyfin and *arr. Guess I'll look into throwing matrix or mattermost on there now, too.
-
This post did not contain any content.
I wonder if Flotilla on Nostr will be ready in time. The nostr community can unfortunately be a bit iffy right now, but I like the tech, and I'm always excited to see someone taking a good stab at Discord.
-
I wonder if Flotilla on Nostr will be ready in time. The nostr community can unfortunately be a bit iffy right now, but I like the tech, and I'm always excited to see someone taking a good stab at Discord.
Soon as you hear the term instance, most people are out.
-
Soon as you hear the term instance, most people are out.
Call it a server, then. Tons of people already call them Discord servers. And it'd be a lot more true of Flotilla than Discord. Functionally, from a UX perspective, there'd be VERY little difference to an end user. You'd get an invite somehow, probably through a link, maybe combined with whitelisting your identity for more private communities, and you'd be in, using a client remarkably similar to Discord once it's in a good spot. For most users, they can fully ignore the technical complexities.
-
What do you think the main problems are?
In terms of performance, there's Rust in the synapse repo already, and both Conduit (Rust) and Dendrite (Go) seem viable. If one of those projects reaches parity with Synapse, do you think that'll "fix" matrix?
If not, are there other issues core to matrix design? I'm not that familiar with matrix except as an occasional user that follows a few tech rooms, but I'd love to help out if I'm pointed in the right direction. I'm comfortable with Rust and Go (and do Python at my day job), so if backend performance is a bottleneck, I could make help out.
But if the problems are fundamental to how it's designed or how the project operates, I'd rather work on other things.
I do think the other home server implementations gaining parity (production-ready) with the reference home server would go a long way. I haven't run a home server but I've heard from those that have that it really has a hard time scaling. (Though this serves as impetus to give it a try over spring break)
Which brings me to the caveats of the protocol, I personally don't think the design is ideal, it's more described as a distributed message bus, what I've read of the spec it's over engineered, it made good decisions wrt using modern web technologies (JSON, WebRTC), but it didn't scope itself to the particular task.
That said, I haven't written a federated protocol, and they have.
But if I was going to, I'd really want to look at Discord and see how to copy a lot of that model, but break parts of it out to facilitate federation:I originally wrote a huge hypothetical design here that I speculated would fare better, but honestly the specifics become less relevant, point is that the shared state of rooms is a real challenge, and one out of scope for just a federated instant messaging system, and I'm no longer certain it's viable.
-
This post did not contain any content.
Finally, I hope Discord's inevitable enshittification will be the kick in the ass that will launch a platform that doesn't gargle donkey balls - preferably someting fediverse capable.
-
Duuude. Discord is a dumpster fire right now. I'm interested to see how much hotter that fire can get.
Enough to power cities that run out power because Canada cut them off.
-
Getting my friends to shift over is a pain in the ass for sure
I have my friends and family on Matrix.
My instance is over 7 years old.
Love it, can't imagine being without it.
-
I do think the other home server implementations gaining parity (production-ready) with the reference home server would go a long way. I haven't run a home server but I've heard from those that have that it really has a hard time scaling. (Though this serves as impetus to give it a try over spring break)
Which brings me to the caveats of the protocol, I personally don't think the design is ideal, it's more described as a distributed message bus, what I've read of the spec it's over engineered, it made good decisions wrt using modern web technologies (JSON, WebRTC), but it didn't scope itself to the particular task.
That said, I haven't written a federated protocol, and they have.
But if I was going to, I'd really want to look at Discord and see how to copy a lot of that model, but break parts of it out to facilitate federation:I originally wrote a huge hypothetical design here that I speculated would fare better, but honestly the specifics become less relevant, point is that the shared state of rooms is a real challenge, and one out of scope for just a federated instant messaging system, and I'm no longer certain it's viable.
I'm personally more interested in P2P protocols than federated, so that's the stuff I build in my spare time.
So instead of something like Lemmy or Matrix, I'd have something like BitTorrent or Tor, so nodes just add capacity instead of hosting specific content. You could configure your node(s) to pin specific content (e.g. for backups or latency), but your data would also be distributed to other peoples' computers.
This provides data redundancy, permanency of the service (no centralization whatsoever), and ease of scaling (every client could store and seed data), but comes with complexity. I think it's workable though.
-
Apparently at least one person is working, fairly successfully, on a server clone. I think it was this one, but I only know about it from one YouTube video I watched weeks ago.
Sadly Pidgin dropped oscar (aim protocol) support years ago because undeveloped and insecure. So either install a plugin or use the old clients.
On the up side, a complete understanding of the server protocol means new clients can be written.
