coi-specs
coi-specs copied to clipboard
Align with DeltaChat
I hope I'm not late to the party, but this definitely looks like a smaller brother of the widely used production-level software package DeltaChat (native clients for Android & iOS, electron app for Windows, *nix, macOS).
How about aligning both projects?
DeltaChat is much much more mature, is well funded with quite large user base and established developer base, so aligning both seems like a good idea.
This project serves to represent the specification that Delta Chat uses.
See Delta Chat among other partners here: https://www.coi-dev.org/coi-partners/
Wow, I totally missed that. Could all the partners (and alike) be made more visible? Preferably even here on github - maybe putting a link to "partners" (I'd rather call it "implementors") directly in the organization description and maybe even into README.md
s of each repo?
I don't think I'm the guy to make that call, though I guess you're free to submit a PR.
@robert-virkus ?
Hi, yep, it's totally fine to also mention Delta Chat here, I will align that with Holger and Björn from the Delta Chat project.
Delta Chat and COI share a lot of sentiments and goals, so it definitely makes sense to align.
Right now there are still lots of differences between the COI and the Delta Chat approach, just for example:
- Delta Chat is client only, ie not changing IMAP or SMTP server side functionality - COI strives to work with existing email services but works on improving the server side and introduces new server capabilities
- COI strives to be even more compliant than Delta Chat when it comes to normal email users, ie on COI the
To
andCC
email fields are used to identify the group participants, no other Delta Chat-only fields.
Hope this helps, Robert
Perfect, thanks @robert-virkus . If you need something, I'd be happy to help.