FCC Rules on Conflict of Interest at Comcast

Posted by Bill McGonigle Fri, 22 Aug 2008 05:53:00 GMT

Following up on my March 2007 article Conflict of Interest at Comcast, in excerpt:

Odds are those high-traffic users are downloading video. … This is directly in competition with Comcast’s other, main, business, providing video services. The amount of traffic they’re killing at (~250GB/mo) is probably just about what you need to replace a Comcast video service.

the FCC yesterday ruled:

Comcast had an “anticompetitive motive” because it delayed and blocked peer-to-peer files through applications such as BitTorrent. Such files often are high-quality video that might otherwise be watched and paid for on cable television.

and ordered Comcast to behave. As I noted earlier, this mirrors a previous decision about DSL companies monkeying with VOIP traffic.

del.icio.us:FCC Rules on Conflict of Interest at Comcast digg:FCC Rules on Conflict of Interest at Comcast reddit:FCC Rules on Conflict of Interest at Comcast spurl:FCC Rules on Conflict of Interest at Comcast wists:FCC Rules on Conflict of Interest at Comcast simpy:FCC Rules on Conflict of Interest at Comcast newsvine:FCC Rules on Conflict of Interest at Comcast blinklist:FCC Rules on Conflict of Interest at Comcast furl:FCC Rules on Conflict of Interest at Comcast fark:FCC Rules on Conflict of Interest at Comcast blogmarks:FCC Rules on Conflict of Interest at Comcast Y!:FCC Rules on Conflict of Interest at Comcast smarking:FCC Rules on Conflict of Interest at Comcast magnolia:FCC Rules on Conflict of Interest at Comcast segnalo:FCC Rules on Conflict of Interest at Comcast

Twittervision

Posted by Bill McGonigle Thu, 10 Jul 2008 15:19:00 GMT

Twittervision is combines Tweets and geo coding to show a realtime display of what people are Twittering. It’s quite a beautiful thing to watch, especially the 3D view.

I guess I wasn’t aware that Twitter fed all updates to third parties, so that’s something important to be aware of - it’s not just your followers who are seeing your updates.

I’m not sure it’s actually useful, but it certainly is neat, so probably it is useful to somebody.

I wonder if Twitter will be coming up with a trademark licensing program to allow apps like this to live peacefully.

del.icio.us:Twittervision digg:Twittervision reddit:Twittervision spurl:Twittervision wists:Twittervision simpy:Twittervision newsvine:Twittervision blinklist:Twittervision furl:Twittervision fark:Twittervision blogmarks:Twittervision Y!:Twittervision smarking:Twittervision magnolia:Twittervision segnalo:Twittervision

Fonality Astroturfing FreePBX?

Posted by Bill McGonigle Fri, 27 Jun 2008 15:49:00 GMT

Have a read here and boggle in disbelief.

I used to run Trixbox on my PBX; I started when it wasn’t a commercial product, and Tim did a great prezo on it for SLUG. When they required registration to run the software I became very uncomfortable. When I couldn’t administer my PBX one day because their server was down, I switched to Elastix, and I couldn’t be happier - I should have done it sooner; it’s a superior product.

If you’re still sitting on the fence, this behavior from Fonality is likely to knock you square off it. That Fonality relies so heavily on FreePBX only makes it so much more inconceivable. Assuming this is true, only the dismissal of the individual involved could regain any trust the community once had in Fonality.

Oh, and BTW, a FreePBX backup and restore makes it fairly simple to switch from Trixbox to Elastix.

del.icio.us:Fonality Astroturfing FreePBX? digg:Fonality Astroturfing FreePBX? reddit:Fonality Astroturfing FreePBX? spurl:Fonality Astroturfing FreePBX? wists:Fonality Astroturfing FreePBX? simpy:Fonality Astroturfing FreePBX? newsvine:Fonality Astroturfing FreePBX? blinklist:Fonality Astroturfing FreePBX? furl:Fonality Astroturfing FreePBX? fark:Fonality Astroturfing FreePBX? blogmarks:Fonality Astroturfing FreePBX? Y!:Fonality Astroturfing FreePBX? smarking:Fonality Astroturfing FreePBX? magnolia:Fonality Astroturfing FreePBX? segnalo:Fonality Astroturfing FreePBX?

