Real time is not just real time as it is happening right now. Real time is also real time as it happened in real time two years ago. But Twitter thinks only your 3,000 or so latest tweets are relevant. It does not destroy the old tweets, but it disallows access to them, which in my book is akin to destroying them.
My single biggest frustration with Twitter has been that I can not search through all of my own tweets. If I could, Twitter would be my Dropbox. But no, Twitter would not open up its API.
Twitter opening up its API would mean Google being able to access all tweets without paying Twitter. Bad deal for Twitter? No. Like Jeff Jarvis says, do what you do best, link to the rest. Twitter does not do search right, if at all. My tweets belong to me, not to Twitter. At the least I should have access to them.
All tweets ever tweeted becoming fair game to Google Search would enhance the piece of real estate called the tweet tremendously. It is in Twitter's interests to open up. Lift the iron curtain. Mr. Dorsey, tear down this wall.
Image via CrunchBaseI have long been a proponent of adding a social element to FoodSpotting, (FoodSpotting API) and Nosh seems to have that element, but where Nosh does not seem to "get" it is that with Nosh the dish does not seem to be the starting point. That is a big minus. (FoodSpotting's Dish As Starting Point)
The social graph I have had in mind for FoodSpotting has been more the Color kind than the Facebook kind. FoodSpotting could be an amazing force for peace. And I don't feel like I am exaggerating. I do mean to talk geopolitics.
But if I were FoodSpotting, this would be a wake up call to me. The brain behind Nosh was the same brain behind what today is Google Voice. The guy sure has the tech chops. And he is trying to fork into the FoodSpotting space from the Instagram paradigm. But he has already exhibited some major vision level blind spots. The name Firespotter borrows half the body from the name FoodSpotting. Thief!
ReadWriteWeb: Like WordPress for Mobile App Creation: Cabana is a Service to Watch: Is it possible for a visual drag-and-drop mobile app creation tool to deliver a sophisticated product? ..... Drag and drop addition of features like a camera, check-ins on services like Gowalla or Foursquare, integration of the Instagram photo API and many more things are possible. ..... There is a clear demand for this kind of light app publishing technology
This is the future people. Until the mobile web attains the same levels as the big screen web, we will need apps. And just like every offline business needs its own specific website, the mobile phone app has become the equivalent of the website on the big screen web. And the only way to meet that demand would be through services like this that promise to take the wizardry out of mobile app creation. Anyone who can drag and drop should be able to build an app.
Technology Review: The Next Stage Of Online Video Evolution: CNN and The Onion, for instance, have used it to build out their video libraries, in part because it offers new design options. "The technology is far more expressive" ..... the new Web standard lacks some features of Flash ..... Flash is much better at letting developers use digital rights managementsoftware .... a full-screen mode--the absence of which is a glaring difference between HTML5 and Flash ..... not yet fully fleshed out in HTML5 is closed captioning and subtitles via synchronized time pegs
Internet access speed is a big enough bottleneck. But the evolution to HTML 5 promises to usher in a new era for online video. Hopefully the speeds will go up too, but those are two different domains. HTML 5 is to do with programming and architecture.
But HTML 5 is not just about video, although that is where much of the noise has been. It is being said the non video aspects are actually more exciting.
And it's kinda early. HTML 5 - whatever it is - is not quite here yet.
But Adobe has Flash and Microsoft has Silverlight. It is not obvious if they are competing or parallel technologies. Smart minds have made counter claims.
Technology Review: How HTML5 Will Shake Up The Web: lesser-known features could ultimately have a much bigger impact on how users experience the Web..... ts network communications and browser storage features--could make pages load faster ...... Web Sockets provide a website with an application programming interface (API) that opens an ongoing connection between a page and a server, so that information can pass between them in real-time. ... The effect of Web Sockets is something like moving from having a conversation via e-mail to having it via instant message ..... A feature called Web Storage lets Web applications store more data inside the browser, retrieve it more intelligently .... HTML5 allows developers to embed windows of animation onto a page .... improvements in the way browsers handle forms will reduce the amount of javascript needed and speed up page loading
Technology Review: Google Offers Cloud-Based Learning Engine: the smartest Web services around rely on machine learning--algorithms that enable software to learn how to respond with a degree of intelligence to new information or events...... Google-hosted algorithms could be trained to sort e-mails into categories for "complaints" and "praise" using a dataset that provides many examples of both kinds .... extracting emergency information from Twitter ...... machine-learning black box--data goes in one end, and predictions come out the other ...... "This API could be a way to get a capability cheaply that would cost a huge amount through a traditional route." ... Prediction API .... has the potential to be a leveler between established companies and smaller startups
We went from big, ugly computers - mainframes - to PCs. PCs were simpler. And over time they became pretty powerful. And then the cloud emerged. The internet itself was the cloud. So I agree with Larry Ellison when he claims he has always done the cloud thing.
We went from servers to data farms. And these data farms run by big companies like Google and Facebook are huge, big enough that the electricity costs are a major headache even for these rich companies.
When Larry bought Sun, I threw a challenge in his direction. Can you build data centers that are the size of servers? Or at least small data centers? That might be nano territory. But I figured what the heck? There is never too much drama in Larry's life. What is one more challenge?
One common denominator with these disruptive technologies is they have been democratizing forces. It has always been about making it possible for more and more people, more and more businesses. We basically want everybody to be able to go online.
Google's Prediction API is a step in that same direction, and I am glad. Suddenly even small businesses will be able to make sense of large quantities of data they might end up collecting.
Chris Dixon: Web Services Should Be Both Federated And Extensible: The next step in this evolution is to create web services that are both federated (APIs) and extensible (Apps)..... The combination of Facebook’s data (social graph and check-ins) and SimpleGeo data/algorithms would create much more advanced feature possibilities than either service acting alone...... a “data threesome” ..... Allowing websites to be federated and extensible will open up a whole new wave of innovation
Two memes have been making the rounds: the web is dead, women in tech.
Chris Dixon, in this post, is referring to mash ups, high level mash ups. He is talking of "data threesomes" and how that would lead to "a new wave of innovation."
Some people have commented saying it is already being done. If it is, it is not mainstream yet.
People have been building APIs upon APIs. There is much data sharing going on, but not entirely enough.
What really matters is the end product, that final interface that the end user interacts with. A simple interface sitting on top of rich data interactions is what you want to shoot for.
Google is not a company TechCrunch talks about a whole lot. TechCrunch stays on the lookout for that hot new startup. So I was surprised to see so many Google related posts on TechCrunch today.
I protested. I did my part. If the protests are not going to work, and the ban on me at the Google Wave API Google Group is not going to be lifted, I move on. I guess I will have to find out other ways to spot trends in Google Wave development. I am sure there will be several good blog options. We are at the early stages of seeing blogs dedicated completely to Google Wave. Maybe some of those bloggers will do the reading for me in those Google Groups.
A great way to follow an open source project is in the very open perhaps.
Einstein was attacked by some with anti-Jewish leanings. When a pamphlet was published entitled 100 Authors Against Einstein, Einstein retorted "If I were wrong, one would be enough."
The name is clear enough: Google Wave API. It is a group about Google Wave API. So if
you are going to post messages about viagra ads and Nigerian dictators who need help with money transfer, then you don't belong in the group. So I am not trying to argue it is my human right to belong to the group.
The initial protest was that it was a group for hard core code talk. I respect the sentiment. But there were numerous threads about spam, t-shirts and invitations to Wave. Noone seemed to have been bothered, bothered enough to protest and ban people.
The third thing I established was that code and community/culture are both on par, they are both important. You can not expect to have strictly technical conversations and still exp
ect to create waves with Google Wave. And then I offered to stick my vision, culture and community talk to one out of the 300 plus threads in the group.
Then they said, it is not what you are saying, it is how you are saying it. Why do you post links to your blog posts in this group? People who don't "get" links and blogs should voluntarily walk away from a group about Google Wave development.
The slam dunk was I said but my primary interest is in code talk. That is why I joined the group in the first place. I wish to follow all the code related conversations so I can spot trends in Wave development over the coming months as we prepare to unleash Wave upon the world.
I just noticed I have been banned from the Google Group called Google Wave API. The decision sounds Stalinist to me. I would have understood if this was a group for hard core coders who only talked about code. But there were numerous threads on all sorts of non code topics there.
My "crime" was that I pushed forth the opinion that code is important, but so is the coder community and that community's culture. Code is important, but without vision the people shall perish. That I was interested in vision, and community, and I was very interested in code, because I wanted to follow the conversations in the group to be able to spot the trends as they emerge in the Wave developer community. But some genius went ahead and banned me from the group. I don't know where I would go to appeal the decision.
This is so ridiculous. The guy who banned me from the group is like the five blind men, he thinks he is feeling the trunk: Five Blind Men And Google Wave.
What makes this ban extra ridiculous is if you are not a member of the group, you can still read its content, but I can't.
Brain. Or maybe you should just go ahead and ban me since looks like you deleted my past three or four posts.
I started this thread that in its title very clearly says this particular thread is about the community aspects, not the code aspects. So those developers who are only interested in the code aspects will not even bother clicking on this thread. I thought t-h-a-t was fair enough.
I have been in the process of establishing the fact that code and community are both important. That has been true for Google Corporate, and the open source communities. That is going to be true for the Google Wave Developer community as well. Google Corporate is 20,000 strong, about 50 out of 20,000 devoted to Wave. The Wave developer community on its own is going to be larger than 20,000. And you are going to tell me talking about code is enough?
I don't know where you stand in the Google Wave Corporate hierarchy, but the official Google Wave Developer Blog has linked to my blog posts on the importance of a culture for the developer community at the bottom of every single of their posts as of now. Go take a look. http://googlewavedev.blogspot.com
And my original Google Corporate Culture blog post that you so derided has been a hit on Twitter, and is at the bottom of all the latest 30 plus of the posts at the official Google Blog itself. http://googleblog.blogspot.com
Now can we please repost my posts at this thread that you went ahead and deleted?
And how primitive is it to suggest you can post words but not links to your blog posts? Links are what the internet is all about. How, Sir, did you miss that part? Links are the center of gravity in Google's PageRank concept. Links are what make Twitter Twitter, it is not the 140 character limit.
I have come to this Google Group with a very clear goal, which is to share in the excitement of Google Wave - the next big thing in web technology - and to help shape its developer community, especially its culture aspects, and to try and spot and popularize trends related to Wave, especially as they might sprout out from the developer community.
Your basic respect for free speech would be much appreciated.
I just went around and looked at the subject titles of many of the other threads at this forum. My thread is more on-topic than most. Most of the threads so far seem to be about wanting in on a Google Wave account. That's code talk? Come on, man.
Lessons on Community Management from the Open Source World, Angela ...Fostering the Drupal community is actually more important than managing the code base. ........ the success of healthy open source projects defies all logic. Scores of individuals from all over the world, all of whom have different skill levels, use cases, experience, native languages, and time zones, collaborate together in order to help make a project succeed. ........... How is it that all of this chaos comes together and creates something wonderful and useful? ........ a diverse, passionate, and vibrant global community. ......... Create a Great Community and Great Code Will Follow .......... the project's developers, but also to those who report bugs, review fixes, answer support requests, design interfaces, provide translations, help with marketing and evangelism, and write and edit documentation. ............. Many key individuals who are driving forces within open source projects got their start by fixing typos in documentation or answering other users' support questions. ......... A culture that values a well-written tutorial as much as a well-written application programming interface (API) is much more likely to attract and retain newcomers than a culture that values seasoned developers, or the marketing team, at the expense of everyone else. ............... the difficulty in managing a community of strongly independent individuals, each with their own motivations. .......... contributing can directly or indirectly lead to paid work which acts as another long-term retention tool. ............ people won't get the peer reviews they require to accomplish their goals by being arrogant, insulting, and demeaning towards others. ............ The sooner a frustrated user realizes that there is only a collective “we" where each contributes whatever they can to make the project better, the sooner the transformation into contributor can take place. Users then learn to channel their frustration into an effective force for change. ............ The same peer review process that lends itself to building a strong community and great software can be terrifying to newcomers. .......... The natural problem-solving methodology for perfectionists tends to be withdrawal from the community and working quietly in isolation until they believe they've achieved something that is immune to criticism. This brings with it a whole host of problems ........................ their work can get permanently trapped in "analysis paralysis" and never see the light of day. ........... Working in isolation eliminates transparency ........... In a worst-case scenario, the larger community has already developed a solution to a problem in parallel by the time the perfectionist is finished, leading the perfectionist to extreme frustration, particularly if coupled with a deep attachment to their own solution. ........................... vital to establish a strong culture of “release early, release often” ............ a lack of attachment to any one solution so that the best possible solution is found. ...... The key difference that separates healthy perfectionist contributors from unhealthy ones is the participation in a collaborative problem-solving process, rather than an introverted one. ................ Focus on the people, not the product. A team that enjoys working with one another will naturally be more productive. Take a "mental health" check of the people on your team. Is there animosity brewing between two or more groups that could be solved by them working more closely together? Is decision-making in the hands of a single individual, hampering the feeling of ownership by other, capable people? Resolving these kinds of issues should take precedence over anything else. ............. fight red tape in all of its forms. Remember that a frustrated person is often best poised to lead revolutionizing changes for the better as they have the motivation. Get the road blocks out of their way and empower them to get to work. ........... Put processes in place that help prevent perfectionists from getting trapped in their own heads, and get them working with others instead."
I have been part of a conversation at the Google Wave API Google Group where I have been trying to suggest community is as important as code, and so there has to be talk of the culture of the Wave developer community. Many have disagreed saying code is all that matters. Some have said community also matters but maybe you don't know enough to be talking community either. I don't know what I don't know. But vision and group dynamics are specialties all their own.
The last suggestion I made was, let's have 100 threads on purely technical issues, and I hope to develop my technical chops along the way, but let's have one thread where we talk about fluffy issues like vision and community. Code and community do belong at the same forum.
Once it is established that both code and community are important, we can then move on to studying the lessons of the open source communities past so as to distill from their best practices, because the Wave developer community, culturally speaking, has more in common with the open source communities than any of the corporate ones.
Building a community of developers is not just about code.
I am not trying to lead or follow. I am just trying to be part of the conversation, to learn from the conversation, to contribute to the conversation.
The Google Wave team, or at least those who look after the official Google Wave Developer Blog and The Official Google Blog have been nice to me, they have been nice to my blog. They have given my blog posts on Google Wave special status. I am honored. But more than honored, I am excited. I am so excited I feel like I could be putting out blog posts on Google Wave daily. Right before that Google got me excited with Android, with the donut talk. And now I am thinking, between Google Wave and Android, Google might just have taken over this blog for the rest of this year, because I can't imagine bigger topics in tech for the rest of this year than Google Wave and Android. Bring it on.
Now I just need one of the Googlers on either the Wave or the Android teams to walk over to the Google Ventures people and put in word for me that they need to go ahead and buy 2% of my company for 100K: Google's Newest Venture: Google Ventures.
Reader Response
One reader wrote in one of my comments sections saying I came to your blog thinking you will throw some light on Google Wave's architecture, but I did not find anything. I guess so far I have been more interested in the implications of the Google Wave architecture rather than the architecture itself. But soon enough I will get around to the actual architecture, the technology of it. But for now let me have one more go at the implications. What will it mean to have Google Wave?
Organizations Will Go Topsy Turvy
You will not be able to prevent your workers, your team members from using Google Wave, it is not like you will be able to say, sorry, it's not in the budget, maybe next year. There will be bigger lines - virtually speaking - forming for Google Wave than ever did for the iPhone or the iPod. Just wait until we get nearer to the release date.
The product will be free. The product will be mind-blowing. Organizations that resist will be blown out of the water.
But email did not kill organizations. Wave will not kill organizations, quite the opposite. Wave will breathe new life into organizations. Collaboration will take a whole new meaning, a meaning that collaboration never had before. And that is a good thing.
If Google just delivered in a few months that it promised in this video, I would be happy enough. For one, this application will take blogging to a whole new level. And I have been excited enough about Zemanta and Disqus.
But you also wonder, where could this all lead to? What new applications, gadgets, innovations might we see? I have a feeling it will be like Gmail and Gmail Labs. They keep coming up with new, nifty features that you choose to add on.
People will be creating and consuming waves in quantity. New wave forms will become possible.
Google Wave will not be launched for a few more months. I think that might be enough time to get some developers to surprise us in major ways. I can't wait to see.
The mark of a successful web service or app is that (1) it creates buzz, and (2) developers start developing around it. Think of all the Facebook, Twitter, and iPhone applications. Wave will beat them all, I think.
Google Wave Federation Architecture (Google Wave Federation ... the Google Wave Federation Protocol for federating waves between wave providers on the Internet. ........ various elements of Google Wave technology - data model, operational transformation, and client-server protocol ...... The wave federation protocol enables everyone to become a wave provider and share waves with others. ....... A robot is an automated participant on a wave (see the robots API). Examples are translation robots and chess game robots. ........ A gateway translates between waves and other communication and sharing protocols such as email and IM. ....... Different wavelets of a wave can have different lists of participants. ......... there is a designated wave provider that has the definitive copy of that wavelet. We say that this particular provider is hosting that wavelet. ......... different users have different wave views for a given wave. ...... the user's read/unread state for the wave, is stored in a user-data wavelet ....... A wave is identified by a globally unique wave id, which is a pair of a domain name and an id string. ......... Like a wave id, a wavelet id is a pair of a domain name and an id string. ......... Wavelets in the same wave can be hosted by different wave providers. ........ a federation gateway and a federation proxy. ........... "local wavelet" and "remote wavelet" Salesforce rides on Google wave : News : Software - ZDNet Asia Google Wave Architecture Google's move to introduce a Wave of synchronicity | Web Apps News ...Wave is an architecture, and not really a very new one. It's an old solution to a very old problem: that of synchronicity in distributed applications. ........ the speed and connectivity have not yet existed to deploy a transformational database matrix on a massive scale. But "Google" has come to mean massive scale, and now it's giving the concept a try. ........ One way that it works is by upsetting the typical hierarchy of database architecture ....... Whereas typically you might think of a database as a thing in the core to which changes happen, OT reverses the concept by generating a kind of change model that bears a striking resemblance to a Feynman state-change diagram in quantum physics. Here, the database or "document" that ends up being the beneficiary of change, is used to represent the change itself, or what the architecture calls a wavelet. ........ a better Google Chat than Google Chat .... The architecture itself is the major undertaking here. .... Wave isn't really an app yet, and isn't a fully-fleshed out architecture yet, and doesn't have a complete platform yet Google Wave - a developer's eye view In the 80s, we called it Lotus Notes. As of recent, we called it MicrosoftSharepoint. Today, I guess, it's Google Wave. ....... Google shoving its fist into the gooey, caramel-center of the enterprise collaboration market is a good thing, because when it comes to APIs, Google sells to the developer, not the managers. ........ think of a "wave" as a collaboratively edited document. ....... you don't have to be running a particular program or be on a particular website to interface with these documents. ........ Embedding a wave into a web page is as easy as a couple of lines of Javascript code and then any stylizing CSS you want to do around it. ...... "Federation....that was hard." ..... Wave servers talk to each other using an extension to XMPP, which is the same protocol that powers Jabber and Google Talk. Google Wave And Teaching And Learning Where email is all about stored messages, and the web about linked resources, Wave is about collaborative events. ........ like email and the web, and unlike most social network tools - anyone can play ......... A lot of educational technology centres around activity and resource management. ......... the activity type that’s most interesting is likely to be group collaboration, and the most interesting resources are those that can be constructed, annotated or modified collaboratively. ........ the idea of real time document collaboration as the fundamental organising concept ....... Google is treating this as a rising platform/wave that will float all boats. Much as they do with the general web. ....... Wave developer API guide. This is easily the clearest introduction to Wave’s concepts- short and not especially technical
Looking Forward to the Vacation Entrepreneurship in India Elections 2009: What Next for the BJP An Entrepreneur's Early Days There is a wafer-thin margin which separates the two worlds .... one with its clear, laid-out path up the corporate ladder, and another with its glorious uncertainties. ........ After two years of working, I finally called it quits and embarked on life as an entrepreneur. ....... It was a dream that would have to wait a decade before I got an opportunity to try to make it happen. ....... I am now in my third innings as an entrepreneur. The first lasted two-and-a-half years and ended in failure. The second lasted five years and ended in my business being sold. The third began two years ago. How it will end I do not know. ....... Financial gain should not be a driving factor or even a consideration in becoming an entrepreneur. ....... All other doors need to be closed, so one cannot run away mid-way ........ Entrepreneurship is not about parallel processing activities, it is about bringing complete focus to something the entrepreneur deeply believes in, even though as time goes on, these beliefs may be altered. ..... fewer than one in thousand find financial success. ...... However good the entrepreneur is in his field, in the area of running his own business, he is a baby. ...... the self-doubt and loneliness of the early days ........ Being a baby, I did a lot of things wrong. There was a lot of stumbling and falling. At that time, it was hard to see what was the good that would come out of all this. But, that is how we learn. The second stint at being an entrepreneur was where all this learning came in useful. ...... a world in which the entrepreneur now seeks to make connections, reach out and touch others. Everything around may be the same, but yet things look and feel quite different. ....... The entrepreneur now needs to start putting a team together, along with raising capital (either from family and friends, or from angels and venture capitalists). Each day is now full of life. ........ The new business has to be built day by day, customer by customer, rupee by rupee. ........ I still remember the day we launched IndiaWorld, the first two customers we got for our home pages, and the first large order we got for a website (I was on a bus back from Nasik on a suspenseful trip in the pre-cellphone era). Even today, the many meetings I had in the early days to try and get content partnerships are still quite fresh. Much of the period since then is a blur, but those few memories are forever etched away. ......... Just like the teenager who feels he can do no wrong, so does the entrepreneur. This is, therefore, also the most dangerous period in the life of the entrepreneur. .......... One has gone through the early, tough days, and there is a latent volcano waiting to explode on the scene. ....... there is no Undo or Edit button. ....... recruiting the second-tier management team, the first markets to tap into, the partners to ally with, the activities to do. This is the time when temptation of doing everything is abundant. This is when judicious decisions need to be made ........ deciding on the few things that need paramount attention ......... there is no way that everything can be done well at the same time. ........ This is as exciting a chess game as any that has been played. Rethinking Education A Second Train Journey Meeting a Friend after 21 Years Blog Past: India.com 2.0 How much is your social network worth? Digg for online ads USA.gov adds tools to open up information sources the Government News Aggregator, which allows citizens to receive consolidated news and information from across the federal government, delivered via RSS feeds ...... the public no longer has to scour a vast array of government websites to follow news that’s relevant to them ...... a USA.gov Word Cloud that is a visual representation of the top 75 most popular search terms on USA.gov China blocks popular websites in lead up to Tiananmen anniversary Google set to move into e-book space, take on Amazon Stop selling scarcity The new Detroit isn’t Detroit Jay Rogers, founder of Local Motors. He is creating the platform and API for new cars that are designed collaboratively by communities and built in microfactories across the country by staffs of only 41 using almost entirely off-the-shelf parts. He says he will be profitable selling only 500 cars. He plans to build 3-5,000 of each model and he’s months away from delivering his first......... Local Motors does what it does best and links to the rest ....... Rogers said the most important hire a company can make today is a CCO, chief community officer. ...... bimodal intelligence ....... The mass market is dead, replaced by the mass of niches. ...... Middlemen are doomed. Local Motors has no dealers. The factory is the showroom. The customers are the salesmen. Government by the people No gadget savior in news, neither the device nor the form matters nearly as much as the information and its timing. This requires that publishers unleash their news on every device possible. But no single gadget will be their saviour. Google Wave and news Just as I was thinking they were behind the curve on the live web - and argued they should buy Twitter - Google attacked it from the left flank with Wave. ...... Because it can feed blog and web pages and Twitter, I see a new way to create content, collaborative and live. I see a new way to make news. ..... Here, I speculated about the topic becoming the new atomic unit of news ...... Wave isn’t just the email we’d invent if email were invented today, as was Google’s goal. Wave is what news can be if we invent it today, as we must. ..... Replace news story with “disease you suffer from” and reporter with primary care doc and editor with specialist and photos with lab results, etc, and you can see its potential. The embeddable newspaper newspapers need to think distributed, that they need to go to where the readers are rather than expecting them to be attracted to news sites like magnets ...... make itself embeddable without having to go through Google’s funnel. ..... Becoming embeddable is a way for a site to act like Google and go with the flow of the internet, to be distributed by its readers, to take its content and branding and advertising out into the web. The Google – Youtube – Conundrum
![Reblog this post [with Zemanta]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_touJrv9opHyBgV8jpPiZKzRJWuGJ4ox5D9jdXo4IeItbPCga8lzliKmXps61monvQGC3Pw14BPmdR9PaBnvT44qhQpdPGrb2rvuAnyhcHli83Zu7Xp17JJlEbNt3dIQBSTAZUuqIwuSioyrIfDprJR=s0-d)
![Reblog this post [with Zemanta]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_tUaVm1KJpw679DvLWYcTwgxW8MMAO8pNcMKdYCNAIg3jIS65uG7lmiXYrUkeRpnvRgbTFH6m5KouDGx_DmJHYYm3hJ_B1VRL4T5sdR9BDau8LB6mXd6gx5Xtm3UENZv_itUOvQkeaBde7xl2rBMOA=s0-d)
![Reblog this post [with Zemanta]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_tziprMC2Znqk5QuO7ZhkI-fLjYXh3noGpRI1Umr7Nro-9c3zGXNg0z-Cnr8fWwXvmQWTJio7jkaqpBHke1kA49dRjp2_AHIuk6tlCl8B8xyEm3zeVXcTsBI8sqI1KglvRP35iN2T8KC3MIFavwcwM=s0-d)
![Reblog this post [with Zemanta]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_vSnl0f6-pAjKD8fQBig2n94YQo1Y7nO1TmgtNaj4IdyWk9j-h-ys-TpJ1bWMvezpHNtezlyTTR8ElUA3mCp3DCiedMufX70wJrzWqQUg0ZXfHJ1FrW-6F0Ri1wDohAXQQmePTViFiyIfG38t4RCyYT=s0-d)
![Reblog this post [with Zemanta]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_u3fdVnY07DGRDwu3_nD8AQPo0E_vDs4twS3WXbZ2-SYHPN9PFr3ujy7Kcy6ZpExKu2llqUy_adZ6CfawGb10ikQtDq36WaE4w5YxN81eifQ8Oe9Vyo1dR8CS9_ERHgpzKFzUbeFAm7eR00qeO3ru0=s0-d)
![Reblog this post [with Zemanta]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_sj2o-hQ1KpnHHlyo6V7ZjKy3UlBteww4drZ-IAlNmP31FACDT_Vu94qsL1LrX8JwuKf2zgq-8rrNds3fweH1UWDEaM9tUFT8KfV1jFIyQiXzTs5QXpNZ07Z-E5CJyC7nFkcpW-pffuT2u5jWQOlxl0=s0-d)
![Reblog this post [with Zemanta]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_ttkXHPOPpQwtlASGfThDvuoYNwFzlB5c3QrjmYOKod6UVB3IT3oWyzzaOFPuknLs5w32iK5-AHAD4xhUOyEes3_Pqegy8qC7Oz-a_H6WV3xln0L3t0CcojGDlkAEgAsaaiLJfQxTLqiiu0tOKuE8s=s0-d)
![Reblog this post [with Zemanta]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_vhYfGrp-QyjeKANlERyk9Uzo6BQi3dAvY7-RoelV0I9r4cUe3_Idda4saRMEwWG3vx2DS4v53xF8XrsJzkl28azRwxA1Uf7_n69Tgw54zmeCKBz7A0KeHgeLweuNyj-GQ-LPdEIw8JRXpLtUTcj6tz=s0-d)
![Reblog this post [with Zemanta]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_u8WdBOTbors0fcOSjlLp4sMek8k4-uNL0fYzjGRIXX9i9471WM-kAe-nZkni_YV30DKOKn5Gqb6gwAKGNhMJwtb7sz1OkVjUC9lPfbqzwdLwEUO8pPU5nCePOJyj2eOXtkSq9s9dwzCOa5xtijDeOT=s0-d)