@MostlyBlindGamer Yes, my entire afternoon actually got stolen, because I suddenly decided I had to go write an entire mud built around these things, with cool npcs and a world with rules and and and. I think I'm better, now.
@feld I wish Mumble supported WebRTC, though. As it is, doing a web client would be annoying. And everyone seems to want web clients for everything, for reasons I can't understand but must apparently comply with. IRC can do websockets, so there's no issue there. ircv3.net/specs/extensions/websocket@debacle@ltning@jae@evilham
@feld Yes, and that's exactly what I mean by "annoying". If you want people to actually use it, it has to be part of main. Not run a mumble server and then run an IRC server and then also run a websocket proxy thing. And if you're forking mumble to add IRC, and also support websockets for voice, why base on Mumble at all? Now you're just writing your own thing. Might as well do the voice protocol propperly instead of bringing Mumble's legacy issues onboard. @debacle@ltning@jae@evilham
@feld That's wrong. You can do Opus via WebRTC. Opus has all of the features of speex, but also stereo audio and higher samplerates. Nobody should be using speex in 2026. @debacle@ltning@jae@evilham
OMG what am I even doing This is a huge project it's going to need Jingle and that needs WebRTC and then file transfers and voice messages and oh also localization and sounds and hotkeys and settings and multi-account support and Oh God. even with AI this will take fifteen years why did I get out of bed today and choose this for myself
@feld I dropped Jami and signal from my life for the same reason. “Just use the official clients” is not an open protocol. Not even if the client and server are open source.
@feld@jae Nope. These are just running deltachat-core or libdeltachat, from what I can tell. If I want a library in C#, there is none. If I want to write my own library in C#, without depending on deltachat-core, I can't. There's no list of RFCs I can look at, nothing like xeps or IRCV3 caps, etc. It's just "use our library".
@feld@jae It's not, though. Deltachat does weird shit with email headers to anonymize everything. I couldn't just read a message from deltachat in my regular email client. And I have no idea how they're doing federation and key exchange and things. But it's all based on weird links that require deltachat's domains and servers to exist and be running. I can't just type an email in the chat client and send a deltachat message.
@feld@jae Interesting that everyone uses libdeltachat or deltaachat-core, then. There is no ecosystem of standards compliant implimentations. And seemingly no clear idea what that would even mean to deltachat.
@feld@jae That's what we thought with Twitter and Reddit. Then they discontinued the API's. Those are just two recent examples of something that has happened dozens of times in the last 25 years. Slack discontinuing IRC is another. If I depend on an API that could be taken away at any moment, I have nothing. If there are no competing and interoperable implementations of the standard, you're just at the whims of the owner of the one true version.
@feld@jae If I don't like the c# library I'm using to build XMPP, I can rip it out and pick another one. There are like 6 to choose from. If they disable an API I needed, I can build it myself, or use a different library. Those are not options with deltachat.
@arcanechat@feld@jae If deltachat doesn’t want people indipendantly authoring libraries that use its protocol it is not an open standard. End of story.
If you are #blind and still use #irc there's a new adispeak release for you! This one includes the latest adiirc beta, with the fixed and fully accessible settings and server list. It also includes sounds thanks to @FreakyFwoof. If you've never heard of adispeak, it's a script to make adiirc read out IRC messages, in the spirit of sjams or mircspeech, but supporting #NVDA, and based on a more modern IRC client. Get it at: github.com/fastfinge/adispeak/releases/tag/v_0.4#a11y#accessibility#screenreader