Zash

12 ms·

91.
by Zash 9y ago
Must everything be over HTTPS? Must all diversity really be killed like this? It saddens me.
92.
by Zash 9y ago
But what format is the data sent to the server in?
93.
by Zash 9y ago
It took me a long time to understand what you were talking about, the first few results on that Google search did not have any dates at all.
94.
by Zash 9y ago
What open source hardware would that be, and how can everyone eligible to vote be able to understand how it works and be able to observe that it really does work?
95.
by Zash 9y ago
This is why I really like the federated client-server model. It's a pretty good compromise between centralized and peer-to-peer. Much easier to wrap your head around than p2p, while only a little more complicated than something centra
96.
by Zash 10y ago
https://swift.im/ is cross platform client that strives to do things right. Some of the more modern features are available in the latest beta.
97.
by Zash 10y ago
I saw nothing like that in the API when I had a look. But there's always the trusty ol' tar format.
98.
by Zash 10y ago
> XMPP tried to address this and failed XMPP aint't dead yet ;)
99.
by Zash 10y ago
A hash function takes variable length input and returns a fixed length output, that's all. Then there are sub-categories optimized for things like use in hash tables or building blocks in crypto, all with varying emphasis on uniquenes
100.
by Zash 10y ago
Personally I'm a fan of running unbound locally. DNSSEC verification on the same machine is pretty nice, but you lose the benefits of sharing the cache with many others.
101.
by Zash 10y ago
True, neither architecture will ultimately solve the problem of an attacker having absolute control over the lower layer. No way around it. Federation does has the nice property that it gives you some choice over who controls the infrastru
102.
by Zash 10y ago
I wasn't aware that they had switched entirely, only that they invented their own custom compression and (really bad) authentication and encryption methods.
103.
by Zash 10y ago
I think this comes from people attempting to roll their own low-level XMPP clients top of generic XML libraries, which is a recipe for having a bad time. Also, people who connect Pidgin to their Gmail and think that is the pinnacle of XMPP
104.
by Zash 10y ago
Did you know that WhatsApp uses XMPP?
105.
by Zash 10y ago
crickets
106.
by Zash 10y ago
Well, to be pedantic, it got assigned a XEP number.
107.
by Zash 10y ago
Re GNU Social polish, have you seen the frontend Qvitter? Eg https://quitter.se/ and repo at https://git.gnu.io/h2p/Qvitter
108.
by Zash 10y ago
You could try http://swift.im/
109.
by Zash 10y ago
Not easy, but it can be applied to XMPP: https://blog.thijsalkema.de/blog/2014/08/07/https-attacks-an...
110.
by Zash 10y ago
I remember SIP as being very HTTP-like. Looking at https://tools.ietf.org/html/rfc3261#section-4 this seems to be accurate. > SIP is based on an HTTP-like request/response transaction model. The protocol wire f
111.
by Zash 10y ago
> Related: [comment from 1977 days ago] Yes, people have been bashing XMPP forever. http://stpeter.im/journal/1384.html The XMPP protocol is quite qualified to compete with WhatsApp, considering they are using XMPP
112.
by Zash 10y ago
Then why, every time XMPP is mentioned, do droves of people praising Matrix and bashing XMPP show up out of nowhere?
113.
by Zash 10y ago
XMPP is great, NOT a JSON hellhole, and has its own implementation of Axolotl for private messaging: https://conversations.im/omemo/ And Conversations is pretty great too. etc...
114.
by Zash 10y ago
> There is no easy way to tell if your server supports them, either. False. XMPP has excellent feature negotiation capabilities. > everyone using Conversations essentially has to use a server that is maintained by the developers No, y
115.
by Zash 10y ago
XMPP is alright. It will never be perfect, but it keeps improving, and that's important. Personally I believe more in having people be in control of their own communications than having ultra secure crypto. No crypto is going to help i
116.
by Zash 10y ago
They really just dropped support and left it a broken mess. It kinda looks like you can federate with them if you disable TLS, but messages are apparently just dropped. This is worse than if they just killed it, as people tend to blame XMPP
117.
by Zash 10y ago
Emphasis on in 2014 , that was forever ago in Internet time. XMPP is steadily moving forward and the things mentioned in that post have improved a lot. Check out https://conversations.im/ for example.
118.
by Zash 10y ago
If federation is too hard then I don't think P2P, which is even harder, will be considered.
119.
by Zash 10y ago
They had an XMPP interface, yes. It allowed you to sign into FB Messenger using any XMPP client. But it was very limited and did not follow modern XMPP practices. Then they killed it in favor of MQTT, which isn't even an IM protocol.
120.
by Zash 11y ago
The real problem is that the problem keeps changing. XMPP adapts. There's some friction. XEPs get written to deal with it. Life goes on. Someone invents yet another variation of IM and the cycle repeats.

More ›