ralphm

10 ms·

31.
by ralphm 9y ago
Let me first turn this around. I actually personally tried to interact with the Slack team on how they implemented their XMPP gateway, early on. I pointed out how a relatively small missing protocol feature (server-side group chat bookmarki
32.
by ralphm 9y ago
MailGun has been spun out of Rackspace almost a year ago.
33.
by ralphm 9y ago
Article is from 2016. Previous discussion: https://news.ycombinator.com/item?id=11570606
34.
by ralphm 9y ago
The part where playing audio, including that from 3rd party sources, doesn't need Sonos to get any device usage data. However they still want it 'to improve their service', and you can't turn that off. Not accepting term
35.
Sonos: users must accept new privacy policy or devices may “cease to function”(zdnet.com)
271 points by ralphm 9y ago|248 comments
36.
by ralphm 9y ago
#3 is blue for all newborns
37.
by ralphm 11y ago
Note that the example was changed as a result of my initial comment.
38.
by ralphm 11y ago
As mentioned in another thread, don't do this blindly. If there are `Host` or`Match` blocks in the config, this new line will only apply to the last of those blocks.
39.
by ralphm 11y ago
Indeed. The page gives bad advise. If your config has `Host` blocks, like often in people's personal configs, or if you have a `Match` block, the new directive only applies to the last of those blocks in the config file.
40.
by ralphm 11y ago
And only the last `Host` entry in that config, if present.
41.
by ralphm 11y ago
Don't ever fix your `ssh_config` by appending stuff to the end of the file. The configuration syntax allows for block constructs without an explicit end marker (like `Match` and `Host`). Appending will cause all kinds of sadness.
42.
by ralphm 11y ago
I disagree. XML namespaces are URIs and give XMPP distributed extensibility. If you do this in JSON you are just replacing pointy brackets with curly ones.
43.
by ralphm 11y ago
The most valuable thing XMPP gains from using XML is namespaces. The way namespaces have been defined to work on top of XML, is what allows the protocol to be distributely extensible. I.e. anyone can define new protocol without having to
44.
by ralphm 12y ago
Oh, I think we can agree that the situation is far from ideal. But this is to note that nothing has actually changed recently, as opposed to what has been written last week. With the exception of Voice over the old GTalk network, that is. A
45.
No, it’s not the end of XMPP for Google Talk(xmpp.org)
137 points by ralphm 12y ago|62 comments
46.
by ralphm 12y ago
Google did start Jingle and large part of their work ended up in the Jingle standards at the XMPP Standards Foundation. However, Google Talk and the old Hangouts took quite a while to move to the standardized version, and were never fully c
47.
by ralphm 12y ago
In short, it is very unlikely the reasons for abandoning federation, or dropping XMPP altogether with Google Voice, are technical in nature.
48.
by ralphm 13y ago
“The technology of the last 10 years should have all been open to experimentation by developers without locking users in. There are a lot of developers who believe in this. It's central to the mission of WhatsApp, btw, so if you doubte
49.
by ralphm 13y ago
Makes much more sense for what, exactly? There are a number of protocols that have been promoted for use in the Internet of Things arena, for example, including MQTT and XMPP. All of them have different strengths and weaknesses. Cisco did a
50.
by ralphm 13y ago
While yes, it may not excel in beauty, when do applications developers really need to look at, or implement, wire-protocols? Embedding JSON inside an XML element seems to be one of the least horrible things you could encounter. Binary proto
51.
by ralphm 13y ago
This has been discussed many times, but so far, no clear advantage of changing the wire-protocol, to be based on JSON instead of XML, has been shown. Especially if you want to retain distributed extensibility you will mostly end up with cur
52.
by ralphm 13y ago
I have understood that you should definitely try to keep the heap size under 32G as apparently the JVM can only compress pointers below that. Because we do event logging and our documents don't change after being indexed, some of the p
53.
by ralphm 13y ago
You're most welcome. Drop me a line any time.
54.
by ralphm 13y ago
I missed that, but that looks pretty awesome. Thanks for sharing!
55.
by ralphm 13y ago
In our case, most of the metrics come from the events flowing through Logstash, and statsd is on the machines running the Logstash server. Note that we are not using Logstash for shipping log events.
56.
by ralphm 13y ago
I did look at the greater landscape. What I found great about Graphite is the number of functions you have to massage the metrics. Not all metrics come in the same form (total number of bytes received since boot, or number of bytes received
57.
by ralphm 13y ago
What I found most important is to monitor Elasticsearch while doing that tuning. That's when I set up Graphite and StatsD and https://github.com/ralphm/vor . First of, you need to make sure Elasticsearch can lock a
58.
by ralphm 13y ago
Yeah, it takes a bit of tuning, depending on what you want to do with Elasticsearch. There are so many different use cases. I found that especially keeping the heap size for field data down to 40% helped quite a bit, in my case.
59.
Google and Walled Gardens – Farewell XMPP(diversity.net.nz)
2 points by ralphm 13y ago|0 comments
60.
by ralphm 13y ago
It should ship with one, but otherwise see here http://mcabber.com/hg/index.cgi/file/dd8ae0abfc68/mcabber/mc...

More ›