Missing Sync and the Garnet VM on Nokia n810

Posted by Bill McGonigle Mon, 12 May 2008 21:23:00 GMT

In the long and continuing saga to have a decent mobile Internet solution that is friendly to Free Software, I’ve been working out a porting strategy to get rid of my Treo 650, which, while it’s been useful, is now beyond the end of its useful life. The replacement for the Treo is a Nokia n810, which is not a phone, but can use a phone over Bluetooth to get Internet access. It’s a great little linux box, with a Mozilla-based browser with Flash and wealth of 3rd party apps via .deb repositories. Wifi, bluetooth, GPS, etc. Meanwhile, I want a phone with good phone audio quality (pretty much rules out smartphones - bummer), EVDO, Bluetooth, and 4+ hours talk time (so I can run it all day without charging). A flip-phone is really what I want, to avoid accidental dialing in my pocket (DAMHINT), not just for the Captain Kirk factor.

I have a decent workflow established with the Treo 650 and Missing Sync on Mac OS X that works pretty well for me. Access, the company which owns Palm OS, released, a while back, a PalmOS 5 emulator for the Nokia n810 which runs all the basic Palm applications. I tried getting this working earlier but wasn’t successful.

Now that’s changed. One unexpected checkbox later and I have full HotSync between n810/Garnet and Missing Sync 5.1 on Mac OS X 10.4.11. Here’s how to do it:

First, in the Sharing Pane of System Preferences, make a new firewall exception like this, to allow in Network HotSync preferences:

Now, add a new handheld in Missing Sync, and change the Preferences, to include these:

And set the various standard conduits to overwrite data on handheld with desktop (once only).

Now, on the Garnet VM, put in the IP address of your Mac (dns didn’t work for me), and click the HotSync button. You should get a successful sync. Do it again to make sure it does nothing, quickly, indicating successful sync. Change some data on both ends and make sure it syncs. OK, you’ve got sync.

Now, go back and uncheck the allow-all-handhelds-to-network-sync box to protect your data. Make sure ‘Network’ is set in ‘Edit Handhelds’, and it’ll continue to work. I’m not sure what happens the first time, but there must be some handheld negotiation that’s required without permissions. Minor inconvenience, just needs to be documented.

All the iCal stuff should sync just fine, but MemoPad apparently doesn’t allow a way for sharing Memos between handhelds. So, to get this you also need to copy the Memo data file; copy:

~/Documents/Palm/Users/treo-profile/MemoPad.memopad

to:

~/Documents/Palm/Users/n810-profile/MemoPad.memopad

and sync again. You should have all your common Palm data on the n810 at this point.

Have fun. I ordered a new-in-box Motorola e815 radio from eBay for $90, which meets all my phone criteria. From here, I’d like to move to KDE PIM apps, and perhaps OpenSync. OpenSync to iSync is a non-starter, currently, but perhaps SyncML can bridge the gap.

del.icio.us:Missing Sync and the Garnet VM on Nokia n810 digg:Missing Sync and the Garnet VM on Nokia n810 reddit:Missing Sync and the Garnet VM on Nokia n810 spurl:Missing Sync and the Garnet VM on Nokia n810 wists:Missing Sync and the Garnet VM on Nokia n810 simpy:Missing Sync and the Garnet VM on Nokia n810 newsvine:Missing Sync and the Garnet VM on Nokia n810 blinklist:Missing Sync and the Garnet VM on Nokia n810 furl:Missing Sync and the Garnet VM on Nokia n810 fark:Missing Sync and the Garnet VM on Nokia n810 blogmarks:Missing Sync and the Garnet VM on Nokia n810 Y!:Missing Sync and the Garnet VM on Nokia n810 smarking:Missing Sync and the Garnet VM on Nokia n810 magnolia:Missing Sync and the Garnet VM on Nokia n810 segnalo:Missing Sync and the Garnet VM on Nokia n810

