Update Email Provider Database with the "163.com" entry

[iscas-zac]

Hello, I'm very interested in this app and tried it with a newly created 163 account (while my other 126 accounts has no spare auth codes). It seems that your descriptions are out of date for the provider, so I updated it a little. I'm not very familiar with your guideline here, so adjust the wording as you like.

By the way, while the e-mail system is the only mature decentralized system and apt for the chat data communication, I'm really curious whether is there any way to directly chat between two clients without the server (which is really what p2p means), considering the complicated network factors like IPv4/NAT, proxy, firewall, ad-hoc wireless network connection and so on. Are there any progress for the mission impossible? Thanks.

[r10s]

By the way, while the e-mail system is the only mature decentralized system and apt for the chat data communication, I'm really curious whether is there any way to directly chat between two clients without the server (which is really what p2p means)

you have luck 🍀

yesterday, we introduced "realtime Peer-to-Peer networking" for webxdc apps - and one of the demo apps is a chat app :)

https://delta.chat/en/2024-11-20-webxdc-realtime#live-chat-realtime-chat-in-a-chat-

[iscas-zac]

yesterday, we introduced "realtime Peer-to-Peer networking" for webxdc apps

Good, I'll read it more carefully and try out. That page seems to focus on the ephemeral side of this app, and I am not aware whether it still requires the mail server or not.

PREPARATION always requires a before_login_hint, sth. as:

I have not reviewed change before. Does this require my commits, or you will handle this alone?

[r10s]

if you think, my suggestion makes sense, i will merge that and then this PR

[iscas-zac]

Of course it makes more sense than my pure intuition, as I have no idea about the database formats. Thanks for reviewing.

[missytake]

Thanks!