Downside is that the quick terminal doesn't support tabs. Unfortunately that's currently a dealbreaker for me.

You can always run tmux inside. I personally don't use tabs in my terminal emulator at all, because I use tmux tabs for everything.

It may not work for you, of course.

{"message":"Missing Authentication Token"}

Which API are you trying to call ? This doesn't look like one of my error messages.

I assume the example numbersapi that is loaded by default.

I got the same thing. Leaves me wondering what to do next. It's not clear, then I figured I'll try this curl command, then an error and still nothing obvious to try next.

Formatting.

How does it compare to e.g. ActiveMQ? http://activemq.apache.org/

We are currently getting DDoSed at Hetzner and they are clueless as well.

If you're planning on getting DDoSd you probably should pick a provider that offers DDoS protection.

Not sure why you'd choose a budget provider for production infra anyway.

> If you're planning on getting DDoSd

This, don't do it, far better to not get DDoSd ;-)

Surely any org that depends on internet presence would plan against DDoS attacks. That's like internet 101.

I just had to deal with a defective Anker Cable after 5 months.

Interesting, me too (4 months) - the charge will cut in and out randomly, although looking at the cable it seems to be in perfect condition still. Makes playing music through my car's USB port a challenge, as it's rare to be able to play more than two songs in a row without a disruption. Disappointing.

Why should it not be similar faster on mobile?

No only different instruction set, but probably drastically different cache hierarchy and branch predictors. The tool cachegrind which they are using is simulating a program's effect on the cache and branch predictor, which will likely both be dramatically smaller in embedded devices vs modern server CPUs, so the results may be very misleading to real world applications for sqite.

Also multicore memory hierarchies are very different on ARM -- e.g. atomics are much more expensive there in my experience.

Different instruction set. The release notification isn't very clear about what optimizations took place. It is quite possible that it will not be the same result on a different architecture.

Even moreso, different cache sizes. Some object that might fit nicely in a 4kB cache might get destroyed with a 1kB cache.

He never said it shouldn't, just that he would be interested in seeing the numbers. I would be too since they would be more relevant to my use case.

Does not work for iOS yet? Edit: "At this time, WhatsApp Web is available only for Android, Windows Phone, Nokia S60, BlackBerry and BB10 smartphones." https://www.whatsapp.com/faq/en/web/28080003

"Unfortunately for now, we will not be able to provide web client to our iOS users due to Apple platform limitations." http://blog.whatsapp.com/614/WhatsApp-Web

<del>Assumption: WhatsApp for iOS is in the 5 business day App Store approval queue.</del>

"Unfortunately for now, we will not be able to provide web client to our iOS users due to Apple platform limitations."

And even if they could, I'd doubt that they'd make Facebook wait 5 days for their app to be aproved.

Assumption: the platform limitation is that it's not allowed to run an app (continuously) in the background, which is required for WhatsApp web

It's not the browser ... the iOS app doesn't yet have the capability to scan the QR code to link your account to the website

> They have been much slower adopting features than the competition.

It's not a matter of speed. This seems to be using WebRTC for handling communications between the phone app and the browser. Safari has chosen not to implement WebRTC and so far it is still not a proper standard so I can see why. Google, as the developer of WebRTC, will obviously support it right away. Note that no browser other than Chrome can be used as well.

Wait, you know that WebKit is spearheaded by Apple? And that there's two completely unrelated problems here:

1. The frontend only works on Chrome for desktop (it appears only because it uses the non-standards track filesystem API)

2. The backend service and mobile app does not work with iOS (it appears because it uses background networking)

They may seem related, but they aren't.

That doesn't seem likely to me: what features does iOS not have right now, that this is likely to use? It seems more likely if they are targeting chrome only they did it to avoid the support overhead of making it work in multiple browsers.

Install or sign in?