Collateral Damage in Comcast vs. Bittorrent

Posted by Bill McGonigle Fri, 08 Feb 2008 19:25:00 GMT

It’s already well known that Comcast interferes with bittorrent traffic but what is less known is that their measures also take out other legitimate applications, such as iChat AV.

The trouble with interfering with some traffic is that you then have to defend why you don’t interfere with other types of traffic, of a more pernicious nature. One would think Comcast would save more money by building a decent network and defending its common-carrier status.

del.icio.us:Collateral Damage in Comcast vs. Bittorrent digg:Collateral Damage in Comcast vs. Bittorrent reddit:Collateral Damage in Comcast vs. Bittorrent spurl:Collateral Damage in Comcast vs. Bittorrent wists:Collateral Damage in Comcast vs. Bittorrent simpy:Collateral Damage in Comcast vs. Bittorrent newsvine:Collateral Damage in Comcast vs. Bittorrent blinklist:Collateral Damage in Comcast vs. Bittorrent furl:Collateral Damage in Comcast vs. Bittorrent fark:Collateral Damage in Comcast vs. Bittorrent blogmarks:Collateral Damage in Comcast vs. Bittorrent Y!:Collateral Damage in Comcast vs. Bittorrent smarking:Collateral Damage in Comcast vs. Bittorrent magnolia:Collateral Damage in Comcast vs. Bittorrent segnalo:Collateral Damage in Comcast vs. Bittorrent

Vermont Confuses Me (specifically re: Fairpoint)

Posted by Bill McGonigle Mon, 31 Dec 2007 19:11:00 GMT

The first half of that title could apply to so many things, but regarding the Fairpoint proposal, Vermont’s PSB found this:

In rejecting the application, Vermont’s Public Service Board said in a statement that FairPoint failed to demonstrate that the company would be financially sound after completing the transaction… “Significantly, the Board noted that its review did not consider a recent settlement in Maine that had the effect of lowering the purchase price of the merger,” the Vermont Public Service Board said in its statement.

And the article adds this:

The companies settled objections from Maine regulators on December 13 and revised its transaction proposal that lowered the price by about $200 million. The new reworked proposal, has not yet been submitted to Vermont regulators.

So, the Vermont PSB knows about the altered terms of the deal but decided to issue a ruling based on what it knows is inaccurate data? Why would they do such a thing?

Possibilities:

  • They were under a deadline
  • They can only cast a reject/accept under such a deadline
  • There wasn’t a deadline but they wanted to make the news and/or color perceptions
  • They’re clueless.

So, the menu as presented is: incompetence, malice, or bureaucracy. What other possibilities are there (I’m asking, not being rhetorical)? What does Hanlon have to say about government?

[Thanks to Steve for the link]

del.icio.us:Vermont Confuses Me (specifically re: Fairpoint) digg:Vermont Confuses Me (specifically re: Fairpoint) reddit:Vermont Confuses Me (specifically re: Fairpoint) spurl:Vermont Confuses Me (specifically re: Fairpoint) wists:Vermont Confuses Me (specifically re: Fairpoint) simpy:Vermont Confuses Me (specifically re: Fairpoint) newsvine:Vermont Confuses Me (specifically re: Fairpoint) blinklist:Vermont Confuses Me (specifically re: Fairpoint) furl:Vermont Confuses Me (specifically re: Fairpoint) fark:Vermont Confuses Me (specifically re: Fairpoint) blogmarks:Vermont Confuses Me (specifically re: Fairpoint) Y!:Vermont Confuses Me (specifically re: Fairpoint) smarking:Vermont Confuses Me (specifically re: Fairpoint) magnolia:Vermont Confuses Me (specifically re: Fairpoint) segnalo:Vermont Confuses Me (specifically re: Fairpoint)

Fairpoint Deal Closer? 1

Posted by Bill McGonigle Tue, 18 Dec 2007 05:21:00 GMT

