User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
2d
So because I have gone temporarily off my rocker, I'm working on an client using 10 and WPF, with artalk-xmpp for XMPP, libsignal for , and prism for screen reader output where needed. I'm only an evening into it, and I can already tell that OMEMO is going to be the source of complicated, inexplicable, and unreproducible bug reports for decades to come. It's still not as overcomplicated as , though.
9
5
8
0
User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
2d
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
4
1
4
0
User avatar
Only 3 Easy Payments of $19.95 @feld@friedcheese.us
2d
@fastfinge there's always Delta Chat which solved almost all of these problems already :)
2
0
2
0
User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
2d
@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.
1
0
2
0
User avatar
Only 3 Easy Payments of $19.95 @feld@friedcheese.us
1d
@fastfinge you're completely wrong we have third party clients and more coming all the time

github.com/trufae/parla

lambadalambda.github.io/estuary/

Unreleased tui client by @jae
1
0
2
0
User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
1d
@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".
2
0
4
0
User avatar
Only 3 Easy Payments of $19.95 @feld@friedcheese.us
1d
@fastfinge @jae there is no "library" to write. It's PGP emails and SMTP/IMAP. Go ahead and do it yourself, there's nothing proprietary being implemented. It's just emails.

Name a feature that you think is some secret proprietary thing
1
0
1
0
User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
1d
@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.
2
0
3
0
User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
1d
@feld @jae Or if it is, it's not developer friendly at all. For XMPP, I can look at the list of xeps to know exactly what my client needs to implement to achieve various levels of compatibility with the standard: xmpp.org/extensions/

Same for IRCV3, the list of rfcs and extensions is all right there: ircv3.net/irc/

I have no idea where any of this info lives for deltachat. The website and github don't make it obvious. What parts of email do I need? What parts of PGP do I need? I guess I need to do autocrypt based on your message. But what is the name of the standard that deltachat is even targeting? Chatmail, I guess? What do I need to have to be a "chatmail compatible client"? Are there test suites I should pass?
1
0
3
0
User avatar
Only 3 Easy Payments of $19.95 @feld@friedcheese.us
1d
@fastfinge @jae the main website says "built on internet standards" and links here:

github.com/chatmail/core/blob/main/standards.md
2
0
1
0
User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
1d
@feld @jae And that document is either out of date or false. Deltachat's misuse of subject lines, date smearing, etc, are absolutely in violation of the RFCs. Notice they never claim they follow or comply with the standards. They're just "based on them". Just following those standards will not result in a client that in any way can be used seamlessly with other deltachat users, or is guaranteed to interoperate with them.
2
0
1
0
User avatar
ᴏᴏᴍ-ᴋɪʟʟᴇʀ: 333[𝟱𝟬𝗽𝘀𝗶 𝘁𝗼𝗶𝗹𝗲𝘁]™ @jae@bsd.cafe
1d
@fastfinge @feld most of the docs are out of date. its something i wanted to fix but didn't work out so i stopped trying to hop the gatekeepers
0
0
1
0
User avatar
Only 3 Easy Payments of $19.95 @feld@friedcheese.us
1d
@fastfinge @jae
Deltachat's misuse of subject lines, date smearing, etc, are absolutely in violation of the RFCs.
No it's not. The subject and date headers are that way because we've found mail servers that will not accept completely removing them even though that's fully supported by RFC 9788. If you have never heard of this RFC before, it's what allows you to disregard ALL plaintext headers and put them all inside the PGP encrypted part.

datatracker.ietf.org/doc/rfc9788/
0
0
0
0