See I've been reading about this via DSL Reports and Ars Technica and between their posts and a post by Peter Nowak I do believe I have this figured out.
1) ISP's will not disclose data on congestion.
It's complicated but basically I believe congestion is created for political reasons. Not to support UBB mind you but to leverage the most money out of content delivery networks like LimeLight and Akamai. You'd have to do a lot of reading to see why I came to that conclusion but all my information stems from the discussion on NANOG around the Level(3)/Comcast dispute.
2) Marginal cost for ISP's is falling. Fixed costs are fixed.
High users of broadband don't really cost an ISP more money and we already know that. Netflix and (many) others claim a cost of less than 3cents/GB and falling to deliver traffic. So we know the ISP's are not proposing this to help cover the marginal cost of delivering a GB. On the other hand fixed costs are probably not decreasing as fast as ISP's would like.
3) ISP costs are tied to the price consumers pay.
I could look up a million economics theses supporting this or I could leave that as an exercise to the reader.
4) The more subscribers an ISP has then the less each pays (since almost all costs are fixed).
5) This encourages ISP's to pursue as many customers as possible at as high a density as possible.
Let's say it costs $250,000 to hook up a neighborhood. Each house costs another $250 to set up individually. Each GB costs 3cents (and falling!) to deliver. Hmmm... I wonder which cost the ISP is most concerned with recovering?
6) An ISP will deploy whatever methods it deems necessary to increase subscribers.
See this is arguably one of the great parts of capitalism. The ISP actually wants to spread its costs out as much as possible so it will continue lowering its prices (and reaching new customers!) until...
7) The bean-counters say it we go lower we might start losing money (or not making as much altogether).
Since the hardware costs cannot be lowered (I'm certain they've tried this approach as its the cheapest and least resistant) the ISP moves on to business strategies.
8) Someone says "Hey, what if we charged some users more and some less?"
The conversation might go something like this:
Executive A: "That's a great idea! How do we do it?"
Executive B: "It'll be like a toll road. You already pay taxes but the more you use the more you pay."
Conclusion: So the ISP in attempting to broaden its reach and connect the most households (subsidizing its costs and lowering its risk through a greater pool of customers) has developed what it describes as a "fair" billing system. There are other details like how an ISP wouldn't want wholesale customers competing with itself but this is basically the situation and the motivations as far as I can tell. Whether this is fair or an appropriate solution to the ISP's incessant search for improved efficiency is ultimately up to you.
I am a student studying computer science (programming) and networking. These are my notes.
Thursday, February 24, 2011
Friday, February 18, 2011
Either it is or it is not.
Two possible reasons for running across the "error: Error parsing XML: unbound prefix" issue on building your Android app.
1) You have not properly specified an XML namespace for Android to use. Fixing this is easy, just add
"
xmlns:android="http://schemas.android.com/apk/res/android"
"
immediately after the opening of the first LinearLayout tag at the top of your document. This will allow the interpreter to parse the rest of your document and recognize the android: properties.
2) You have an error in your XML that is very likely a spelling mistake. When I was searching for this I was confused because it repeatedly specified the opening of the XML tag which was on a seperate line from the actual misspelling. I had to go down three lines to where I had specified andriod:id rather than android:id.
Hopefully this helps someone! :)
1) You have not properly specified an XML namespace for Android to use. Fixing this is easy, just add
"
xmlns:android="http://schemas.android.com/apk/res/android"
"
immediately after the opening of the first LinearLayout tag at the top of your document. This will allow the interpreter to parse the rest of your document and recognize the android: properties.
2) You have an error in your XML that is very likely a spelling mistake. When I was searching for this I was confused because it repeatedly specified the opening of the XML tag which was on a seperate line from the actual misspelling. I had to go down three lines to where I had specified andriod:id rather than android:id.
Hopefully this helps someone! :)
Thursday, December 23, 2010
At least someone reported on the real Wikileaks story
http://www.theregister.co.uk/2010/12/23/wikileaks_and_data_theft/
I read somewhere that it was likely the communication channels opened after 9/11 that enabled this security atrocity. Kudos to "the media" though for overlooking this blatantly obvious and genuinely interesting story of security officers unconcerned with the well-being of either their own soldiers or Iraqi civilians (see this chat transcript for more).
The amazing thing is this lasted for months! Wired published that article on June 10, 2010 and El Reg (I hope they don't mind me calling them that) has only JUST reported on it. I don't know that I would call this a conspiracy but I have a hard time believing that this was just conveniently "missed."
Although perhaps I give them too much credit. After all, this wasn't even reported on in such a security conscious manner until 6+ months later when someone gave a report sounding the China/cyberwarfare alarm.
I read somewhere that it was likely the communication channels opened after 9/11 that enabled this security atrocity. Kudos to "the media" though for overlooking this blatantly obvious and genuinely interesting story of security officers unconcerned with the well-being of either their own soldiers or Iraqi civilians (see this chat transcript for more).
The amazing thing is this lasted for months! Wired published that article on June 10, 2010 and El Reg (I hope they don't mind me calling them that) has only JUST reported on it. I don't know that I would call this a conspiracy but I have a hard time believing that this was just conveniently "missed."
Although perhaps I give them too much credit. After all, this wasn't even reported on in such a security conscious manner until 6+ months later when someone gave a report sounding the China/cyberwarfare alarm.
Wednesday, December 22, 2010
Tuesday, December 21, 2010
This is why
This is why I hate Microsoft's updating system.
http://msmvps.com/blogs/bradley/archive/2010/12/20/if-at-first-you-don-t-succeed-with-a-net-update.aspx
http://msmvps.com/blogs/bradley/archive/2010/12/20/if-at-first-you-don-t-succeed-with-a-net-update.aspx
Tuesday, December 14, 2010
Security, security, SECURITY!!!!!
The past couple of days I have received three very important emails.
The first email was a message from Gawker Media stating that my account may have been compromised and somewhat downplayed the risk. Ironically, the risk it downplayed was the use of the same password across many/all sites (a very common practice) which was exactly the practice that led to penetration of the Gawker site and ultimately the release of all 1.3 million account details (including mine! :( ) including passwords.
The second was an email from LinkedIn stating that my account may have been compromised. Sound familiar? Well, I figured that someone had decrypted my password and was attempting to use it at another site (it must have failed I figured because I sometimes used slight variations). So I began my trek to change my password on every site. It's now a 15 character GRC-generated password consisting of ASCII characters (so '!@#$%^&*(), etc. are all possible values).
The third email was also from LinkedIn clarifying the first LinkedIn email. It seems they downloaded and scanned the database of Gawker accounts and checked the email against their own user database. When they found a match, they sent out an email to every email account listed as associated with that user.
As much faith in my fellow programmers the Gawker hack destroyed, LinkedIn has singlehandedly restored it.
Simply amazing.
The first email was a message from Gawker Media stating that my account may have been compromised and somewhat downplayed the risk. Ironically, the risk it downplayed was the use of the same password across many/all sites (a very common practice) which was exactly the practice that led to penetration of the Gawker site and ultimately the release of all 1.3 million account details (including mine! :( ) including passwords.
The second was an email from LinkedIn stating that my account may have been compromised. Sound familiar? Well, I figured that someone had decrypted my password and was attempting to use it at another site (it must have failed I figured because I sometimes used slight variations). So I began my trek to change my password on every site. It's now a 15 character GRC-generated password consisting of ASCII characters (so '!@#$%^&*(), etc. are all possible values).
The third email was also from LinkedIn clarifying the first LinkedIn email. It seems they downloaded and scanned the database of Gawker accounts and checked the email against their own user database. When they found a match, they sent out an email to every email account listed as associated with that user.
As much faith in my fellow programmers the Gawker hack destroyed, LinkedIn has singlehandedly restored it.
Simply amazing.
Saturday, December 4, 2010
Que funny!
Saw this while I was trying to find a way to lock down Mozilla for a public terminal. I made this in response.
Subscribe to:
Posts (Atom)



