1,880 karma · joined November 17, 2013
* No desktop client
* Connected to your google account meaning I'll need to juggle several google accounts to keep my personal and business chats separate
Just the fact it doesn't have a native desktop client makes it unusable. I know there are workarounds I can use like nativefier but it's still not as smooth as a desktop app.
Running in the browser:
- Gets grouped with my other browser windows in my taskbar, making it hard to find
- Notifications might or might not work, depending on firefox's whims
- If for any reason firefox crashes all your communication crashes with it
- Susceptible to every single browser bug that allows silent loading of extensions that scrape all your data
// X - uncommented on 1.2.03 to fix bug
// Y - commented again on 3.2.03 because it broke stuff
// if (condition)
{
... logic here, half of it commented out ...
}Then, you take the universal authorisation request authorisation token and hand it off to the counter incrementing authorisation server which gives you a counter incrementing authorisation token.
Then, you take the counter incrementing authorisation token to your local counter incrementing server and ask it to increment the counter by 1.
In turn, your local counter incrementing server checks that your counter incrementing authorisation token was indeed signed by the central authorisation server and issues a counter incrementing operation to one of the 8 central counter incrementing servers.
Of course, your local counter incrementing server is itself authorised by the central authorisation server and the counter incrementing authorisation server to issue authoritative counter increment operations; so if its own local counter incrementing authorisation token has expired (5 minutes), it also has to do steps 1-3 to renew its authorisation to perform authoritative counter incrementing operations. This doesn't concern you, as all those requests are buffered so this section is purely informative.
Your own authorisation tokens also have expirations (5 minutes for the unviersal authorisation request authorisation token and ~10 seconds for the specific authorisation tokens) so you best issue your requests promptly and make sure to renew the tokens. Should your token expire before you have completed your counter increment request to your local counter increment server, perform steps 2-4 (or 1-4 if more than 5 minutes have elapsed since you acquired your universal authorisation request authorisation token).
Expect to receive a counter increment confirmation message within the next 2 full moons by carrier pigeon.
Super simple stuff.
On the other hand, DNS could fix this - just have a TLD of ip6 and have it resolve all the examples in the article. It would require no changes to current software and will work transparently. I.e. you'd enter http://deadbeef.ip6:1234 and when the ip6 TLD servers receive a request for deadbeef.ip6, they will reply with dead:beef:0:0:0:0:0:0. Similarly with deadbeef.1.ip6 and so on. You could easily implement this in the OS too without much hassle and not even need servers on the internet to do it.
This of course applies to private individuals, not companies, banks or other institutions.
To expand:
Touch your right thumb to the small bone on your right pinky finger that is closest to the palm - this is 1. Move it up one bone (phalanx) - this is 2. Move it one more to the tip of your pinky - this is 3. Then you continue with your ring finger - 4, 5, 6 and when you reach the tip of your index finger, you're at 12. Now raise one finger on your left hand for 1 * 12 and continue with your thumb on the first phalanx of your pinky - 13. Once you've raised all 5 fingers on your left hand you're at 5 * 12 = 60 and when you then place your thumb on the tip of your index finger, you're at 72. It's easy and quick after only a bit of training and lets you count practically all numbers you'll ever want to count on your fingers.
The occasional malfunction is to be expected.