According to the latest Dec 2014 Reports in Colorado, they brought in $44 million for the time period 2014-01 to 2014-11.
Which although less than the planned 65 million (Nov brought in $7m so Dec could bring the total to $52 assuming monthly upward trend continues), is still a lot of revenue to fund schools, improve infrastructure and enforcement.

Though one still has to wonder how many cartels own pot dispensaries now :D

The negative attitude is what stops ideas from flourishing.

You have no complete files on your computer, just random bits and blocks. At some point, the compression techniques will improve to ensure that data can be reconstructed from these disparate pieces.

Bandwidth is transient, you use your bandwidth, and it's just a passive background task that's always going onwards, and as more units come online into this world, the less bandwidth each unit is required. The files and file systems are designed to handle losses, machines and boxes dying. The blocks are spread across multiple devices and are always kept redundant, so that the chances of data becoming lost approaches zero. If the primary source of your target block is gone, route to another storage loaction of that particular block.

It's is not about large companies supplying all the space (albeit, some will) it's about -every- device offering up space, cpu, hardward, and bandwidth to ensure that the flow of information can never be stopped, becuase it's ubiquitous.

It's for the the full mobility of the data everywhere.
Beyond a single tier provider like drop-box, but spread across every infrastructure storage.
And as advances in storgage increase, those would be deployed and handled the increased load.

The vision is to ensure that day-to-day life goes on, but everyone still needs a hard-drive for local offline storage, boot-up, caching, and the like.
Storage media will not be disappearing so long as ubiquitious internet access world-wide does not exist.
Thus, there will be a market, companies will still have infrastructure.
It's about having every device in the world suppling redundance storage space for multiple copies of data.

Terminoligy needs to be fixed.

All Codepoints are 4 bypes
All characters (defined as a single conceptual, and graphical display unit) range from 1 to 6 code-points. (so, 4-24bytes)

Sinhala:
0dc1 0dca 200d 0dbb 0dd3
ZHA VIRAMA ZWJ RA VOWEL-SIGN-II

