* SketchDeck seems more upfront about their pricing. eSlide and VisualSpiders both ask for consultation to get a price. SketchDeck gives a rough estimate per slide, so at least I know what I'm getting into.
* SketchDeck has a nice and simple site. Presentation does matter.
Google missed the boat because they only hired academics, not hackers.
They didn't need to embrace standards or build APIs, they just had to hire people who knew how to build products that real people outside the valley wanted. Google got lucky with its first product (search), acquired a company to make it a successful business (Adwords), and kept buying companies to try and onboard innovation.
Im not sure google have any clue what people want.
The general impression I get is that they facilitate hundreds and hundreds of projects, let them develop, and if it looks good, let them loose into the wild and see what sticks. Most people only get to see the successful ones. I think the vast majority of these projects never see the wild.
In contrast, I get the impression that other big tech companies lean towards thinking something up, then trying to push on to users.
Perhaps I've just fallen for PR, but thats the impression I get.
Academics of all people should understand the value of having a wide open Internet tied together by search. I don't think that's where they went wrong. I think they let Facebook do their thinking for them, and Facebook has a fairly limited vision that's not at all friendly to the knowledge-building power of the web.
Keep telling your self that. Hackers rarely build things that scale to the size Google needs. A failure for Google has 10 Million signups the first day.
The Product managers are what count in building a new product. Hackers are rarely good product managers.
Academics are only a problem when they don't get user feed back before hand. A good researcher can build product that fits the needs of the users, and when paired with good UI people you get a winning product. Google isn't good at getting user feed back they work like Mathematicians, not like Anthropologists and Psychologists.
Math and Anthropology are still academics. But not in the same field.
Large ISPs sure as hell don't do this (maybe they used to; but not in the last 3 years). They have dedicated cages in their datacenters for external gear that sit at the edge of their network.
Regardless, the word on the Netflix-Comcast situation is that Netflix is indeed hosting the hardware at 3rd party datacenters with a dedicated connection to Comcast. Whether you call it an interconnect or private peering is just semantics; it's a pretty common practice in the industry and technologically, it's no different than having a 10gig fiber link within a datacenter.
I'd say more than 99.9% of WhatsApp users haven't heard of Telegram.
WhatsApp users are mostly not early adopters like you and your friends. They are ordinary people, because WhatsApp is is a simple communication tool targeted to everyone. And that's why they keep doubling their user base.
The uproar in Spain about WhatsApp switching to $1 per year was huge, noisy and... emphemeral. Line got a lot of new signups for a few weeks, but the only person I know that still considers using Line today didn't even have WhatsApp back then (but, like everyone else, does have it now).
It isn't really an issue they can fix. Voicemail and missed call notifications come in from carriers over specially formatted messages. You'd need to develop a new out of band messaging protocol that is as reliable as SMS delivery and get all the 30+ carriers Apple works with globally to roll it out before they could turn off the old stuff.
Yes, it is. But DDoS attacks to EU or the US aren't launched from China/Africa anyway.
You need relatively low capacity to start an amplification attack, so a server at some ISP which doesn't care is enough. There are some ISPs which knowingly allow this, like Ecatel in The Netherlands which is probably the most notorious example.
Your routers wouldn't speak HTTP. Your web service endpoint would talk to your network management middleware, which would then issue your respective IOS/NXOS/JunOS commands to your core or edge gear.
You'd grant your customers the ability to null route traffic from IP blocks (/24 or larger, because ain't nobody got memory to route blocks smaller than that in IPv4) so they wouldn't saturate their links with useless traffic. There was a discussion on the North American Network Operators Group (NANOG) mailing list a few weeks ago.
Disclaimer: I have operated large-scale networks for over a decade.
Sorry, but I call shenanigans on your having operated a large scale network.
Every carrier worth its salt will already let you use blackhole communities to mitigate attacks. You tag it, it gets dropped at the edge of your upstreams networks. Simple and effective. You don't need a web service or middleware for any of this.
Also, a route and netmask (generally) take exactly the same amount of memory regardless of the size of the network you're covering.
Conversion rate isn't the only thing you optimize for. I helped a company reduce its fraud/chargeback rate by asking for the type of card without error correction. A type mismatch was one of a dozen or so scoring items that, if over a specific threshold, tripped a second level of verification.