If you are attending the VON Show in Boston, be sure to check out the VONCamp Unconference. Tired of attending sessions where the same people you have been hearing from are giving the same presentations you already heard? The whole idea is to let whomever shows up select the topics, shape the discussions and share what they know.
"Think of it as constructive anarchy," says Iotum CEO Alec Saunders. "Amazing things can come out of these sessions."
Tom Howe will kick the day off with an "agenda bashing" session, where all attendees will decide on the agenda for the day. After that, 12 sessions of 25 minutes each area available. Anyone can present and everyone is expected to participate in some way.
I'd be willing to bet this is the best use of time most of us could commit at the whole meeting, no offense to the organizers of the more traditional show.
http://5thtrack.pbwiki.com/ is the link.
Showing posts with label Alec Saunders. Show all posts
Showing posts with label Alec Saunders. Show all posts
Sunday, October 21, 2007
VON Unconference is Where the Action Will Be
Labels:
Alec Saunders,
Iotum,
Unconference,
Vonage
Gary Kim has been a digital infra analyst and journalist for more than 30 years, covering the business impact of technology, pre- and post-internet. He sees a similar evolution coming with AI. General-purpose technologies do not come along very often, but when they do, they change life, economies and industries.
Friday, September 7, 2007
Microsoft Vista Service Pack Near Beta
As a follow-up to his email sent to Microsoft execs about Vista issues, Alec Saunders says: "Coincident with my note to Microsoft about Windows Vista quality yesterday, Microsoft let it be known that Vista SP1 would be going into beta in a couple of weeks, and surprise surprise, a substantial focus is on quality."
"Following the email I sent, two Microsoft senior execs responded yesterday — Steven Sinofsky who runs with the Windows platform organization, and Jeff Raikes, President of the Business Division. Among the many things in Raikes' mails was a question about how well I liked Office 2007, a product that I absolutely love. When I told him that, he observed that Sinofsky was the VP in charge of shipping Office 2007, and that he was applying many of the same methodologies to Windows Vista."
"Sinofsky gently chided me for having rose colored glasses, observing that PnP in Windows 95 routinely fried his network cards. Perhaps, he was saying, Windows Vista isn't as bad as I've described it. Nonetheless, he acknowledged that two key areas of focus for his team right now are application compatibility, and the video subsystem. Many of the Windows updates that go out are focused on these two areas, and that seems to be a good chunk of the focus in SP1 as well."
"Time will tell. As John McKinley pointed out, this is a franchise issue for them. They have to get it right."
"Following the email I sent, two Microsoft senior execs responded yesterday — Steven Sinofsky who runs with the Windows platform organization, and Jeff Raikes, President of the Business Division. Among the many things in Raikes' mails was a question about how well I liked Office 2007, a product that I absolutely love. When I told him that, he observed that Sinofsky was the VP in charge of shipping Office 2007, and that he was applying many of the same methodologies to Windows Vista."
"Sinofsky gently chided me for having rose colored glasses, observing that PnP in Windows 95 routinely fried his network cards. Perhaps, he was saying, Windows Vista isn't as bad as I've described it. Nonetheless, he acknowledged that two key areas of focus for his team right now are application compatibility, and the video subsystem. Many of the Windows updates that go out are focused on these two areas, and that seems to be a good chunk of the focus in SP1 as well."
"Time will tell. As John McKinley pointed out, this is a franchise issue for them. They have to get it right."
Labels:
Alec Saunders,
Iotum,
Jeff Raikes,
Microsoft,
Steven Sinofsky,
Vista,
Windows Vista
Gary Kim has been a digital infra analyst and journalist for more than 30 years, covering the business impact of technology, pre- and post-internet. He sees a similar evolution coming with AI. General-purpose technologies do not come along very often, but when they do, they change life, economies and industries.
Wednesday, August 29, 2007
Vista is a Damn Disaster
From: Alec Saunders
Sent: August-29-07 9:54 AM
To: Steve Ballmer; Jeff Raikes; Steve Sinofsky
Subject: regarding Windows Vista
Steve, Jeff and Steve…
I am writing you both because I know you from my days at Microsoft from 1992 to 2001. And to put what I’m about to say in context, I have been a Windows PC user since Windows version 1.02, and my home is stuffed full of PC’s, networks and servers… all running Windows – XP, Vista, Home Server. I worked on the launches of MS-DOS 6, MS-DOS 6.2, Windows 3.1, WFW, NT 3.1, NT 3.51, Windows 95, Windows 98, Windows CE, Windows 98 SE, and Windows ME before leaving the company. I’m a self-professed geek and will willing put up with a lot of pain in order to have the latest technology as well.
Now that you have the context for who I am, I want to tell you that I am seriously losing faith. My experience with Windows Vista has been a rank disaster. At this point, I believe it to be worse than Windows 98, which many consider to be the worst quality Windows product that Microsoft ever released. Specifically:
1. Driver quality is low. The ATI graphics card I have installed in my PC regularly causes a spontaneous reboot. My HP scanner doesn’t have a supported driver anymore.
2. Partner software quality is even worse. For example, over the weekend I installed Sony’s software for the HDR-SR1 (their new high definition camcorder) and lived through a series of spontaneous reboots. On one PC I was able to do a system restore. On another, uninstall worked. However, at this point I am simply unable to retrieve or view video files from that Camera, as they are all recorded in the new AVCHD format.
3. The OS quality is also low. Subsystems sometimes stop working for no reason. The PC I have printers attached to simply decides not to print, periodically. Then the print spooler on all of the other Vista PC’s attached to it simply stops and has to be manually restarted.
4. Microsoft software hasn’t been fully tested on Vista either. I use Foldershare, quite a bit, which works intermittently. My Windows Live OneCare software sometimes works and sometimes not… on some PC’s and not others.
I could go on and on, but suffice it to say it’s no surprise to me that one of the top stories on Techmeme this morning is that one in six new laptops are Macbooks, and not Windows. I myself have seriously looked at abandoning my investment in Windows. My Macintosh owner friends encourage me to do so, and don’t seem to have the same kind of trials with PC’s that I do. They appear to be able to just open them, use them, and put them away. Parents I know are opting to buy their children Mac’s, apparently because it relieves them of the need to be IS manager for the home.
The driver, Microsoft software and OS quality issues are Microsoft’s alone. However, the partner quality issue is an evangelism and certification issue. It seems, from where I sit, that the evangelism effort that the Windows 95 launch team undertook was not matched by the Windows Vista launch team.
This issue impacts me daily. I spend at least an hour a day fixing PC problems, whether on my tablet PC in my office, or at home. I can’t continue this way, and if I can’t I would imagine a lot of other customers can’t either.
Regards,
Alec.
Labels:
Alec Saunders,
Apple,
HP,
Iotum,
Microsoft,
Sony,
Vista,
Windows OS
Gary Kim has been a digital infra analyst and journalist for more than 30 years, covering the business impact of technology, pre- and post-internet. He sees a similar evolution coming with AI. General-purpose technologies do not come along very often, but when they do, they change life, economies and industries.
Thursday, July 19, 2007
Ooma, PhoneGnome
Ooma hopes it can make a business in the independent VoIP space without slugging it out with incumbents, cable companies, Vonage, Packet8 and others. Ooma uses peer-to-peer technology, it reminds me of nothing so much as PhoneGnome. A user can rely on broadband and Ooma, "cutting the cord," or can keep legacy POTS and integrate Ooma with a traditional landline (the easiest way to keep 911 service). All calls within the U.S. market are free, and off-network calls are billed at Skype-like rates.
Like PhoneGnome, the revenue model is "selling boxes," not recurring revenues from services. Ooma is betting that a $400 purchase of a base hub that functions like an analog terminal adapter will appeal more than a VoIP service account. Additional Ooma adapters can be bought to add service to other analog phones on other standard wall jacks.
Perhaps the longest-lasting impact, irrespective of what happens with Ooma, is the P2P approach it uses to create a network. As with all P2P networks, each end user's client becomes a node on the network to help terminate traffic. I don't know what technology platform Ooma uses. It seems logical that Session Initiation Protocol is not what Ooma is doing on the P2P side of its platform, but it seems SIP has to be there someplace for interface to the public network at some level. But David Beckemeyer seems best placed to noodle on that.
Alec Saunders (Iotum)asks an interesting question, however. Ooma says it will try to use member POTS access to essentially avoid paying termination charges. Presumably that means invoking user phone numbers in some way. If caller ID information cannot be spoofed from the POTS phone, but only from the trunk side of the network, does that mean a user's caller ID gets delivered even when it is just a transit node between a calling party and the called party? Details are scanty at this point so I'm not sure anybody outside Oomba knows the answer.
Or maybe there isn't even a problem. Presumably Ooma would try to "terminate" a call at a local Ooma "node" and then use the Ooma P2P to retransmit the bits using the public Internet to the terminating Ooma node with no need to deliver calling number ID information.
One wonders how much longer it will be until even Tier One service providers start to take a closer look at integrating P2P in some significant way with the existing public networks, especially as those networks are upgraded for IP Multimedia Subsystem and there's more broadband in the access network.
Not P2P as an "over the top" end user application. P2P as a part of the architecture of a managed network that simply uses multiple techniques to reach deeper into the environment sitting on the other side of the traditional "network termination" point. Making customers part of the network is starting to look like good business sense.
Like PhoneGnome, the revenue model is "selling boxes," not recurring revenues from services. Ooma is betting that a $400 purchase of a base hub that functions like an analog terminal adapter will appeal more than a VoIP service account. Additional Ooma adapters can be bought to add service to other analog phones on other standard wall jacks.
Perhaps the longest-lasting impact, irrespective of what happens with Ooma, is the P2P approach it uses to create a network. As with all P2P networks, each end user's client becomes a node on the network to help terminate traffic. I don't know what technology platform Ooma uses. It seems logical that Session Initiation Protocol is not what Ooma is doing on the P2P side of its platform, but it seems SIP has to be there someplace for interface to the public network at some level. But David Beckemeyer seems best placed to noodle on that.
Alec Saunders (Iotum)asks an interesting question, however. Ooma says it will try to use member POTS access to essentially avoid paying termination charges. Presumably that means invoking user phone numbers in some way. If caller ID information cannot be spoofed from the POTS phone, but only from the trunk side of the network, does that mean a user's caller ID gets delivered even when it is just a transit node between a calling party and the called party? Details are scanty at this point so I'm not sure anybody outside Oomba knows the answer.
Or maybe there isn't even a problem. Presumably Ooma would try to "terminate" a call at a local Ooma "node" and then use the Ooma P2P to retransmit the bits using the public Internet to the terminating Ooma node with no need to deliver calling number ID information.
One wonders how much longer it will be until even Tier One service providers start to take a closer look at integrating P2P in some significant way with the existing public networks, especially as those networks are upgraded for IP Multimedia Subsystem and there's more broadband in the access network.
Not P2P as an "over the top" end user application. P2P as a part of the architecture of a managed network that simply uses multiple techniques to reach deeper into the environment sitting on the other side of the traditional "network termination" point. Making customers part of the network is starting to look like good business sense.
Labels:
Alec Saunders,
David Beckemeyer,
Ooma,
Packet8,
PhoneGnome,
VoIP,
Vonage
Gary Kim has been a digital infra analyst and journalist for more than 30 years, covering the business impact of technology, pre- and post-internet. He sees a similar evolution coming with AI. General-purpose technologies do not come along very often, but when they do, they change life, economies and industries.
Subscribe to:
Posts (Atom)
Will AI Fuel a Huge "Services into Products" Shift?
As content streaming has disrupted music, is disrupting video and television, so might AI potentially disrupt industry leaders ranging from ...
-
We have all repeatedly seen comparisons of equity value of hyperscale app providers compared to the value of connectivity providers, which s...
-
It really is surprising how often a Pareto distribution--the “80/20 rule--appears in business life, or in life, generally. Basically, the...
-
One recurring issue with forecasts of multi-access edge computing is that it is easier to make predictions about cost than revenue and infra...