Combine to form a single displayable character. (Sri) (kinda a fancy item; but different from without the ZWJ which would display two graphemes. (S', and RII)

And Lituanian:
"However, not all abstract characters are encoded as a single Unicode character, and some abstract characters may be represented in Unicode by a sequence of two or more characters. For example, a Latin small letter "i" with an ogonek, a dot above, and an acute accent, which is required in Lithuanian, is represented by the character sequence U+012F, U+0307, U+0301."

And there are many other cases where there is no single code-point to represent a single grapheme.
So for string truncation and line-splitting, (and anything dealing with arabic or indic scripts), you need to never crop in the middle of a codepoint-sequence that defined a single grapheme; or else the visual display is incorrect, or bakamoji (jibbrish).

Characters in Thai are rendered in display-oredr, and not logical order.
so, for example ( mina would be imna) and requires reordering for sorting.

Characters in many Indic languages are still all syllable based.
So, consonants and vowels are encoded separately, and fully interact as a logical graphical character.

Sinhala:
0dc1 0dca 200d 0dbb 0dd3
ZHA VIRAMA ZWJ RA VOWEL-SIGN-II

Combine to form a single displayable character. (Sri)

If you omit the Zero-Width-Joiner, then it displays as two characters, "Sa'" and "Ri."
So, the rendering and display are dependant on the entire grapheme, which is the normal unit of display and truncation.
Otherwise one will be cropping portions of a character on display; and rendering either jibbrish/bakamoji, or unrelated characters/syllables because.

Malay:
0d15 0d4d 0d38 0d3e
KA VIRAMA SA AA

One displayable character.
If you display code-point by code point, the grapheme displayed would changes 4 times.
KA
K'
KSA
KSAA

"However, not all abstract characters are encoded as a single Unicode character, and some abstract characters may be represented in Unicode by a sequence of two or more characters. For example, a Latin small letter "i" with an ogonek, a dot above, and an acute accent, which is required in Lithuanian, is represented by the character sequence U+012F, U+0307, U+0301."

THe arguments above are missing the point of this development.
It's fear that's the root of all evils, and prevention of advancement.
And the fear, however irrational/illogical on your personal scale is the only obstacle of advancement for all.

This isn't just about putting others' files on your computer, in broken encrypted pieces.
It isn't about the legal ramifications of having random unreadable bits on your hard-drive shard.
What this is, is the future of truly unlimited storage for everyone.
By creating a P2P storage solution, it's creating an "Internet" of storage space that everyone in the world can use.
It can render the local hard-drive solution solely a "cache" of files, but all the files, all the items you access will live on across the network.

If it's done correctly, It will allow one to lose your hard-drive completely, and have all your files instantly available.
Available from any computer interface anywherer in the world at any time.
And, depending on your decryption keys, or more specficially, your custom data-access identifier, you can have multiple file-stores, that are independant, and not related in any way. Or even co-mingling.

This has the prospect of leading the future into a truly data-everywhere situation.
The only item that needs to be resolved, is how to make this information publically available after some time.
History is being lost by the Encryption, and the loss of private journals, of private note-writings, and such.
And over time, it is those items that need to be protected and spread across the world to give insight into who you were, and into your thoughts, dreams, and different views on the events of your lifetime.

But, that can be handled after.
By doing this, we can pretty much guarantee that information can never be lost again, (which is different from ever being exposed.)
Which is a good thing.

I got a ticket doing 65 in the left-most lane; Reason: Car coming up behind me had to break.
It's an enforcable law in most states, that left lane is for active passing only.
More so in Utah, apparently.

They are using ISO Year for the Date header, for some reason. (the last 3 years wouldn't have been affected)
As Mon Dec 29, 2014, is ISO year 2015, Week 1, Day 1.

The Last-Modified header is showing the correct date and time.
The Date: header is not.

Last-Modified: Mon, 29 Dec 2014 00:59:30 GMT
Date: Mon, 29 Dec 2015 00:59:30 UTC

So, they're using the "G" rather than "Y" designator for displaying the date (if C based)
As all the other fields are correct, but they are using the ISO Year, rather than Calendar Year.
It's a subtle issue, but a rather silly one.

And clients, can probably see that either a) Mon Dec 29, 2015 doesn't exist (invaild date); or is b) Ignore monday, and 2015-12-09 is too far out of range for a new session token.

Full Time Employees only, not contractors.

These cards have been around for at least the last 4 years.
They get mailed out to your home address.
Employees only, not contractors.

The cards are for residential support (business is separate)
The cards give a gateway-blocked phone number that requests your card ID.
And then dumps you into tier 2; Usually into Res-Internet.

Needless to say, I'm not discounting that the lobbying arm of the company has added benefits, and have access to much more influential tools.
But the Make It Right cards still relies on existing Customer Support infrastructure.
There's no room in that particular system to allow for any real exceptions to give preferencial/better service.

If you go to high in the support chain, your problem won't get solved because of triaging, and work-load, and now issues are being managed by Scrum and Project Managers; and thus you'll wait longer.
If you go too low in the support chain, they may not have the experience or know how of how do figure out your issue.
Hence the cards get you to tier 2. You bypass the easy-fixes (assuming you tried that once all ready), and thus Tier 2 can help you better and start assessing your issue.

If you use the card, and didn't go through Tier 1 first; you'll basically get the same quality of service as the Tier 2 rep needs to basically do all the tier 1 work with you now. Only difference is that the Tier 2 rep has more experience and may have dealt with your particular issue before (which is also the case with Tier 1), and can bypass some questions due to insight.

Comcast is all about not making exceptions; it complicates business and handling.
Top Engineering ands VPs are treated the same way as Call Center reps; at least when it comes to all the details of initial pay, vacation, benefits, cards, tools, etc.
Now, the Skilled staff get additional items added on, but these are hacked in.
To minimize internal costs, means getting everything onto the same systems, no special cases, and nothing un-audited.

In our division, I have seen, usually near end of year when VPs and Execs send out an email asking "Does anyone have any extra Make It Right cards?" ... employees are usually more than happy to forfeit their cards to someone higher-ranked.

Tier one service is adequate for 70-80% of the people calling in.
of the above calls, the issue is resolved in one call for 95% of the time.
It's the deeper problems that require Engineering Insight, or learning customer state, or escalating to what's effectively Tier 5 support, to escalate to Engineers that cause issues. (tier 2 and above get logged; and increase in weight; usually driving bug-fixes and Engineering time)

The issue is more that no-one has figureud out a way to actually enable good Customer Support.
This is an ongoing problem and there is no good solution in the wild yet.

State 1: There are only a few visible symptoms, and end-customers usually have no idea what's going on.
State 2: There are literally hundreds of systems internally that affect the customer
State 3: For these 10-20 symptoms, there are 100,000s of possible problems.

Problem 1: Hiring hundreds of call centre workers for $10/hr, many of whom have little technical background.
Problem 2: Trying to teach these people everything about Engineering, IT, Infrastructure, Systems Architecture, Hardware, Interaction issues, Software Service Issues, Billing Systems, Switching Systems, etc.... and not quit becasue they now know more than most Engineers.
PRoblem 3: Because Problem 2 never happens, how does the CS agent search for the solution for your particular problem?
      You state symptom 1, 2, and 3.
      CS does a search, there are 80,000 possible problems.
      CS asks you a question to try to limit.
      You perform, and answer.
      CS enters that in, there are now 50,000 possible problems.
      [repeat until there's a reasonable number]

This leads to Problem 4: Users lie, or misinterpret. If they answer any question wrong, or perform an action incorrectly and give a unknowningly false response, that just filtered out their actual problem, and their problem will never get resolved on that call.

Things like "reboot your modem" are good filters, as that eliminates thousands of possible issues if it causes no change. If you don't actually do this (depending on the problem, they would actually send reset signals, and then require you to reboot; many techincally competent people don't reboot when asked, and thus ) a problem which normally would be fixed with a reboot, isn't, simply because the end-user assumed becasue they rebooted before and it did nothing.

Now, if anyone can design a system that allows unskilled end-users, to communicate their issues, and allow unskilled CS workers to search and find the solution, that would make millions.

For people who ask "train them more" As a fully trained CS degree, Engineering degree, and Engineer at Comcast, I would say that I have no insight as to how hundreds of systems interact or data-relays function. Within my realm, there are thosands of things that can go wrong, thousands that should never happen (yet somehow do, possibly becaues of CS reps changing state on an account without realising the impact). I can fix many issues. But bceause I have this breadth of technical skill, understanding, and knowledge -- would I work CustSupport? No.

If you want better Customer Support, figure out how to make it enticing for highly skilled, trained engineers to work phone jobs; and enough of them to support millions of customers.

The story is BS.
Every employee at Comcast gets 3 cards a year.
The idea is that if you see or hear someone who's having a problem, you can give them a card and they get a better experience.

The number on the card is a single use number. Thus, once used, it's tied to a specific account/issue, and can never be used again.
Second, it's only good for Residential services (Business services have separate support numbers and staff)
Third, it only bypasses Tier 1 customer support (newly hired users, who are still trying to figure out all the tools, and the problems,; once you're competent enough on enough systems, you can be promoted to Tier 2.)
Thus, if you want the same situation, call in to comcast, and immediate ask to speak to their supervision or a Tier 2 rep; or simply BS that your call was dropped while the issue was being escalated, etc.

Fourth, only a small number of employees actually use the cards. There was a drive to try to convince staff to jus give them out to anybody with a problem; even to friends of friends, or to strangers on the train talking about comcast. Just get them out there.

As the cards are basically tied into the Residential Support system, it doesn't help with Retentions, Service Cancellation, or other non Technical issues with your service. Not sure about billing.

I know when I was at Comcast, I didn't use my cards on friends. Someone complained on twitter about their comcast service, I gave them one of my cards. I gave one to a women I met on a flight; and the last I just lost.

Friends I would direct to call and tell them which keywords to use about their problem so that custrep can find the issue and fix it. (since they're basicaly just using a search engine to try to find out which of the 100,000s of issues your symtoms could match to; which leads to basically hundreds of questions to try to narrow it down, if they haven't experienced your particual problem before)