I got this in my e-mail over the weekend:

   
          Dear Verizon New England Inc. Customer,
          
          Pending approval of the Maine, Vermont & New Hampshire public utilities commissions, Verizon has agreed to transfer control of Verizon New England Inc. assets in Maine, Vermont and New Hampshire to FairPoint Communications. After the transfer, your new local service provider will be FairPoint Communications. We currently expect that this transfer will occur between January 31 and May 1, 2008.
          
          Beginning December 2007, Verizon will cease providing paper-free billing. It is Verizon’s current understanding that FairPoint Communications will reinstate paper-free billing at a future date.
          
          It has been a pleasure serving you.
          
          Sincerely,
          Verizon
          

Meanwhile, the Valley News seems to be printing the IBEW talking points without analysis and, while paying lip service to the necessity of high speed Internet for regional economic viability, it completely ignores the white elephant in the room which is Verizon’s neglect of New Hampshire’s telco infrastructure and unwillingness to make further investment. They do point out that Vermont has more regulation on the telcos there, but one has to wonder why a New-Hampshire based newspaper would conveniently leave out mention of its own state’s problem.

del.icio.us:Fairpoint Deal Closer? digg:Fairpoint Deal Closer? reddit:Fairpoint Deal Closer? spurl:Fairpoint Deal Closer? wists:Fairpoint Deal Closer? simpy:Fairpoint Deal Closer? newsvine:Fairpoint Deal Closer? blinklist:Fairpoint Deal Closer? furl:Fairpoint Deal Closer? fark:Fairpoint Deal Closer? blogmarks:Fairpoint Deal Closer? Y!:Fairpoint Deal Closer? smarking:Fairpoint Deal Closer? magnolia:Fairpoint Deal Closer? segnalo:Fairpoint Deal Closer?

Is Net Neutrality a Waiting Regulatory Disaster?

Posted by Bill McGonigle Mon, 29 Oct 2007 01:47:00 GMT

Ed Felten voices his concerns that asking for net neutrality is a regulatory disaster in the making. I left this response to his post:

There’s some level of reasonableness that can be achieved in any regulatory system, and, of course, room for abuse. That’s not unique to net neutrality, yet some regulation seems to help some markets. When I first wrote about Comcast’s conflict of interest in throttling heavy bandwidth users as video competition, I linked to an FCC ruling about DSL providers being forbidden to interfere with VOIP traffic. To me, there are some no-brainers that regulators can do like that without hosing the Internet forever. As far as folks here complaining about the bandwidth hogs - imagine if electricity usage were flat-rate. That’s what we have with bandwidth packages now. In the case of the natural monopoly, such as an ISP with xTTH, history has shown that metered usage with public oversight of rates is the model that is least-bad given the forces involved. All these issues of TCP resets, port filtering, SPAM zombies, bloated websites, torrent seeding, illegal p2p usage, etc. would work themselves out with a reasonable per-GB fee (20 cents, perhaps) and a minimal connection fee ($10 per mo, maybe). I suspect that those on the $15/mo package now would still pay a similar rate, and those on the $80/mo package would also still pay a similar rate. But there’d be none of this hassle of offering and ‘managing’ free, because ‘free’ doesn’t exist.

What I forgot to add is that this model also would drive the providers to increase speeds to the user, which the US is sorely lagging in. Obviously prices would have to decrease over time, compared with the overall economic environment.

One counterpoint would be all-you-can-talk phone plans. While these are technically ‘unlimited’, nobody actually talks all the time (even teenage girls need to go to school), as that takes labor, whereas a bittorrent client can run 24/7 with no real effort.

