What I would like to see: some FLOSS home server (camouflaged as a wireless router) that did all this same stuff for the average guy. If we had a popular federated social networking protocol, it should include that, as well as e-mail, chat, on-line/off-line docs, etc. Register for a domain name from the vendor to have automatic dynamic DNS and backups of data. I'm thinking of something like eBox (or Zentyal, I think, as it's called now). My data in my house. Backed up. Ubiquitous. No real set-up. If the vendor goes bust, you could just change vendors the way you change registrars.
First of all, I'd like to say that I'm a huge proponent of Chrome OS. I did a month-long "live in a browser" stint two years ago.
That said, this is an extension of what I've been doing for years: back up my apps with debconf-get-selections and keep a backup of my files. It's nothing new (even my backups weren't local before). The only real difference? This is seamless.
1) "persons" and "people" are different words with different meaniings.
2)We as a people need to decide whether a fetus is a person or not and either stop allowing abortions or stop charging people of vehicular manslaughter, etc. for the death of a fetus.
Even if it's fairly locked down, I'd be happy to see it hit 10% of the market, with iOS and OS X also at 10% each. The 60+% left for MS Windows would mean that my OS of choice would be a lot more likely to work on sites and hardware I use.
Any app I run could modify my.bashrc or install something to $HOME/local and run on log-in. As long as I have network access, the program can create a botnet.
ChromeOS updates automatically, just like Chrome does if you have the privileges so the images aren't old. The system auto-updates and auto-heals. Your extensions and "apps" are sync'ed whenever you login to any ChromeOS machine.
It could be less than 30 secs. I don't know. It will certainly cost over $800 less. Schmidt intends these to be appliances for enterprises running Google Apps (a.k.a. thin clients, a la SunRays, which he worked with).
Oh, then in that case, you get an extra $800 in your pocket. You may like your purchase, but there's definitely a market for this (hint: Schmidt's a big fan of SunRays).
Chrome OS is Google's enterprise push on top of Apps. it need a lot of bandwidth. the mobile world hasn't gotten there yet. expect Android to become more like Chrome OS over time.
I read this last night on Reddit, and have been chewing on it. I see this as a move to get mobile developers by piggy-backing on the Obj-C knowledge of iOS devs. Same language -- subset of API.
Exactly my point. No need to sign up on a site. No need for fifteen social media buttons -- just one -- and the share's pushed to whichever ones you've decided to push to.
This requires profiles and incognito in browsers by tab if desired, of course.
OSW works and has worked for months, unlike Diaspora. It's built on a mature codebase and protocol, unlike Diaspora (Ostatus is interesting, though). XMPP is extensible and most of the plugins necessary for a social network are already available. Get Google, Yahoo! and MS to support the protocol in their IM/e-mail clients, and they stop the hemorrhage of IMers to full-time Facebook use. Finally, put the protocol in the browser and have true social identity.
Agreed on OneSocialWeb -- they were out the door with working, federatable servers before Diaspora even got announced. XMPP has its drawbacks, but I think social should be a W3C protocol and it should be integrated into the browser. Heck, just right-click on a picture in your browser, choose "share," and publish to anyone or everyone on any network. It should be that easy.
Ummm. they're basing it on OStatus. I'd prefer to see XMPP because security and granular permissions are already solved there, but OStatus is an open protocol.
Hopefully, people don't join "Diaspora" -- they join a rebranded system with support from whatever provider they want and get the benefits of federation.
Slashdot Mirror
What I would like to see: some FLOSS home server (camouflaged as a wireless router) that did all this same stuff for the average guy. If we had a popular federated social networking protocol, it should include that, as well as e-mail, chat, on-line/off-line docs, etc. Register for a domain name from the vendor to have automatic dynamic DNS and backups of data. I'm thinking of something like eBox (or Zentyal, I think, as it's called now). My data in my house. Backed up. Ubiquitous. No real set-up. If the vendor goes bust, you could just change vendors the way you change registrars.
What's funny is that Schmidt mentions all of these and why he thinks this time will be a success when he's talking about Chrome OS
First of all, I'd like to say that I'm a huge proponent of Chrome OS. I did a month-long "live in a browser" stint two years ago.
That said, this is an extension of what I've been doing for years: back up my apps with debconf-get-selections and keep a backup of my files. It's nothing new (even my backups weren't local before). The only real difference? This is seamless.
1) "persons" and "people" are different words with different meaniings.
2)We as a people need to decide whether a fetus is a person or not and either stop allowing abortions or stop charging people of vehicular manslaughter, etc. for the death of a fetus.
Even if it's fairly locked down, I'd be happy to see it hit 10% of the market, with iOS and OS X also at 10% each. The 60+% left for MS Windows would mean that my OS of choice would be a lot more likely to work on sites and hardware I use.
Any app I run could modify my .bashrc or install something to $HOME/local and run on log-in. As long as I have network access, the program can create a botnet.
ChromeOS updates automatically, just like Chrome does if you have the privileges so the images aren't old. The system auto-updates and auto-heals. Your extensions and "apps" are sync'ed whenever you login to any ChromeOS machine.
It could be less than 30 secs. I don't know. It will certainly cost over $800 less. Schmidt intends these to be appliances for enterprises running Google Apps (a.k.a. thin clients, a la SunRays, which he worked with).
Oh, then in that case, you get an extra $800 in your pocket. You may like your purchase, but there's definitely a market for this (hint: Schmidt's a big fan of SunRays).
Chrome OS is Google's enterprise push on top of Apps. it need a lot of bandwidth. the mobile world hasn't gotten there yet. expect Android to become more like Chrome OS over time.
Single signon to google apps in thirty seconds from cold boot.
I wasn't defending it: you sounded like you didn't know.
The goal is to write a GTK+ backend for Wayland.
I read this last night on Reddit, and have been chewing on it. I see this as a move to get mobile developers by piggy-backing on the Obj-C knowledge of iOS devs. Same language -- subset of API.
No problem.
Exactly my point. No need to sign up on a site. No need for fifteen social media buttons -- just one -- and the share's pushed to whichever ones you've decided to push to.
This requires profiles and incognito in browsers by tab if desired, of course.
OpenID, OAuth, Atom/RSS, PubSubHubbub, ActivityStreams, Salmon, and WebFinger
OSW works and has worked for months, unlike Diaspora. It's built on a mature codebase and protocol, unlike Diaspora (Ostatus is interesting, though). XMPP is extensible and most of the plugins necessary for a social network are already available. Get Google, Yahoo! and MS to support the protocol in their IM/e-mail clients, and they stop the hemorrhage of IMers to full-time Facebook use. Finally, put the protocol in the browser and have true social identity.
Linux succeeded / got popular on the server in the 90s, long before GNOME or KDE existed. He wasn't talking about desktops or replacing MS Windows.
DNF had numerous demos, too, but never really shipped.
OK, Eric Schmidt. I'll do that.
Agreed on OneSocialWeb -- they were out the door with working, federatable servers before Diaspora even got announced. XMPP has its drawbacks, but I think social should be a W3C protocol and it should be integrated into the browser. Heck, just right-click on a picture in your browser, choose "share," and publish to anyone or everyone on any network. It should be that easy.
Ummm. they're basing it on OStatus. I'd prefer to see XMPP because security and granular permissions are already solved there, but OStatus is an open protocol.
Solved by putting XMPP and social in every browser (see sig) -- then there's no associated name at all, and social becomes just like HTTP.
Hopefully, people don't join "Diaspora" -- they join a rebranded system with support from whatever provider they want and get the benefits of federation.