Managing friends in Google Reader is slow, and hard to do
I see most news faster on Twitter than in Google Reader.
iPhone apps are much more robust and better for sharing, retweeting, etc. Google Reader apps (and I have five on my iPhone) don't make it easy to share and reading on them
CPU: VIA VM8650 800MHZ
9.7" TFT Touch LCD (1:1)/Resolution:1024x800
Multimedia Codes: Support MP3/Audio Format support 3GP/Video Format support WORD,EXCEL,MAIL &PDF READER
Web vedio with the ICON / RAM:1G
HARD DISK:16GB NAND FLASH,
WIFI: 802.11B/G Battery: 2400MAH
Orientation Sensor: automatic steering display screen
Sound Effect: Stereo speakers device, Built-in micphone.
Audio: High-Fidelity stereo speaker output
Software: Google Android
Browser: Google chome-lite UCWEB Browser
Desktop: Android, automatically change the wallpaper (like win7), update frequencies can be set to 1hour to 6 days
E-book and Office word processing, Document to Go (Word, Excel, PPT, PDF), Support E-book function
E-Mail: Mainstream Web Mail service Gmaill/Yahoo Mail/Hotmail/Sina Mail/163 Mail
Communication Software: Fring,SkypeOut can call local call、long-distance call、overseas call and mobile call , MSN,SKYPE,GTALK
Game: G-Sensor game, Classic game, Touch game
Automatic screen rotation: Four-Direction Rotate screen
Note Paper: desktop tools, support 1x1~4x4 custom size
Resco Explorer: Android task Killer,Andexplorerhao de
You can share any content from any web page, even if the site doesn't have a feed.
For even more control over what gets shared, select some text from the page before clicking the "Note in Reader" bookmarklet and your selection will appear as the item's body.
Have you ever wanted to share something that you were reading, but you didn't want to go through the hassle of subscribing to a whole feed for a single interesting article? And what about sharing content from sites with no feeds? There you are, reading along, and you think to yourself, "If only everything on the web had a 'Share' button like in Google Reader!"
Streamy can easily become a great alternative to Google Reader and Tweetdeck. It's already one of the most fully-featured social media aggregators we have seen.
dynamic overlays that allow any blogger or online publisher to integrate multimedia content into their pages.
use Zemanta as usual
insert links
After your post goes public,
additional icon
allow your readers to access the information
without having to leave
content from from the Creative Commons-licensed Freebase database
includes information from sources such as YouTube, Wikipedia, Google Maps, and MusicBrainz
millions of articles from Freebase contributors.
Balloon links will appear only when we can show a smart overlay
It’s about standards and open web
The underlying code for Balloons is open source and built on the Common Tag architecture
open tagging format
developed by Zemanta, Yahoo, AdaptiveBlue, Freebase, and others.
make content more connected, discoverable, and engaging.
every aspect of Balloons – from its open source code base to its use of Freebase’s openly licensed content – has been designed to ensure the easy, free, and open spread of information across the web.
find other people that are commenting on the post and join the conversation
other blogs
Blogger/Blogspot, Digg, Disqus, FriendFeed,
Google Blog Search, Google Reader, Identi.ca, IntenseDebate, Mixx, Reddit, StumbleUpon, Technorati, Twitter,
TypePad/MoveableType and WordPress blogs
As social media has become a game changer for industries across the board, you can bet the experts at this year's TED conference will have their sights set on peeling back the hype and getting at the core of what social technology has in store for this year and beyond.
In simple terms, CSS preprocessing is a method of extending the feature set of CSS by first writing the style sheets in a new extended language, then compiling the code to vanilla CSS so that it can be read by Web browsers. Several CSS preprocessors are available today, most notably Sass2 and LESS3.
Polling sucks. We think a decentralized pubsub layer is a fundamental, missing layer in the Internet architecture today
a fundamental design that looks like this: This picture leaves out multiple publishers and subscribers and the subscriber registration process, but you get the basic idea
fine for server subscribers (like, say Google Reader) but not for client subscribers (like, say TweetDeck).
the only way to enable client subscribers to play in this async messaging world is via some type of relay service
In this approach, the client subscriber makes an outbound connection to some type of relay infrastructure
technically feasible
Yes, having to relay messages sucks. But the question is