1,029 karma · joined May 6, 2010
Guess standalone app is the only route to avoid this? I think even Chrome extensions couldn't get around this since they dropped the experimental sidebar thing :/
I think it will take colonising other planets before the world is ready for a new unit of time and at that point the whole concept of 'day' is kind of out the window.
EDIT: Oh.. it's now Symantec, and they will no doubt try and sell you their other products :( ... well at least it used to just be an identity provider.
Whereas a tripod 360 can't include the bass, won't all of these have a coy person directly below pretending to act natural like they didn't throw a ball straight up.
Great little product though.
Checkout the usage for ./go so-far here: http://code.google.com/p/go/source/browse/src/cmd/go/script....
yeah I had though about https not being clear, it will accept your https url, but your right there's no indication that it's ok to type it.
... where bootstrap really shines is that I had a working basic version of the app running and looking pretty good about 6 hours after the idea, I would have spent longer than that in photoshop staring at color swatches. It's the perfect prototyper.
We're aiming for more of a fire-and-forget approach where Erlywarn learns what is acceptable/unacceptable behaviour – next week the notification emails will have a "don't warm me like this" type button in them to help you train the alerts. When monitoring 100's of sites you have some that are more sensitive than others, and we want to remove the "setup" from this.
At the moment that would be flagged as "problem" and you would be alerted. Very soon (few days) the notifications will be much more informative and tell you exactly where and what kind of problem.
RE network & dashboard: Good plan. It does seem silly not to show we are using it too.
RE go; go is really not experimental anymore, and has been an excellent choice for this kind of concurrent problem. We had something similar in Erlang (internally) and this has been so much faster to build and is much simpler. I get your point and wouldn't normally mention it, but if anyone would be interested it's here :)
Thanks for your feedback.
Had zero trouble with Payment Express (known as Direct Payment Solutions to the UK banks). Only thing that is maybe not ideal is the time difference, Payex. are in New Zealand and so email-threads can take several days if you don't ask questions at 1am.
(with the extension that the 'clicking on the session link' could one day be automated behind the scenes)
Where it all falls down is their bizare "pre-pay/top-up" payment system. You have to set your card to periodically to-up your account with the exact amount you need. I really hope they change this if they are going to an even more unpredictable usage plan.
If you opt-out of the pre-pay system, you have to purchase each little component (A vps here, some hard-disk there) as seperate transactions... it's a real pain.
>We will be providing our customers samples of their new bills before the new pricing model is launched so that they will be able to see what will be changing.
[1] http://code.google.com/apis/gmail/gadgets/ [2] http://code.google.com/apis/gmail/docs/inbox_feed.html
...
If Backends are available at versioned URLs too (and I suspect they do/willdo) then there might be nice opportunities to build little Go Backends to do heavy lifting within your main Python applications. Sounds cool.
I believe they are more like Tasks on Steroids than a way of having something like a little persistant VPS for your app.
I had to come here to really understand what I was looking at.
plus a implementation of:
http://gmailblog.blogspot.com/2011/01/new-in-labs-unread-mes...
Sitting up straight solved the cat issue. Maybe a cat will solve your slouch issue.