I don't even think Buzz was a failure, I think they thought it would immediately blow up, rather than slowly grow, then blow up with the network effect.
They should have worked on integrating it with picasa, in a non forced down your throat way, but instead allowing picasa to be your place to store photos, and making it easy to post them in Buzz.
Buzz had a few things going for it.
1) not everybody you ever met forever was your friend (I suppose that would fade if it took off) 2) not blocked by internet filters (more places allow gmail than facebook) 3) not full of junk (see 1)
My friends and I used it as essentially our private message board and it worked well for that. Wave was similar, but the realtime aspect of it made it pretty annoying. It shouldn't of sent anything until you hit submit the first time.
This was my biggest fear when I purchased a Chromecast, but actually it works fine in the background.
It doesn't really stream from Phone to Chromecast, what actually happens (I'm guessing based on behavior) is phone sends app to Chromecast when you set said app to cast, then your tablet sends commands to that app loaded on the chromecast, the Chromecast actually pulls the video from the internet itself, not your tablet. You can hit the home button and browse away, with most apps having control buttons in the ongoing part of the status pull down.
In fact, if your device goes away, you can no longer control the chromecast, but what's playing will finish.
I did until last year when I purchased a Macbook Pro with the 256GB SSD.
It's a work computer that I have total control over. Previously I had a thinkpad, Win7 for Creative suite, PowerPoint, and Trial Director, and Ubuntu for everything else (personal, and petty website work).
The new computer has a small hard drive, and rather than figure out howto: 1) triple boot 2) split it into three pieces
I use Win7 exclusively (I have a small OSX partition that I don't think has been booted since the first week I had the laptop).
Purchased the 13.3 inch for the lightness, and the screen. I can't wait until screens like this hit the PC world, bonus if it's cheaper even! Win7 suffers mildly on the screen, especially CS4, but it's totally work the minor annoyances to have real workspace when I'm off site for weeks at a time.
Actually, my bank is perfect for this method, as they have the secret questions either, and if you needed to get them right, and the password to login, I think you'd get similar protection??
The bank requires a secret question on new systems anyway, then verifies with a cookie, I bet you could combine said questions with the password the way this article describes.
It all becomes a shell game, if you need to connect to the main DB at any time, then a compromised system can be a problem.
The only solution I can think would involve downtime by writing to disk, booting single user mode, updating the master copy while safe in single user mode (assumption being that is as secure as memory anyway), reboot caching locally changes (which are probably not that often in a typical system).
You'd have to have an hour or so of scheduled downtime, in exchange for only users that signed up, or changed passwords since the last scheduled downtime are vulnerable. For many systems I'd think this is a reasonable trade, for example, my bank's website, that allows checks to be written (though not without email notification for email address change, and check being written), could go down an hour a week, or even a day between 4:30am and 5:30am eastern time (2:30-3:30 western), and it wouldn't be a big deal.
They did that to me too, no longer offering modem purchases, or modem only.
I was able to get it into bridging mode, but it was a big pain on the phone (they asked for a reason, and I just said work VPN equipment, and every rep I spoke too (I talked to 3 because switching modes revealed the one they shipped me was broken and I had to get a new one) knew what I meant and was super helpful, but I was kinda cranky that they locked the ability to bridge from the admin interface. The Modem / AP where I work allows the customer to turn on bridge mode.
The fact that you make that choice makes you a good driver (and that I don't arguably makes me a bad driver (thought I'm past median miles between accidents with no accidents yet, so I'm not the worse driver at least).
I'm not saying talking on the phone isn't bad, simply that those that talk on the phone don't consider the potential issues with driving distracted in general, and frequently make the wrong call (such as reaching for a dropped candy bar, etc.).
Part of the issue with many studies is they take people, but them on a course or simulator, have them drive. This has them driving at their best (there's a word for subjects being better than real life when being studied, I'm too lazy to find it). Somebody focused on driving with full attention is obviously significantly better than someone that isn't, but in day to day driving many (such as myself) are not particularly focused anyway.
And studies where people are actually driving in real world environments find that talking on the phone does not increase accidents. They did find that operating the phone does, at a similar rate to any other activity that takes one's eyes off the road for a second. The dialing is dangerous, the talking not so much so. In the real world that is, because in the real world people aren't hyper focused on driving, the phone cuts into that other part, not the driving part.
It's the day dreaming, the trying to place a song, drinking of coffee, adjusting the radio, etc. Part of the brain that the phone deprives in real life.
In the study you mention, all that is artificially focused on driving.
The problem is that in these studies people are focusing when not using a phone. So it's focused driver vs cell phone driver, but in reality many drivers dont focus in real life.
Studies that worked by installing cameras in cars and seeing what actually was going on found that the accident prone drivers were quite often doing terrifying things behind the wheel, only one of which was too much focus on a phone conversation.
They said that it didn't take long for people to stop acting like there was a camera, but it did take days, not hours.
Cabs are regulated similar to the post-office, there are more and less profitable routes, and some subsidize others.
They don't want non-licensed services that can charge whatever they want to snipe profitable routes at a lower rate.
I'm not saying it's good, but it's really not a case of artificial scarcity. I know I've gone on routes that are higher than they like, and others where they'd be happy to negotiate a lower price.
And Unity isn't terrible, as long as they keep things easily replaceable (by using Wayland etc. under it), they have real potential I think.
What they are doing with phone has real promise too. They really need to work within the system though. KDE is working on similar things with Plasma (netbook, vs desktop, vs active), it'd be great if at least some of the work between the two is sharable. Not just great, but part of the platonic idea of FOSS.
Ubuntu started projects used to get adopted, as time went on, they went more off the walls, and their projects became tainted.
The Mir thing is really upsetting to me as a user, because Wayland has demonstrated the ability to take feedback and adapt, making the whole split seem like lies.
Wayland really seems like a smartly run project handled very well, that seems to be a huge mistake.
Even if in principal I like the idea of Android drivers working, I think Wayland has been working on that too though.
Upstart vs Systemd I have no specific opinion of (though systemd I think addresses a security risk designed into upstart), but at this point upstart is done, everyone else has chosen, even those that initially used upstart (Fedora).
They need to take credit (even false) for spreading ideas (upstart, actually using wayland, experimenting with what it can and cannot do), and use what gets settled on, unless there truly is something missing.
but from what I can tell, the Ubuntu style release schedule took off over-all.
And as long as things are consistent, it will have the effect Ubuntu wanted (or close too it, they basically wanted upstream to release 4 months before them, so they could integrate if memory serves).
I always assumed that punishments were to keep people honest and prevent crime but keeping people honest. Not for the sake of revenge. So you need to go to haul thrive the next guy pause.
That's what I was thinking. The whole summary made me sick. Justice isn't a code word for vengence.
There's an argument to be made for execution, if someone is deemed beyond redemption, but to invent drugs to extend punishment is horrible. Unless the idea is someone can be released in a week, and become productive rather than a drain on society.
I'm pretty sure that it's constantly getting more stable, and if OpenSUSE is using it, they probably did vet it.
I'm pretty sure the only point of distros like OpenSUSE or Fedora are to get wide testing on new technologies (this is good, and running them is a great way to give back to the community).
I would guess that in a year btrfs is going to be the default in general, but it takes someone to make the leap of faith to start that rolling. If no main stream distro adopts ever, it will by tautology never be the default.
Props to OpenSUSE!, good luck to their users, or more realistically, not bad luck.
Most OpenSUSE users use it because they generally like, and trust, the choices of OpenSUSE. This trust may be misplaced, we'll know soon, but in the learning, we'll have a MUCH better understanding of how ready btrfs is to move past the beta testing zone (or if OpenSUSE bosses are right, proven to be past there).
Defaults matter, reputations of Linux distros can shatter on them, because we're not passive users, and thought they aren't all drop in replacements, as non-passive users, they're close enough.
Slashdot Mirror
I don't even think Buzz was a failure, I think they thought it would immediately blow up, rather than slowly grow, then blow up with the network effect.
They should have worked on integrating it with picasa, in a non forced down your throat way, but instead allowing picasa to be your place to store photos, and making it easy to post them in Buzz.
Buzz had a few things going for it.
1) not everybody you ever met forever was your friend (I suppose that would fade if it took off)
2) not blocked by internet filters (more places allow gmail than facebook)
3) not full of junk (see 1)
My friends and I used it as essentially our private message board and it worked well for that. Wave was similar, but the realtime aspect of it made it pretty annoying. It shouldn't of sent anything until you hit submit the first time.
This was my biggest fear when I purchased a Chromecast, but actually it works fine in the background.
It doesn't really stream from Phone to Chromecast, what actually happens (I'm guessing based on behavior) is phone sends app to Chromecast when you set said app to cast, then your tablet sends commands to that app loaded on the chromecast, the Chromecast actually pulls the video from the internet itself, not your tablet. You can hit the home button and browse away, with most apps having control buttons in the ongoing part of the status pull down.
In fact, if your device goes away, you can no longer control the chromecast, but what's playing will finish.
I wonder if thats addressed in TFA?
In any case, this isn't my problem, since I took the Burner Express bus in and out of Burning Man and would plan on doing it again.
Yep, it is.
I did until last year when I purchased a Macbook Pro with the 256GB SSD.
It's a work computer that I have total control over. Previously I had a thinkpad, Win7 for Creative suite, PowerPoint, and Trial Director, and Ubuntu for everything else (personal, and petty website work).
The new computer has a small hard drive, and rather than figure out howto:
1) triple boot
2) split it into three pieces
I use Win7 exclusively (I have a small OSX partition that I don't think has been booted since the first week I had the laptop).
Purchased the 13.3 inch for the lightness, and the screen. I can't wait until screens like this hit the PC world, bonus if it's cheaper even! Win7 suffers mildly on the screen, especially CS4, but it's totally work the minor annoyances to have real workspace when I'm off site for weeks at a time.
That sounds horribly inefficient.
You're using heat from somewhere to make the oil and gas, but not convert all of the carbon in the wood.
Then you take a subset of the carbon and burn it in the form of oil and gas.
Actually, my bank is perfect for this method, as they have the secret questions either, and if you needed to get them right, and the password to login, I think you'd get similar protection??
The bank requires a secret question on new systems anyway, then verifies with a cookie, I bet you could combine said questions with the password the way this article describes.
It all becomes a shell game, if you need to connect to the main DB at any time, then a compromised system can be a problem.
The only solution I can think would involve downtime by writing to disk, booting single user mode, updating the master copy while safe in single user mode (assumption being that is as secure as memory anyway), reboot caching locally changes (which are probably not that often in a typical system).
You'd have to have an hour or so of scheduled downtime, in exchange for only users that signed up, or changed passwords since the last scheduled downtime are vulnerable. For many systems I'd think this is a reasonable trade, for example, my bank's website, that allows checks to be written (though not without email notification for email address change, and check being written), could go down an hour a week, or even a day between 4:30am and 5:30am eastern time (2:30-3:30 western), and it wouldn't be a big deal.
I bet that makes password changes and adding accounts super easy too.
They did that to me too, no longer offering modem purchases, or modem only.
I was able to get it into bridging mode, but it was a big pain on the phone (they asked for a reason, and I just said work VPN equipment, and every rep I spoke too (I talked to 3 because switching modes revealed the one they shipped me was broken and I had to get a new one) knew what I meant and was super helpful, but I was kinda cranky that they locked the ability to bridge from the admin interface. The Modem / AP where I work allows the customer to turn on bridge mode.
The fact that you make that choice makes you a good driver (and that I don't arguably makes me a bad driver (thought I'm past median miles between accidents with no accidents yet, so I'm not the worse driver at least).
I'm not saying talking on the phone isn't bad, simply that those that talk on the phone don't consider the potential issues with driving distracted in general, and frequently make the wrong call (such as reaching for a dropped candy bar, etc.).
Part of the issue with many studies is they take people, but them on a course or simulator, have them drive. This has them driving at their best (there's a word for subjects being better than real life when being studied, I'm too lazy to find it). Somebody focused on driving with full attention is obviously significantly better than someone that isn't, but in day to day driving many (such as myself) are not particularly focused anyway.
I think it was this study:
http://www.vt.edu/spotlight/ac...
along with explanation (by study author) on this podcast:
http://freakonomics.com/2013/1...
that formed my opinion.
And studies where people are actually driving in real world environments find that talking on the phone does not increase accidents. They did find that operating the phone does, at a similar rate to any other activity that takes one's eyes off the road for a second. The dialing is dangerous, the talking not so much so. In the real world that is, because in the real world people aren't hyper focused on driving, the phone cuts into that other part, not the driving part.
It's the day dreaming, the trying to place a song, drinking of coffee, adjusting the radio, etc. Part of the brain that the phone deprives in real life.
In the study you mention, all that is artificially focused on driving.
The problem is that in these studies people are focusing when not using a phone. So it's focused driver vs cell phone driver, but in reality many drivers dont focus in real life.
Studies that worked by installing cameras in cars and seeing what actually was going on found that the accident prone drivers were quite often doing terrifying things behind the wheel, only one of which was too much focus on a phone conversation.
They said that it didn't take long for people to stop acting like there was a camera, but it did take days, not hours.
Aren't the prices set by law too?
Cabs are regulated similar to the post-office, there are more and less profitable routes, and some subsidize others.
They don't want non-licensed services that can charge whatever they want to snipe profitable routes at a lower rate.
I'm not saying it's good, but it's really not a case of artificial scarcity. I know I've gone on routes that are higher than they like, and others where they'd be happy to negotiate a lower price.
from TFS it sounds like it's part of x.org, it's all the same developers.
I assume it's a server that kicks to Wayland, similar to Xnest kicking to X.
I did state take credit for "ideas", "even falsely".
I thought the wayland/android thing was a response to Mir though. And that part of the reason Mir came to be was to use Android driver.
And Unity isn't terrible, as long as they keep things easily replaceable (by using Wayland etc. under it), they have real potential I think.
What they are doing with phone has real promise too. They really need to work within the system though. KDE is working on similar things with Plasma (netbook, vs desktop, vs active), it'd be great if at least some of the work between the two is sharable. Not just great, but part of the platonic idea of FOSS.
yeah.
Ubuntu started projects used to get adopted, as time went on, they went more off the walls, and their projects became tainted.
The Mir thing is really upsetting to me as a user, because Wayland has demonstrated the ability to take feedback and adapt, making the whole split seem like lies.
Wayland really seems like a smartly run project handled very well, that seems to be a huge mistake.
Even if in principal I like the idea of Android drivers working, I think Wayland has been working on that too though.
Upstart vs Systemd I have no specific opinion of (though systemd I think addresses a security risk designed into upstart), but at this point upstart is done, everyone else has chosen, even those that initially used upstart (Fedora).
They need to take credit (even false) for spreading ideas (upstart, actually using wayland, experimenting with what it can and cannot do), and use what gets settled on, unless there truly is something missing.
but from what I can tell, the Ubuntu style release schedule took off over-all.
And as long as things are consistent, it will have the effect Ubuntu wanted (or close too it, they basically wanted upstream to release 4 months before them, so they could integrate if memory serves).
In what way did they violate the trademark?
I always assumed that punishments were to keep people honest and prevent crime but keeping people honest. Not for the sake of revenge.
So you need to go to haul thrive the next guy pause.
That's what I was thinking. The whole summary made me sick. Justice isn't a code word for vengence.
There's an argument to be made for execution, if someone is deemed beyond redemption, but to invent drugs to extend punishment is horrible. Unless the idea is someone can be released in a week, and become productive rather than a drain on society.
I'm pretty sure that it's constantly getting more stable, and if OpenSUSE is using it, they probably did vet it.
I'm pretty sure the only point of distros like OpenSUSE or Fedora are to get wide testing on new technologies (this is good, and running them is a great way to give back to the community).
I would guess that in a year btrfs is going to be the default in general, but it takes someone to make the leap of faith to start that rolling. If no main stream distro adopts ever, it will by tautology never be the default.
Props to OpenSUSE!, good luck to their users, or more realistically, not bad luck.
More likely scenario,
Most OpenSUSE users use it because they generally like, and trust, the choices of OpenSUSE. This trust may be misplaced, we'll know soon, but in the learning, we'll have a MUCH better understanding of how ready btrfs is to move past the beta testing zone (or if OpenSUSE bosses are right, proven to be past there).
Defaults matter, reputations of Linux distros can shatter on them, because we're not passive users, and thought they aren't all drop in replacements, as non-passive users, they're close enough.
And fully supported means experimental?