Flowdalic

10 ms·

31.
by Flowdalic 9y ago
A common mistake made by "self-appointed" bitcoin experts and IMHO a good indicator for more red flags. > On one side are those who believe that Bitcoin is … money, currency, …. On the other side are those who believe that it
32.
Prosody 0.10.0 released(blog.prosody.im)
1 points by Flowdalic 9y ago|0 comments
33.
How to Add a REPL to Your (JVM-Based) Project, Using Ammonite and Gradle(geekplace.eu)
1 points by Flowdalic 9y ago|0 comments
34.
by Flowdalic 9y ago
> The reliance on OCB is unfortunate. I wish the Mosh developers would introduce multiple cipher schemes so that people can move away from OCB. Isn't OCB an open standard? https://www.rfc-editor.org/rfc/rfc7253.
35.
by Flowdalic 10y ago
What if the call site does not use the returned value?
36.
by Flowdalic 10y ago
Care to extend on that "polymorphic signature trick"?
37.
Ask HN: Significant commit rate decline of Android's base repository?
28 points by Flowdalic 10y ago|5 comments
38.
by Flowdalic 10y ago
As of now I recommend everybody to use Prosody stable as XMPP server running on Debian stable. Enable the Prosody modules that provide the XEPs mentioned in Daniel's blog post and/or in XEP-0375: XMPP Compliance Suites 2016[1]. Yo
39.
by Flowdalic 10y ago
Your claim that XMPP is a bandwidth-hungry, but in my experience, if XMPP based systems drain battery and consume a lot of bandwidth, then it's because of a poor implementation and design decisions, and not because of the protocol.
40.
by Flowdalic 11y ago
Right, shouldn't have thrown them all together. Corrected the comment.
41.
by Flowdalic 11y ago
OTR [1], Axolotl [2] and OMEMO [3] all provide Perfect Forward Secrecy, which in turn means that you can't (or should not be able to) read your archived messages. And with OTR can't send messages to offline contacts. OpenPGP does
42.
OX (OpenPGP for XMPP): A New OpenPGP XEP(mail.jabber.org)
58 points by Flowdalic 11y ago|25 comments
43.
by Flowdalic 11y ago
Addendum: As Zash pointed out[1], this is documented behavior for offline messages, i.e. messages send while the user was offline. Those are only send if the user announced availability via a presence or if XEP-13: Flexible Offline Message
44.
by Flowdalic 11y ago
I don't think that aspect is intentionally ignored, it's just that most FOSS projects are seriously understaffed, and the UX/UI part is not a high priority item compared to getting it to work.
45.
by Flowdalic 11y ago
Course, you shouldn't poll and if those mechanisms aren't coordinated, then you you will suffer. But that's why Android provides the AlarmManager API and I would expect other mobile platforms to provide something similar.
46.
by Flowdalic 11y ago
I use my mobile XMPP connections without a TCP keepalive but send a server ping if there has been stanzas received in the last 30 minutes and get a useful and reliable XMPP connection without a noticeable impact on battery. If you use And
47.
by Flowdalic 11y ago
> I don't know how accurate Android's power estimates are, but I consistently have people telling me that they are switching back to proprietary messengers because every XMPP client they've tried drained their battery. Wha
48.
by Flowdalic 11y ago
tl;dr It's being worked on (or already solved), but I'm sure the XMPP community welcomes additional contributors. 1-3. Could be solved with upcoming versions of XEP-313 MAM. 4. e2e There is currently a XSF GSOC project running, br
49.
by Flowdalic 11y ago
Idle TCP connections do not consume any battery. And on a data connectivity change, e.g. GSM <-> WiFi switch, there is a good chance that a dozen other components start trying to re-establish their connections, which means the radio i
50.
by Flowdalic 11y ago
> For example, every client that successfully connected to an XMPP server must first send a "<presence>" message. Otherwise, it won't receive any messages despite their successful connection. That statement is wrong.
51.
by Flowdalic 11y ago
> 1. XMPP is not battery-friendly on mobile devices (this primarily has/had to do with the absence of push notifications, it seems). I do use XMPP in a mobile environment without any noticeable impact on battery runtime. It's n
52.
by Flowdalic 11y ago
It appears the opposite is true. ffmpeg is more or less a one man show. See http://thread.gmane.org/gmane.linux.debian.alioth.multimedia... and https://lwn.net/Articles/650816/ "I think the s
53.
by Flowdalic 11y ago
> tarsnap had a signal handler that was reading from a constant array. So what, how could this matter? The standard says thou shalt not. An references to the standard (I assume he is referring to POSIX) where this is disallowed?
54.
by Flowdalic 11y ago
You are absolutely right. I usually encourage people to get involved in improving the (XMPP) situation. Just last week I submitted a XEP for unique stanza IDs to the XSF [1], which will most likely be the base for IDs in MAM and other proto
55.
by Flowdalic 11y ago
"If the user grants a permission, the system gives the app all permissions that the app manifest lists for that functional area." It's unclear from the site if "functional area" == "permission group". But
56.
by Flowdalic 12y ago
XEP-136 is a good example why it's a bad idea to squeeze everything into a single specification (or XEP in this case): The reason it was not implemented by most XMPP stacks was, because it's so much you have to implement. XEP-313
57.
by Flowdalic 12y ago
That is not my observation. It is also not clear what you mean with "get upgraded to Hangouts". I use Hangouts extensively, but I use also Gajim as client for my Google account and still I'm able to add XMPP contacts from non