+1 We already lost significant user base with Google XMPP federation
going bye-bye, don't want to make this problem worse.
On 2015-09-16 9:08 PM, Mike Barnes wrote:
I'm really hesitant to implement a massive restriction like this
precisely because it is invisible to the end user, and is just
On 2015-07-10 2:47 AM, Mathias Ertl wrote:
* Have a valid 4096 bit certificate with at least a sha256 signature.
4096 bit seems a bit excessive. NIST is still recommending 2048 bit from
2011 to 2030.
-Peter
smime.p7s
Description: S/MIME Cryptographic Signature
On 2013-11-22 7:31 AM, Solomon Peachy wrote:
But I can't sign the manifesto, because I strongly believe committing to
a hard cut-off date for non-encrypted S2S traffic is counterproductive.
- Solomon
I fully agree, and this is the reason I'm not signing the manifesto. I
was recently
On 2013-10-29 4:20 PM, Peter Saint-Andre wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In case you missed it during all the TLS discussion, we've repurposed
xmpp.net to function as an IM Observatory. This makes it easy to
figure out whether your service offers a high level of security.
On 2013-10-28 2:05 PM, Peter Saint-Andre wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/28/13 2:54 PM, Peter Kieser wrote:
What servers currently support this? ejabbered doesn't:
https://support.process-one.net/browse/EJAB-532
XEP-0198 is pretty widely implemented and solves
I can no longer send or receive messages to people that have updated to
Google Hangouts. It shows them as being online, and messages are
successfully sent but they are not received by either party.
-Peter
On 2013-05-16 9:12 AM, Dave Cridland wrote:
The best information I've been given is that
