Cooperatives are great and generally better behaved than companies. They're fine for fields that don't require lots of innovation and change.
The problem is the people who start them often have to be more altruistic than typical. Since the effort and cost of starting one is similar to a starting a Company, but the financial rewards to those doing it are less, so why not start a company and make yourself rich instead?
Hence in my opinion, countries should encourage the starting of cooperatives. Maybe subsidize those who manage to start successful ones (but it shouldn't make them super rich). One may complain about that sort of subsidy, but since cooperatives are less prone common corporation evils, it can work out cheaper in the long run.
Yeah, ideas are a dime a dozen. I can come up with hundreds or thousands of ideas.
Remember that self inflating tyre thing? That's definitely an innovative idea. But the tricky thing? Building a tyre that self-inflates, and still is as safe, long-lasting, etc as a current tyre. You have to figure out how to self-inflate but still not pump too much water into the tyre in very wet weather. And test to make sure everything works fine even after thousands of miles of potholes and bumps. And test to see that when it fails it doesn't fail too badly.
Pretty easy to go: "transporter" or "warp drive". Building one is a whole different thing. From what I see the patent docs never have all the details required, so the justification for patents that a patent helps others build it later is bullshit.
They should only pay that Daniel Hogan guy on condition he does the jump- but with no help from them. He has to arrange it all himself.
You can. With TortoiseSVN you can store word docs in svn repo and do a diff between versions. That's about the only reason why I picked it years ago. Otherwise I'd be using git or something else.
However tortoisegit started supporting this too last year...
I just found an SQL injection attack and downloaded the whole password database. I know crack it at my own leisure.
Sure, but while the site is exploitable can't you pwn the rest of the site? You probably can pwn the rest of the database.
The solution it seems is to use different passwords for every site (or at least sites that matter). It doesn't even matter if the passwords are short. Once the hacker has enough access to get the passwords they normally have enough access to get the rest of the juicy data, or even change it.
Given the vast numbers of sites with weak security it seems a waste of time to use very long passwords. Just use passwords long enough that they won't brute force it via HTTP (which will probably look like a DoS/DDoS attack).
They should take it up with Harvard: http://www.health.harvard.edu/healthbeat/whats-the-beef-with-red-meat
That said the Japanese study is interesting, perhaps: a) the beef they eat is different b) the way they cook it is different c) what they eat with it is different d) 3 oz (85g) of beef per day doesn't kill you significantly faster.
So maybe beef is not actually bad for you and it's something else, however if you're going to eat US beef, US style in US quantities, then the Harvard study is more likely to apply than the Japanese study;).
I may be wrong but I get the impression the Japanese generally prefer quality over quantity when it comes to food.
Not true. Unless 'working like this' means sandboxes almost everything[1]. Most people get pwned not because of Windows bugs, but because they actually run the malware, or got exploited by a drive-by browser/pdf bug (Firefox, IE, Adobe etc all have had drive-by bugs). There were even viruses that were in password protected zipfiles, people had to enter the password in the email and open the file, and still many actually did that! In such scenarios even if they were running Linux or OSX they'd get pwned.
[1] In theory you could extend the executable signing stuff and have Windows require all "external" executables to state the sort of sandbox they want upfront. Then by their own stated intentions you can: a) better guess whether they are up to no good b) set an OS policy to not allow any executable that requests sandboxes that are too lax.
By "external" I mean not signed by MS AND classified as an OS internal executable.
Enterprises could even have a Trusted 3rd party audit an app, define a sandbox for it and sign it.
Antivirus software is trying to solve the "halting problem" without the full program and inputs. Sandboxing is like solving the "halting problem" by making sure the program halts by a certain point whether it wants to or not;).
Beef is not good for health. So don't eat it often, but if you're going to eat beef, pick the most enjoyable form for you. Otherwise you're just wasting your life and the beef.
If you don't like it, don't eat it. But if you really like steaks, unless you're really unlucky or unhealthy or stupid[1], a steak dinner every month or three isn't going to kill you that fast. Every week would probably be pushing it but some research would need to be done;).
If my browser is pwned by a drive by, the malware would still be running under a different account from my main account. It wouldn't be running using the same account as my financial browser account either.
The malware might be able to get my slashdot or facebook password, big deal. It can call home, but unless it uses a privilege escalation exploit it doesn't have access to the rest of my system and data. It can send spam or do a DDoS, but if it sends enough traffic or uses too much CPU/mem, I'm going to notice even if I don't sniff my network traffic.
And yes, most of the major AV vendors have done a similar screw up, hence that's why I think they are a bigger danger to me, and their stuff definitely slows things down.
Yes but I wonder if that is good enough. I suppose in theory it could be if you do it for different volume levels of pink noise - in case there are nonlinearities and other weirdness. But the phase could be important too, not just the frequency response.
Why would I? My browser runs as a more restricted account than my main user account, I don't use Adobe's PDF reader. If I'm hit by drive-by malware that is sophisticated enough to use a privilege escalation exploit, the malware author is likely to know how to use virustotal etc and make sure his malware passes all AV checks. So AV software wouldn't save me either.
They are unlikely to bother with my sort of config since they can already make money from the masses of people who need AV software, or from Governments asking them to get specific targets.
What you suggest is like a HIV test. Might be a good idea once in a while, but if you need to do it regularly you're doing things wrong.
If you've got malware calling home, you've already lost, you've already been pwned. You should also know that nowadays many things call home- Chrome, Firefox, etc.
AV users have a very similar situation too. They have no infections that they or their AV software know of.
You might assume the AV vendor is really good at spotting malware, but their job is like solving the halting problem, only without knowledge of the full inputs and program.
I on the other hand prefer to "solve" the halting problem by ensuring the program actually halts no matter what happens- aka Sandboxing.
This is slashdot. A better analogy would be saying I don't use condoms because I only have sex with myself. And if I ever do have sex with someone else, I'd use a condom, or do it virtually;).
Slashdot Mirror
You're not that aware of the technology or it would be obvious to you what he meant by: "You make a big list of valid hashes, GPG sign the list..."
You do it this way:
http://www.djangoproject.com/m/pgp/Django-1.2.7.checksum.txt
The stuff between: -----BEGIN PGP SIGNED MESSAGE-----
and:-----BEGIN PGP SIGNATURE-----
are signed by the corresponding signature.
more examples: http://distfiles.gentoo.org/releases/amd64/current-iso/stage3-amd64-20120621.tar.bz2.DIGESTS.asc
The temperature is much lower and so less heat energy is lost during the storage. The rate of cooling is much lower.
And a fair amount of the heat in the water can allegedly be reused:
http://www.forbes.com/sites/ericagies/2012/01/25/greening-the-grid-lightsail-aims-to-make-power-cleaner-by-making-energy-storage-cheap-and-plentiful/
http://www.wired.com/wiredenterprise/2012/07/danielle-fong/
Cooperatives are great and generally better behaved than companies. They're fine for fields that don't require lots of innovation and change.
The problem is the people who start them often have to be more altruistic than typical. Since the effort and cost of starting one is similar to a starting a Company, but the financial rewards to those doing it are less, so why not start a company and make yourself rich instead?
Hence in my opinion, countries should encourage the starting of cooperatives. Maybe subsidize those who manage to start successful ones (but it shouldn't make them super rich). One may complain about that sort of subsidy, but since cooperatives are less prone common corporation evils, it can work out cheaper in the long run.
A workaround is to add a bit of water (mist) to absorb that heat- reducing the temperature increase and thus the energy loss.
Sounds to me like you're staying away from religion for religious reasons ;).
Yeah, ideas are a dime a dozen. I can come up with hundreds or thousands of ideas.
Remember that self inflating tyre thing? That's definitely an innovative idea. But the tricky thing? Building a tyre that self-inflates, and still is as safe, long-lasting, etc as a current tyre. You have to figure out how to self-inflate but still not pump too much water into the tyre in very wet weather. And test to make sure everything works fine even after thousands of miles of potholes and bumps. And test to see that when it fails it doesn't fail too badly.
Pretty easy to go: "transporter" or "warp drive". Building one is a whole different thing. From what I see the patent docs never have all the details required, so the justification for patents that a patent helps others build it later is bullshit.
They should only pay that Daniel Hogan guy on condition he does the jump- but with no help from them. He has to arrange it all himself.
You can. With TortoiseSVN you can store word docs in svn repo and do a diff between versions. That's about the only reason why I picked it years ago. Otherwise I'd be using git or something else.
However tortoisegit started supporting this too last year...
What I wonder is how the system stops water from being pumped into the tyre in very wet weather (heavy rain).
In wet and somewhat cool weather presumably the tyres might more likely be less inflated and thus more likely to do the self-inflating thing.
I just found an SQL injection attack and downloaded the whole password database. I know crack it at my own leisure.
Sure, but while the site is exploitable can't you pwn the rest of the site? You probably can pwn the rest of the database.
The solution it seems is to use different passwords for every site (or at least sites that matter). It doesn't even matter if the passwords are short. Once the hacker has enough access to get the passwords they normally have enough access to get the rest of the juicy data, or even change it.
Given the vast numbers of sites with weak security it seems a waste of time to use very long passwords. Just use passwords long enough that they won't brute force it via HTTP (which will probably look like a DoS/DDoS attack).
They should take it up with Harvard: http://www.health.harvard.edu/healthbeat/whats-the-beef-with-red-meat
;).
That said the Japanese study is interesting, perhaps:
a) the beef they eat is different
b) the way they cook it is different
c) what they eat with it is different
d) 3 oz (85g) of beef per day doesn't kill you significantly faster.
So maybe beef is not actually bad for you and it's something else, however if you're going to eat US beef, US style in US quantities, then the Harvard study is more likely to apply than the Japanese study
I may be wrong but I get the impression the Japanese generally prefer quality over quantity when it comes to food.
Keep in mind MSSE is not free for businesses with more than 10 PCs.
Not true. Unless 'working like this' means sandboxes almost everything[1]. Most people get pwned not because of Windows bugs, but because they actually run the malware, or got exploited by a drive-by browser/pdf bug (Firefox, IE, Adobe etc all have had drive-by bugs). There were even viruses that were in password protected zipfiles, people had to enter the password in the email and open the file, and still many actually did that! In such scenarios even if they were running Linux or OSX they'd get pwned.
;).
[1] In theory you could extend the executable signing stuff and have Windows require all "external" executables to state the sort of sandbox they want upfront. Then by their own stated intentions you can:
a) better guess whether they are up to no good
b) set an OS policy to not allow any executable that requests sandboxes that are too lax.
By "external" I mean not signed by MS AND classified as an OS internal executable.
Enterprises could even have a Trusted 3rd party audit an app, define a sandbox for it and sign it.
Antivirus software is trying to solve the "halting problem" without the full program and inputs. Sandboxing is like solving the "halting problem" by making sure the program halts by a certain point whether it wants to or not
I'd rather eat dog biscuits than silage.
Then again, I've only noticed the silage that stunk... e.g. the crappy ones. I suppose you probably had access to the better stuff.
Beef is not good for health. So don't eat it often, but if you're going to eat beef, pick the most enjoyable form for you. Otherwise you're just wasting your life and the beef.
;).
If you don't like it, don't eat it. But if you really like steaks, unless you're really unlucky or unhealthy or stupid[1], a steak dinner every month or three isn't going to kill you that fast. Every week would probably be pushing it but some research would need to be done
[1] stupid = eating way too much, like a kilo.
Apparently it was methane not hydrogen: http://www.tert.am/en/news/2012/08/01/joxovurd/
So someone will need to do a test with hydrogen this time ;).
This guy plays fairly competitive Street Fighter, with his face and tongue:
https://www.youtube.com/watch?v=lx24B6RwekQ
https://www.youtube.com/watch?v=83nSodg-HTU
Perhaps the Asker should also mention what state his injured hand is in.
For throwaway email accounts? It's not like I care that much about my hotmail accounts.
And now it looks like Microsoft is telling hotmail users that they shouldn't care either.
If my browser is pwned by a drive by, the malware would still be running under a different account from my main account. It wouldn't be running using the same account as my financial browser account either.
The malware might be able to get my slashdot or facebook password, big deal. It can call home, but unless it uses a privilege escalation exploit it doesn't have access to the rest of my system and data. It can send spam or do a DDoS, but if it sends enough traffic or uses too much CPU/mem, I'm going to notice even if I don't sniff my network traffic.
And yes, most of the major AV vendors have done a similar screw up, hence that's why I think they are a bigger danger to me, and their stuff definitely slows things down.
That's old stuff: http://www.livescience.com/11022-herb-quells-cows-methane-laden-belches.html
http://www.telegraph.co.uk/earth/environment/globalwarming/7873998/Curry-for-sheep-could-curb-global-warming.html
http://www.treehugger.com/green-food/new-cow-diet-reduces-methane-emissionsand-no-its-not-mms.html
http://www.guardian.co.uk/science/2007/jul/10/ruralaffairs.climatechange
Even garlic appears to help.
Yes but I wonder if that is good enough. I suppose in theory it could be if you do it for different volume levels of pink noise - in case there are nonlinearities and other weirdness. But the phase could be important too, not just the frequency response.
Nah potassium iodide, 130mg.
Why would I? My browser runs as a more restricted account than my main user account, I don't use Adobe's PDF reader. If I'm hit by drive-by malware that is sophisticated enough to use a privilege escalation exploit, the malware author is likely to know how to use virustotal etc and make sure his malware passes all AV checks. So AV software wouldn't save me either.
They are unlikely to bother with my sort of config since they can already make money from the masses of people who need AV software, or from Governments asking them to get specific targets.
What you suggest is like a HIV test. Might be a good idea once in a while, but if you need to do it regularly you're doing things wrong.
If you've got malware calling home, you've already lost, you've already been pwned. You should also know that nowadays many things call home- Chrome, Firefox, etc.
AV users have a very similar situation too. They have no infections that they or their AV software know of.
You might assume the AV vendor is really good at spotting malware, but their job is like solving the halting problem, only without knowledge of the full inputs and program.
I on the other hand prefer to "solve" the halting problem by ensuring the program actually halts no matter what happens- aka Sandboxing.
This is slashdot. A better analogy would be saying I don't use condoms because I only have sex with myself. And if I ever do have sex with someone else, I'd use a condom, or do it virtually ;).