<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for gzino</title><link>http://disqus.com/by/gzino/</link><description></description><atom:link href="http://disqus.com/gzino/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 24 Apr 2017 22:36:00 -0000</lastBuildDate><item><title>Re:  Don’t Make the Internet Safe for Monopolies</title><link>http://blog.tomevslin.com/2017/04/-dont-make-the-internet-safe-for-monopolies.html#comment-3272854972</link><description>&lt;p&gt;agree, Tom, and nicely put @Daniel Berninger "the prospect of government as the antidote to telco/cableco misbehavior is laughable given the track record you note":&lt;/p&gt;&lt;p&gt;also you could argue the hypothetical ISP behavior of prioritizing their own content (or purposely degrading content from others) would actually help open the door for alternative ISPs and methods.&lt;/p&gt;&lt;p&gt;note: we do have a real need to increase local ISP competition.  unfortunately, "net neutrality", regardless of how it plays out, is serving as a distraction to addressing that need.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Mon, 24 Apr 2017 22:36:00 -0000</pubDate></item><item><title>Re: Sending Stuff To The Wrong People</title><link>http://avc.com/2015/02/sending-stuff-to-the-wrong-people/#comment-1870729726</link><description>&lt;p&gt;gmail mobile upgrade rolled out to two of my Androids this wkd; perhaps related.  I see the same (bad) behavior on those, one non-upgraded Android and web.&lt;/p&gt;&lt;p&gt;especially for sharing cloud content (dropbox etc) with groups (as opposed to individuals), will it be much longer before API integrations enable us to choose a group to share with (defined by a name we give it), rather than need to type in list of emails?&lt;/p&gt;&lt;p&gt;Ideally with a 'group DNS' type layer that enables us to define a group as collection of mobile numbers that can then be used by multiple mobile apps (with sufficient authentication layer)?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Mon, 23 Feb 2015 09:42:32 -0000</pubDate></item><item><title>Re: Dear Internet: Let&amp;#8217;s Demo The Slow Lane</title><link>http://feld.com/archives/2014/05/dear-internet-lets-demo-slow-lane.html#comment-1373560674</link><description>&lt;p&gt;Agree on the themes however we (US) are still top 10 in the world for retail IP, and most of the rest of the world is not close, so this is not just a US problem (consider China and India alone; e.g. I have employees in India that can't get a good enough retail connection to do a video call with me from home, and that's using a video service that we specifically engineer to deal with bad networks).&lt;/p&gt;&lt;p&gt;That said, agree "real broadband" is critical to our future, it is inexcusable that we don't get there and a slow lane day is a terrific idea for raising awareness.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Wed, 07 May 2014 11:34:27 -0000</pubDate></item><item><title>Re: Is Google Inadvertently Supporting SBCs?</title><link>http://www.webrtcworld.com/topics/from-the-experts/articles/378016-google-inadvertently-supporting-sbcs.htm#comment-1373544085</link><description>&lt;p&gt;I am anti-trapezoid for many use cases, and video transcoding is painfully expensive, but we can't put this all on Google's broad shoulders or even the video codec:&lt;/p&gt;&lt;p&gt;1. Even w/ homogeneous media codec, firewalls, web proxies, security policies and NAT are making most implementations into trapezoids, especially in the enterprise space.  Sometimes "just" signaling but often media as well.&lt;/p&gt;&lt;p&gt;2. Many (if not most) developers still favor VP8 as a single MTI.&lt;/p&gt;&lt;p&gt;3. Video is only one part of WebRTC.  Even apps that do need video have options for many use cases, e.g. try P2P video but if it doesn't negotiate then try P2P voice or trapezoid video.  Of course (1) above may mean that neither P2P voice nor P2P video work...but in that case the issue is not the video codec...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Wed, 07 May 2014 11:22:02 -0000</pubDate></item><item><title>Re: The decline of the mobile web</title><link>http://cdixon.org/2014/04/07/the-decline-of-the-mobile-web/#comment-1322805411</link><description>&lt;p&gt;Share the concern but not sure if the data is skewed by mobile gaming (and mobile gaming is more gaming appliance replacement than it is web replacement)?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Mon, 07 Apr 2014 15:12:10 -0000</pubDate></item><item><title>Re: Teaching Computer Science To High School Students On The Way To Work</title><link>http://avc.com/2014/04/teaching-computer-science-to-high-school-students-on-the-way-to-work/#comment-1314797574</link><description>&lt;p&gt;Awesome.  Hope to see this model extended across other education domains as well, e.g. life sciences, increasing the probability that each student discovers experts and fields that resonate.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Wed, 02 Apr 2014 09:13:11 -0000</pubDate></item><item><title>Re: Sidecar</title><link>http://avc.com/2014/02/sidecar/#comment-1251611269</link><description>&lt;p&gt;Agree, personal is certainly difficult to build and even harder to scale, but we will see a wave of attempts.&lt;/p&gt;&lt;p&gt;On the demand side, most verticals are in races to the bottom, meaning most people/users/consumers are eating commoditized products/services and developing an appetite for more personal ones.&lt;/p&gt;&lt;p&gt;Meanwhile, on the "supply side" (in a sense), we know mobile/compute/Internet is making it feasible and viable for some companies to feed these appetites in profitable and sustainable manner.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Wed, 19 Feb 2014 10:41:36 -0000</pubDate></item><item><title>Re: Sidecar</title><link>http://avc.com/2014/02/sidecar/#comment-1251538438</link><description>&lt;p&gt;Love the Etsy-Amazon analogy.&lt;/p&gt;&lt;p&gt;Believe personal will be the next wave in a few verticals.  We know personal is hard to replicate, commoditize or automate.&lt;/p&gt;&lt;p&gt;Whereas efficiency can be race to a wide bottom - one Pacific Ocean "winner" per widely defined industry, believe personal can be a climb to the top of many peaks - customized/individualized/narrower scope sub-verticals.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Wed, 19 Feb 2014 09:50:18 -0000</pubDate></item><item><title>Re: Google&amp;#8217;s three Ps</title><link>http://www.asymco.com/2014/01/17/googles-three-ps/#comment-1215589782</link><description>&lt;p&gt;Great article.&lt;/p&gt;&lt;p&gt;This sentence is interesting:&lt;/p&gt;&lt;p&gt;"For all the technology innovations the company can claim, it has not had one internally sourced business model innovation"&lt;/p&gt;&lt;p&gt;I would classify their initial product - AdWords - as business model innovation.  I know Yahoo (and maybe others) dipped their toes in selling ads based on a user's perceived intent (as determined by their search strings), but Y! and others always fundamentally seemed to be basing their business models on selling content?  And of course Google wrapped self-serve etc. around AdWords, essentially inventing a business model?&lt;/p&gt;&lt;p&gt;Maybe the argument is that Google's investment in search algorithms essentially caused that business model, but I am not sure if Google would have invested in their search technology (and self-service etc) to the degree that they did if they weren't convinced of the business model itself (and ultimately funded by it)?&lt;/p&gt;&lt;p&gt;These days, I completely agree: one of the world's most powerful labs and we are often at the mercy (good or bad; knowingly or unknowingly) of the experiments.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Fri, 24 Jan 2014 17:59:48 -0000</pubDate></item><item><title>Re: VC Pitches In A Year Or Two</title><link>http://avc.com/2014/01/vc-pitches-in-a-year-or-two/#comment-1203425112</link><description>&lt;p&gt;"The problem in the USA is too much regulation and artificial monopolies, not a lack of regulation".  Perfect line.&lt;/p&gt;&lt;p&gt;And I would add that the outcomes we are most worried about - harming the little guys in order to build their own profits - are not nearly as likely as we fear.&lt;/p&gt;&lt;p&gt;With or without NN regulation, the ISPs would do it if they could do so in a sustainable, profitable manner.  15 years of VoIP experience tells me that they can't.&lt;/p&gt;&lt;p&gt;And, if I am wrong, and they can, then they would find a way to do it around the regulation, w/ the regulation being costly, full of unintended consequences, and hard to unwind when the world changes.  See the current PSTN landscape for a perfect example.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Wed, 15 Jan 2014 23:04:17 -0000</pubDate></item><item><title>Re: Taking To Dos and Moving Up The Y Axis</title><link>http://avc.com/2013/12/taking-to-dos-and-moving-up-the-y-axis/#comment-1165700594</link><description>&lt;p&gt;Excellent way to articulate that framework.&lt;/p&gt;&lt;p&gt;Probably there (haven't watched the video yet) but imo the key is the steps before the conversations:&lt;/p&gt;&lt;p&gt;1. Hire the people that fit what you need and don't compromise&lt;br&gt;2. Put those folks in a position to succeed - high expectations but viable expectations&lt;br&gt;3. Nail the "what you want to accomplish in the meeting" part - focus your "request"&lt;br&gt;4. Keep eyes and ears open - objectively process the inputs - tweak 1-3 accordingly.&lt;/p&gt;&lt;p&gt;When those elements are in place, very few conversations tend to move up the y-axis to begin with, and the good manager manages the ones that do.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Mon, 16 Dec 2013 08:48:03 -0000</pubDate></item><item><title>Re: Thanksgiving</title><link>http://nextblitz.com/blog/thanksgiving/#comment-1120271836</link><description>&lt;p&gt;in response to the sm pings...yes, my post was intended to be critical of wal-mart's announcement to start their black friday sales on thanksgiving...sorry i don't do a great job writing these types of snarky posts.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Tue, 12 Nov 2013 17:20:26 -0000</pubDate></item><item><title>Re: Decoding WebRTC with Erik Lagerway</title><link>http://www.talkingpointz.com/interview/decoding-webrtc-with-erik-lagerway#comment-1108631593</link><description>&lt;p&gt;Erik makes great points - the API/SDP/signaling are far more important than video codec.&lt;/p&gt;&lt;p&gt;That said, I believe innovative implementations such as Hookflash will make these issues mainly moot in the long-term.  It will cover them up from end user perspective and developers will be able to *afford* the extra time, pain and cost.&lt;/p&gt;&lt;p&gt;Telecom is moving from needing to innovate and solve problems in purpose built hardware to software and web solutions.  Orders of magnitude faster and cheaper, and ultimately more powerful.  That is the disruption of WebRTC (and similar), imo.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Mon, 04 Nov 2013 14:06:50 -0000</pubDate></item><item><title>Re: VP8 vs H.264 in Real Deployments</title><link>http://www.webrtcworld.com/topics/from-the-experts/articles/358425-vp8-vs-h264-real-deployments.htm#comment-1103955191</link><description>&lt;p&gt;The codec discussion itself is very interesting and gets even more interesting when we consider the rest of the package.&lt;/p&gt;&lt;p&gt;Does the device have hardware echo cancellation? How good are the jitter buffer implementations and packet loss concealment methods? What is the webcam doing or trying to do when it "sees" constraints?  Is the client too CPU-intensive?  Etc.&lt;/p&gt;&lt;p&gt;This will be a critical issue for the industry as WebRTC helps move communications off of dedicated, purpose-built, integrated hardware/software, and we simultaneously get increased variety in the last mile (3G, 4G, WiFi, asymmetric DSL, etc.).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Thu, 31 Oct 2013 14:53:52 -0000</pubDate></item><item><title>Re: A Stealthy Video and WebRTC Acquisition</title><link>http://www.webrtcworld.com/topics/from-the-experts/articles/358422-stealthy-video-webrtc-acquisition.htm#comment-1103943108</link><description>&lt;p&gt;Great points. Hadn't thought about it in those terms.&lt;/p&gt;&lt;p&gt;If you are a Fidelity-sized shop, and you want to RTC enable your applications in a high QoE, secure, user-friendly (integrated, SSO, etc.) manner, then you need internal Vidtel type skills. Especially with what I assume is a high number of proprietary apps, some of which need revamping to properly integrate RTC.&lt;/p&gt;&lt;p&gt;Almost an aqui-hire?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Thu, 31 Oct 2013 14:44:39 -0000</pubDate></item><item><title>Re: How Apple iBeacon Will Transform Local Commerce</title><link>http://stevecheney.com/how-apple-ibeacon-will-transform-local-commerce/#comment-1068219822</link><description>&lt;p&gt;Great post.  A couple other potential uses:&lt;/p&gt;&lt;p&gt;1. Niche case but one may of us are interested in...auto disable of cell phone while driving:&lt;/p&gt;&lt;p&gt;&lt;a href="http://nextblitz.com/blog/ibeacons/" rel="nofollow noopener" target="_blank" title="http://nextblitz.com/blog/ibeacons/"&gt;http://nextblitz.com/blog/i...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;2. P2P mesh networks, including ad-hoc.  Use iBeacons + multipath TCP (also in iOS 7).  iBeacons for power efficient peer/network advertising/discovery/selection.  MPTCP to help maintain sticky TCP and TLS sessions during network changes, as well as to aggregate bandwidth across multiple interfaces.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Wed, 02 Oct 2013 22:31:51 -0000</pubDate></item><item><title>Re: WebRTC and enterprise security</title><link>http://nextblitz.com/blog/webrtc-enterprise-security/#comment-1057646036</link><description>&lt;p&gt;KJ, great points.  I should have included an entire section on app and protocol centered possibilities.  To your point innovation in those areas (albeit in a proprietary manner) was a large part of the Skype win.&lt;/p&gt;&lt;p&gt;Not sure NAT goes away, even with IPv6, due to the amount of "carrier NAT" we are seeing and concerns (real and perceived) on direct IPv6 address exposure?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Tue, 24 Sep 2013 17:37:09 -0000</pubDate></item><item><title>Re: There Are Too Many Choices for Video</title><link>http://www.webrtcworld.com/topics/from-the-experts/articles/352891-there-too-many-choices-video.htm#comment-1057056155</link><description>&lt;p&gt;Completely agree.  Although the shelves are increasingly stocked with video options, don't they currently look too similar?  55 cloud covered boxes of toasted oats?&lt;/p&gt;&lt;p&gt;I don't see the diversification, yet (variety in targeted niches, GTM, business model, technical, operational, etc).&lt;/p&gt;&lt;p&gt;But do think we end up with app specific video (and comms in general), maybe the initial overstocking of the generic cereal is just a necessary starting point while the market and technology evolves?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Tue, 24 Sep 2013 09:35:30 -0000</pubDate></item><item><title>Re: TwilioCon - Empowering Software People</title><link>http://www.webrtcworld.com/topics/from-the-experts/articles/354027-twiliocon-empowering-software-people.htm#comment-1057045287</link><description>&lt;p&gt;Nice post, glad to see some focus on the underrated cultural side of this developing ecosystem.&lt;/p&gt;&lt;p&gt;Software (and the web) has certainly eaten telecom.&lt;/p&gt;&lt;p&gt;Do you think there will eventually be some pendulum swing back towards self-contained/vertically integrated communications services over time?&lt;/p&gt;&lt;p&gt;I think the API model is here to stay, and the Twilios of the world are the new telcos, but usually when the waves all go one way, there are opportunities left in the wake for other approaches.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Tue, 24 Sep 2013 09:28:53 -0000</pubDate></item><item><title>Re: The Google and Vidyo Partnership Enters a New Phase: Scalable WebRTC</title><link>http://www.telepresenceoptions.com/2013/08/the_google_and_vidyo_partnersh/index.php#comment-1022127526</link><description>&lt;p&gt;If there are more *teeth* in the agreement (or behind the agreement) then meets the eye, then agree this is a great win for Vidyo.&lt;/p&gt;&lt;p&gt;However, could this mainly be Vidyo PR to counteract the negative attention of the announcement that Google is taking Vidyo out of Hangouts (and a favor from Google to support the PR; a favor earned by Vidyo being a good Hangout partner)?  For example, there is no guarantee that standards decisions or Chrome implementations will end up in Vidyo’s favor when the dust settles, regardless of what Vidyo agrees to contribute.&lt;/p&gt;&lt;p&gt;All that said, SVC is powerful and if Vidyo can get enough support from Google and others to add it to future WebRTC implementations then that has significant upstream impacts on the overall architecture including signaling, SBCs and MCUs...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Thu, 29 Aug 2013 12:36:34 -0000</pubDate></item><item><title>Re: Personal WebRTC Portals</title><link>http://www.webrtcworld.com/topics/from-the-experts/articles/349716-personal-webrtc-portals.htm#comment-1003897159</link><description>&lt;p&gt;hmmm, good point, enterprises are yet another angle.  possibly their experience trying to manage enterprise users within their own app stores will be instructive there, at least for the large enterprises?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Fri, 16 Aug 2013 13:04:40 -0000</pubDate></item><item><title>Re: Personal WebRTC Portals</title><link>http://www.webrtcworld.com/topics/from-the-experts/articles/349716-personal-webrtc-portals.htm#comment-1002751344</link><description>&lt;p&gt;Very interesting.&lt;/p&gt;&lt;p&gt;Possible that we end up with (n) "personal portals" as our current sites add WebRTC capability?&lt;/p&gt;&lt;p&gt;You give good example of how an exciting opportunity for WebRTC is enablement of new comms paradigms, rather than just replacement of old.  More of those new paradigms in this post, would love your thoughts:&lt;/p&gt;&lt;p&gt;&lt;a href="http://nextblitz.com/blog/long-tail-webrtc/" rel="nofollow noopener" target="_blank" title="http://nextblitz.com/blog/long-tail-webrtc/"&gt;http://nextblitz.com/blog/l...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Also what are your thoughts on users eventually running our own personal portals?  Meaning providers making it easy and secure enough for ordinary users to run on our own domains and home network based web servers?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Thu, 15 Aug 2013 16:20:21 -0000</pubDate></item><item><title>Re: Google Glass: Twitter&amp;#039;s Vine Could Be The Killer App - by Brian S Hall</title><link>http://readwrite.com/2013/05/02/twitter-vine-is-the-killer-app-for-google-glass#comment-882935972</link><description>&lt;p&gt;Brian, love it, pocket-to-hand-to-video will quickly seem like work compared to the Glass experience.  Two more thoughts for you:&lt;/p&gt;&lt;p&gt;1. The amount of photos/videos generated by Glass will be ridiculous...added to our already tiny signal to noise ratio...huge opportunity for ecosystem innovation assuming Google exposes enough attributes via Glass APIs?&lt;/p&gt;&lt;p&gt;2. Enterprise videoconferencing...yes, stodgy old enterprise video: &lt;br&gt;&lt;a href="http://goo.gl/YxmfF" rel="nofollow noopener" target="_blank" title="http://goo.gl/YxmfF"&gt;http://goo.gl/YxmfF&lt;/a&gt;&lt;/p&gt;&lt;p&gt;What do you think?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Thu, 02 May 2013 21:25:23 -0000</pubDate></item><item><title>Re: For $19, An Unlimited Phone Plan, Some Flaws</title><link>http://allthingsd.com/20130219/for-19-an-unlimited-phone-plan-some-flaws/#comment-805970860</link><description>&lt;p&gt;Agree, this is glimpse of future.&lt;/p&gt;&lt;p&gt;Over time, we will develop apps that auto choose the network, behind the scenes, e.g. avoid bad WiFi networks for RTC, as opposed to always blindly trying WiFi first.  SPs can adjust their pricing accordingly, whereas for the user it just works.&lt;/p&gt;&lt;p&gt;Hopefully, we will also see more unlicensed spectrum and have more than just WiFi and 3G/4G to choose from in future.  Multiple access networks with smart apps and platforms gluing them together for the end user on a per use case basis.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Wed, 20 Feb 2013 13:59:35 -0000</pubDate></item><item><title>Re: The US Needs A New Spectrum Policy</title><link>http://avc.com/2013/02/the-us-needs-a-new-spectrum-policy-/#comment-805145708</link><description>&lt;p&gt;Is five 9s from one centralized solution the goal of tomorrow?&lt;/p&gt;&lt;p&gt;I would prefer a distributed, diverse set of access options as part of an antifragile (Taleb) system.  The type of set best developed in an open environment.&lt;/p&gt;&lt;p&gt;Multiple dumb access options, none individually at five 9s, with smart, agile, continually evolving apps, platforms, glue and interfaces to stitch it together (behind the scenes) for me as a user, even on a per use case basis when sensible.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gzino</dc:creator><pubDate>Tue, 19 Feb 2013 22:48:57 -0000</pubDate></item></channel></rss>