Flowdalic

5 ms·

1.
by Flowdalic 2mo ago
You are not alone. Java remains unfairly tethered to a reputation forged over 20 years ago. Human psychology reveals a reluctance to update our worldview: once a collective consensus solidifies, it becomes very difficult to dismantle. Yet,
2.
by Flowdalic 1y ago
> The standardization process comes into play when you think you have found a good solution, which should be adopted by THE standard respectively the ecosystem. Na, the standardization process starts much earlier. Using the example of th
3.
by Flowdalic 1y ago
I am not sure if I would phrase it that way. (Seemingly) conflicting extensions are another consequence of the loosely coupling between standardization and implementations. In addition, the emergence of several functionally overlapping exte
4.
by Flowdalic 1y ago
> Personal speculation but I blame the "everything is an extension" model - it was meant to reduce fragmentation and allow clients with different featuresets to interoperate I could be wrong, but that reads like you suggest tha
5.
by Flowdalic 3y ago
The kernel usually just needs to know which binary to execute as init, which is often provided as kernel command line argument by the bootloader.
6.
by Flowdalic 4y ago
> Even if the application is making 50 byte sends why aren't these getting coalesced once the socket's buffer is full? Because maybe the 50 bytes are latency sensitive and need to be at the recipient as soon as possible? > I
7.
by Flowdalic 4y ago
The problem does not seem to be that TCP_NODELAY is on, but that the packets are sent carry only 50 bytes of payload. If you send a large file, then I would expect that you invoke send() with page-sized buffers. This should give the TCP sta
8.
by Flowdalic 4y ago
It should be possible to install meson via pip --user. Even though I prefer system-wide installations, I believe this weakens your argument for user defined functions in your situation.
9.
by Flowdalic 4y ago
QUIC does a lot more than "the one for TCP". While I also believe that modern TCP consists of more than just one RFC (which you already hinted at). I guess the art in protocol design is to have as few as possible mandatory-to-impl
10.
by Flowdalic 4y ago
Smack uses an XML pull parser and non-blocking I/O. It does so by splitting the XMPP stream top-level elements first and only feeding complete elements to the pull parser.
11.
by Flowdalic 4y ago
I get your confusion. But keep in mind that it is not only about just picking the library that shows as first result of your Google search. My naive self thinks that a million dollar company should do some research and evaluate different op
12.
by Flowdalic 4y ago
> One of the harder things with XMPP is that it is a badly-formed document up until the connection is closed. You need a SAX-style/event-based parser to handle it. That is a common misconception, although I am not sure of its origin
13.
by Flowdalic 4y ago
It appears that Gloox, a relative low-level XMPP-client C library, rolled much of its Unicode and XML parsing itself, which made such vulnerabilities more likely. There maybe good reasons to not re-use existing modules and rely on external
14.
Zoom: Remote Code Execution with XMPP Stanza Smuggling(bugs.chromium.org)
231 points by Flowdalic 4y ago|90 comments
15.
by Flowdalic 4y ago
It is not an RFC, it is an I-D (Internet Draft).
16.
PGPainless 1.0.0 Released(blog.jabberhead.tk)
4 points by Flowdalic 5y ago|0 comments
17.
by Flowdalic 5y ago
Using XML is one of XMPP its biggest strengths. XML is well designed, good documented and has a rich set of supporting libraries. XML documents can be composed of other XML documents in a sound fashion, which is a major feature for an exte
18.
by Flowdalic 5y ago
I wonder why people jump fast to conclusion that to "let XMPP die", when the protocol can also be iteratively improved. Presence is not required in XMPP, its an optional feature. Everything you said has been considered in newer XM
19.
PGPainless 0.2 Released(blog.jabberhead.tk)
1 points by Flowdalic 5y ago|0 comments
20.
by Flowdalic 6y ago
I wouldn't be sure that this is authentic, i.e. actually from John Nagle.
21.
by Flowdalic 7y ago
It still shows sign of ongoing development though: https://github.com/psi-im/psi/graphs/contributors?from=2016-...
22.
by Flowdalic 7y ago
1. Concurrency platforms finally help to utilize multiple cores of a system, as result we will see many-core architectures with plenty simple cores 2. The consequences of quantitative easing will emerge and affect us all 3. Another cryptocu
23.
by Flowdalic 7y ago
> Less standards, less use-cases - for example I don't think xmpp should take care of vcards, nickname and tons You mean you just want to use RFC 6120/6121? That's fine, just do it then.
24.
by Flowdalic 7y ago
> I think it started to die when Google decided the XMPP spec was not good enough for them and deviated from it It was my impression that Google dropped XMPP support not because of the spec being "not good", but because they sa
25.
by Flowdalic 8y ago
Link to his stackoverflow answers sorted by votes: https://stackoverflow.com/users/254279/thomas-pornin?tab=ans...
26.
by Flowdalic 8y ago
First, let me say thank you for your efforts towards making DNS more accessible for implementors. Could you elaborate on "CNAME chasing to other zones: let’s not" and "Adding glue from other zones: let’s not"?
27.
XMPP echo bot written in sed(github.com)
2 points by Flowdalic 8y ago|0 comments
28.
by Flowdalic 9y ago
I would recommend XEP-0050: Ad-Hoc Commands [1] for this. 1: https://xmpp.org/extensions/xep-0050.html
29.
by Flowdalic 9y ago
That is a very pessimistic view on the current state of LN. There are three independent open-source LN implementations [1, 2, 3] out there that are being worked on and already implement basic functionality. All three contribute to an docume
30.
by Flowdalic 9y ago
BCC was a hard fork

More ›