4 ms·

> Keeping a persistent connection to your server [...] is not a simple problem But is already solved. Explanations : "The State of Mobile XMPP in 2016" https:/

by apichat 10y ago

> Keeping a persistent connection to your server [...] is not a simple problem But is already solved. Explanations : "The State of Mobile XMPP in 2016" https://gultsch.de/xmpp_2016.html https://gultsch.de/xmpp_2016.html > Federation has the problem of being harder to prevent abuse. Precisely XMPP have already solutions for this problem > And when you control the whole infrastructure, it's easier to provide a good user experience. With federation, you are depending on the quality of other's implementations. Answers here : "Objection to ‘The ecosystem is moving’" https://gultsch.de/objection.html https://gultsch.de/objection.html You might also interest by GnuNameSystem wich is a federate, decentralize and censorship resistance DNS https://gnunet.org/gns https://gnunet.org/gns

cesarb 10y ago
Thanks for the links. It seems my knowledge was outdated. Do you have any links for the "solutions for the abuse problem" part? They should make for interesting reading.
- apichat 10y ago
  > solutions for the abuse problem A solution is using address like greeting@name (meaning localpart@dnspart) https://linuxfr.org/users/apichat/journaux/salut-toto-salutation-regle-editoriale-et-nom-sur-internet https://linuxfr.org/users/apichat/journaux/salut-toto-saluta... An other solution is the design of XMPP : you can control who can speak with you (the contact list).
sliken 10y ago
So basically if you are an expert. Find/install a XMPP client, then register/buy/install an XMPP server. Oh you probably want some SRV DNS entries as well. Then ensure your client and server support and have enabled XEP-0198, XEP-0313, XEP-0352, XEP-0280, XEP-0363, XEP-0374, XEP-0357 then in theory you can have a reasonable user experience. However in reality opening a TCP connection to a server will silently drop and all the discussed behavior depends on the cellular provider sending an RST packet back when that happens.... which often doesn't. So because google negotiates with carriers to not time out GCM connections those don't time out. Unfortunately other connections do, thus the power efficiency of other push based approaches on android.

by apichat 10y ago

cesarb 10y ago

Thanks for the links. It seems my knowledge was outdated. Do you have any links for the "solutions for the abuse problem" part? They should make for interesting reading.

apichat 10y ago
> solutions for the abuse problem A solution is using address like greeting@name (meaning localpart@dnspart) https://linuxfr.org/users/apichat/journaux/salut-toto-salutation-regle-editoriale-et-nom-sur-internet https://linuxfr.org/users/apichat/journaux/salut-toto-saluta... An other solution is the design of XMPP : you can control who can speak with you (the contact list).

sliken 10y ago

So basically if you are an expert. Find/install a XMPP client, then register/buy/install an XMPP server. Oh you probably want some SRV DNS entries as well. Then ensure your client and server support and have enabled XEP-0198, XEP-0313, XEP-0352, XEP-0280, XEP-0363, XEP-0374, XEP-0357 then in theory you can have a reasonable user experience. However in reality opening a TCP connection to a server will silently drop and all the discussed behavior depends on the cellular provider sending an RST packet back when that happens.... which often doesn't. So because google negotiates with carriers to not time out GCM connections those don't time out. Unfortunately other connections do, thus the power efficiency of other push based approaches on android.