<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: New Sputnik Community Gateway 1.1 released!</title>
	<atom:link href="http://www.sifry.com/alerts/2002/05/new-sputnik-community-gateway-1-1-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sifry.com/alerts/2002/05/new-sputnik-community-gateway-1-1-released/</link>
	<description>Dave Sifry&#039;s Musings</description>
	<lastBuildDate>Wed, 10 Nov 2010 05:38:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Dave Sifry</title>
		<link>http://www.sifry.com/alerts/2002/05/new-sputnik-community-gateway-1-1-released/comment-page-1/#comment-12</link>
		<dc:creator>Dave Sifry</dc:creator>
		<pubDate>Tue, 18 Jun 2002 22:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.sifry.org/alerts/?p=28#comment-12</guid>
		<description>It really came down to this: We couldn&#039;t figure out a way to make money
doing the joltage/boingo thing, i.e. get people to set up hotspots and
then do revenue shares with the hotspot operators.  Essentially, there
are two big problems with the model:
1) AUPs.  Most inexpensive wireless broadband access have some pretty
restrictive Acceptable Use Policies, and they usually include a &quot;no
sharing your bandwidth&quot; provision.  Of course, the way around this is to
work out deals with the cable co&#039;s and ILECs so that we give a revenue
share back to them as well.  Unforunately, the slices of the pie keep
getting slimmer and slimmer, even if you assume that you can work a deal
with the local monopoly^H^H^H^H^H^H^H^H^H broadband provider.
2) Customer Service. Know the cornerstone reason why AOL was so
profitable for so many years?  Because they perfected the art of
eliminating customer service calls.  This is the bane of so many
thin-margin businesses (see point 1 above).  One call to your 800 number
can blow your profit on that customer for the month, or even the year.
Now factor into the equation that you don&#039;t control AP placement,
coverage, equipment, or internet uplink, and the customer service issues
start to look VERY unattractive.  Think about what happens when someone
is paying you $19.95/month, getting great access via their neighbor&#039;s
DSL connection, and then their neighbor decides to move.  All of a
sudden you have a dissatisfied customer, and absolutely no way to
control or predict when these situations will arise.  Have it happen
enough times and your reputation is totally shot.
So, we decided to change our model.  We still believe in secure
authenticated roaming, and we still believe in community networking, all
we did was remove the subscriber fee and revenue share part of the
model.  This way, people can set up nodes, and can easily particiapte in
a worldwide network of free community nodes as well.
If you want to be a commercial WISP, great, more power to ya, we&#039;re glad
to sell you the infrastructure and management software that will turn
you into a WISP.  If you want to deply secure 802.11 networks across
your enterprise, you can take proven technology and authenticate against
your chosen single-sign-on system, be it RADIUS, LDAP, NDS, Active
Directory, or whatever, and the APs enforce policy, like bandwidth
shaping and per-user firewalling based on that policy as well.
I hope that further clarifies what we at Sputnik did, and where we
stand in relation to all the great community network initiatives out
there.
Dave
</description>
		<content:encoded><![CDATA[<p>It really came down to this: We couldn&#8217;t figure out a way to make money<br />
doing the joltage/boingo thing, i.e. get people to set up hotspots and<br />
then do revenue shares with the hotspot operators.  Essentially, there<br />
are two big problems with the model:<br />
1) AUPs.  Most inexpensive wireless broadband access have some pretty<br />
restrictive Acceptable Use Policies, and they usually include a &#8220;no<br />
sharing your bandwidth&#8221; provision.  Of course, the way around this is to<br />
work out deals with the cable co&#8217;s and ILECs so that we give a revenue<br />
share back to them as well.  Unforunately, the slices of the pie keep<br />
getting slimmer and slimmer, even if you assume that you can work a deal<br />
with the local monopoly^H^H^H^H^H^H^H^H^H broadband provider.<br />
2) Customer Service. Know the cornerstone reason why AOL was so<br />
profitable for so many years?  Because they perfected the art of<br />
eliminating customer service calls.  This is the bane of so many<br />
thin-margin businesses (see point 1 above).  One call to your 800 number<br />
can blow your profit on that customer for the month, or even the year.<br />
Now factor into the equation that you don&#8217;t control AP placement,<br />
coverage, equipment, or internet uplink, and the customer service issues<br />
start to look VERY unattractive.  Think about what happens when someone<br />
is paying you $19.95/month, getting great access via their neighbor&#8217;s<br />
DSL connection, and then their neighbor decides to move.  All of a<br />
sudden you have a dissatisfied customer, and absolutely no way to<br />
control or predict when these situations will arise.  Have it happen<br />
enough times and your reputation is totally shot.<br />
So, we decided to change our model.  We still believe in secure<br />
authenticated roaming, and we still believe in community networking, all<br />
we did was remove the subscriber fee and revenue share part of the<br />
model.  This way, people can set up nodes, and can easily particiapte in<br />
a worldwide network of free community nodes as well.<br />
If you want to be a commercial WISP, great, more power to ya, we&#8217;re glad<br />
to sell you the infrastructure and management software that will turn<br />
you into a WISP.  If you want to deply secure 802.11 networks across<br />
your enterprise, you can take proven technology and authenticate against<br />
your chosen single-sign-on system, be it RADIUS, LDAP, NDS, Active<br />
Directory, or whatever, and the APs enforce policy, like bandwidth<br />
shaping and per-user firewalling based on that policy as well.<br />
I hope that further clarifies what we at Sputnik did, and where we<br />
stand in relation to all the great community network initiatives out<br />
there.<br />
Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay R. Ashworth</title>
		<link>http://www.sifry.com/alerts/2002/05/new-sputnik-community-gateway-1-1-released/comment-page-1/#comment-11</link>
		<dc:creator>Jay R. Ashworth</dc:creator>
		<pubDate>Mon, 10 Jun 2002 16:54:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.sifry.org/alerts/?p=28#comment-11</guid>
		<description>And the Unique Selling Proposition to potential sites goes away... and the fire goes out.
Tell me why I&#039;m wrong.
</description>
		<content:encoded><![CDATA[<p>And the Unique Selling Proposition to potential sites goes away&#8230; and the fire goes out.<br />
Tell me why I&#8217;m wrong.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

