| 19 Jul 2025 |
 K900 | that's OK we'll fragment matrix real fucking soon | 15:55:28 |
 QuadRadical (Ping) | this room probably isnt the best place for this discussion though | 15:55:32 |
 @magic_rb:matrix.redalder.org | In reply to @quadradical:federated.nexus
theoretically discord bots may work with not too many changes, since the api is compatible The bridges will come if someone writes them and the best bridges happen to be from a company, specifically beeper | 15:55:57 |
| QuadRadical (Ping) | does beeper make the mautrix bridges | 15:56:19 |
| @magic_rb:matrix.redalder.org | In reply to @quadradical:federated.nexus
theoretically discord bots may work with not too many changes, since the api is compatible You need a app service like api, you cant do it with just a normal client api | 15:56:20 |
| @magic_rb:matrix.redalder.org | In reply to @quadradical:federated.nexus
does beeper make the mautrix bridges Yes | 15:56:25 |
| QuadRadical (Ping) | yeah, i think thats planned as well | 15:56:28 |
| QuadRadical (Ping) | ah interesting | 15:56:31 |
| @magic_rb:matrix.redalder.org | So me being on matrix is directly attributed to beeper and element. Idk if i like it, but it is what it is... | 15:57:05 |
 Cat | I will say that i kinda might be to blame for one wave of the thinking that went into creating a Fed API for spacebar even tho as far as i remember the work we are talking about comes way later and they as far as i remember had never heard of my ramblings on the topic. | 15:57:40 |
| Cat | Tho i did talk about that before knowing how much of a shitshow discord is API wise | 15:58:15 |
 @emma:rory.gay | being a discord-ish model was the entire point | 19:53:33 |
| @emma:rory.gay | no | 19:54:59 |
| @emma:rory.gay | they should in theory be compatible without any changes whatsoever, similar to how an official Discord(R) Client(TM) works on spacebar without patching | 19:55:43 |
 emily | surely you need to at least patch the server URL | 19:57:08 |
| @emma:rory.gay | yes but that's not actually part of the client | 19:57:20 |
| @emma:rory.gay | that's all neatly defined in a single script tag in the <head> of index.html | 19:57:40 |
| emily | putting a ton of engineering effort into a greenfield federated chat protocol … to use with Discord clients is weird to me | 19:57:46 |
| emily | like I get people liking Discord's UX and that clients are a lot of work but… if you're putting that much development effort in… | 19:58:14 |
| @emma:rory.gay | the irony is that we cant even ship their client for it, and their desktop client is just a dummy web app wrapper | 19:58:44 |
| emily | why tie it to an API and client designed by a company inherently hostile to what you're doing that will never be match how your actual protocol works | 19:58:51 |
| emily | and that will skew all the work you put in to the actual protocol | 19:59:27 |
| emily | just very odd imo | 19:59:33 |
| @emma:rory.gay | because its meant to be compatible with spacebarchat - which by itself was immensely popular way back when | 19:59:33 |
| emily | pretty sure I've literally never heard of Spacebar in ~a decade (tragically) of using Discord | 20:00:24 |
| @emma:rory.gay | 
Download clipboard.png | 20:00:44 |
| emily | so not sure the piggybacking is helping too much with market penetration there | 20:00:47 |
| @emma:rory.gay | maybe under its old name, fosscord | 20:01:10 |
| emily | feel like I heard the name once or twice and that's it? | 20:03:22 |
| K900 | Hot take: if you're going to emulate an existing protocol just to get free clients, make it fucking Telegram | 20:04:07 |