del.icio.us:Is Net Neutrality a Waiting Regulatory Disaster? digg:Is Net Neutrality a Waiting Regulatory Disaster? reddit:Is Net Neutrality a Waiting Regulatory Disaster? spurl:Is Net Neutrality a Waiting Regulatory Disaster? wists:Is Net Neutrality a Waiting Regulatory Disaster? simpy:Is Net Neutrality a Waiting Regulatory Disaster? newsvine:Is Net Neutrality a Waiting Regulatory Disaster? blinklist:Is Net Neutrality a Waiting Regulatory Disaster? furl:Is Net Neutrality a Waiting Regulatory Disaster? fark:Is Net Neutrality a Waiting Regulatory Disaster? blogmarks:Is Net Neutrality a Waiting Regulatory Disaster? Y!:Is Net Neutrality a Waiting Regulatory Disaster? smarking:Is Net Neutrality a Waiting Regulatory Disaster? magnolia:Is Net Neutrality a Waiting Regulatory Disaster? segnalo:Is Net Neutrality a Waiting Regulatory Disaster?

Dumb Heuristics (Facebook) 1

Posted by Bill McGonigle Sun, 28 Oct 2007 20:17:00 GMT

Using heuristics to look for behavior patterns is a good idea. Implementing dumb heuristics just ticks off your users.

Case in point: Facebook. I rarely have need to use it much, but recently I had the opportunity to make a couple groups, and sent some invites to folks to join the groups. Well, Facebook decides to tell me that I’m using it to spam people and they’ll deactivate my account if I continue. Fine, I sent an e-mail to the folks instead (aside: an ad-driven site telling its users to stop generating more page loads?!?!) which was actually much easier.

Then I went looking for a couple folks I’d lost touch with and sent them friend requests - and it still told me I was using the site for spam. All I can figure is that friend requests must internally generate messages and it tripped on the same shortbus algorithm.

Googling for this leads to kinds of people complaining about the same thing - some even are banned for life for sending ‘too many’ friend requests. Facebook CSR’s apparently have authority to do so. No wonder Microsoft bought these guys.

I also setup an Orkut account. That I just had to go look up how to spell Orkut is one of the many things that’s keeping Google from squishing Facebook.

del.icio.us:Dumb Heuristics (Facebook) digg:Dumb Heuristics (Facebook) reddit:Dumb Heuristics (Facebook) spurl:Dumb Heuristics (Facebook) wists:Dumb Heuristics (Facebook) simpy:Dumb Heuristics (Facebook) newsvine:Dumb Heuristics (Facebook) blinklist:Dumb Heuristics (Facebook) furl:Dumb Heuristics (Facebook) fark:Dumb Heuristics (Facebook) blogmarks:Dumb Heuristics (Facebook) Y!:Dumb Heuristics (Facebook) smarking:Dumb Heuristics (Facebook) magnolia:Dumb Heuristics (Facebook) segnalo:Dumb Heuristics (Facebook)

Palm Linux Phone Slips Another Year 3

Posted by Bill McGonigle Thu, 04 Oct 2007 18:44:00 GMT

Ouch. I was waiting until the end of the year to get a new phone since Palm had announced its linux-based phone would be out before Christmas. Today they announced they’ve slipped a year on that schedule. Bummer, they should have started on this back in ‘03 or ‘04 when Access (sp?) was trying to convince them to get off old the crumbly old PalmOS.

I can’t handle PalmOS for another year, it’s too creaky for what I want. Apple is committed to a closed platform. Nokia is pushing its phone as an open development platform and some feel passionately about it.

Feedback on the E90 welcome!

del.icio.us:Palm Linux Phone Slips Another Year digg:Palm Linux Phone Slips Another Year reddit:Palm Linux Phone Slips Another Year spurl:Palm Linux Phone Slips Another Year wists:Palm Linux Phone Slips Another Year simpy:Palm Linux Phone Slips Another Year newsvine:Palm Linux Phone Slips Another Year blinklist:Palm Linux Phone Slips Another Year furl:Palm Linux Phone Slips Another Year fark:Palm Linux Phone Slips Another Year blogmarks:Palm Linux Phone Slips Another Year Y!:Palm Linux Phone Slips Another Year smarking:Palm Linux Phone Slips Another Year magnolia:Palm Linux Phone Slips Another Year segnalo:Palm Linux Phone Slips Another Year

Older posts: 1 2 3 4