But if you take the time to record the results of a single roulette wheel over the course of a month or so, you'll find that certain numbers are more frequent than others. I would think the obvious countermeasure to this would be to swap the wheels arround every so often (maybe once a week or so).
I don't think they ever used hard drives. Afaict they went straight from tape to flash.
The big problem I see with streaming the data off is keeping it working under adverse conditions. Afaict in a large proportion of crashes some kind of adverse weather conditions or unusually low flight or power failures or other things that are likely to screw up communications are involved.
what for? They know what the pilot is doing to the controls from the flight data recorder (which is seperate from the cockpit voice recorder to increase the chances of recovering at least one of them). They know what the pilots were saying to each other from the cockpit voice recorder. Afaict that is all they really need to know to work out what the pilots did in the runup to the crash.
The software is free software and there are plenty of alternatives anyway. The main data is freely downloadable (the images aren't downloadable en-masse anymore unfortunately due to thier huge size but I doubt a serious fork operator would have that much trouble getting hold of them all) and released under a free license..
but without a community of users large enough to effectively maintain it you just have a huge body of mostly static information that is getting steadilly more and more outdated. Think of the problems of forking a large peice of open source software and getting a sufficiant team that the fork doesn't rot. Now understand that the number of contributors to wikipedia is huge compared to even very large open source software.
To sumerise your post, due to regulatory (must use this exact part or go through recertification) and supply (manufacturer discontinuation) your company was pushed into taking the desperate measure of buying ICs from dubious suppliers without knowing thier original source.
I wonder how often counterfiet chips end up in things like medical gear without being noticed, it is a rather scary thought and potentially far more dangerous than a carefully chosen substitution by engineers who know the product.
At least according to what I have read on microsofts site the only time vista needs periodic reactivation (that is a requirement for reactivation that is triggered by time rather than hardware changes) is when you are activating against your companies internal KMS server. Do you have any evidence to the contary.
I thought the real reason they wanted to replace copper with fiber was because of the lack of laws forcing them to open up thier fiber lines to competition.
I have used microsofts scanpst file to repair corrupt PST files in the past. One big problem I have run into is emails that can be read and even moved about within the repaied PST file but any attempt to copy them to a clean PST file causes errors.
given the rather large number of windows systems that are still on fat with it's famous large cluster sizes using a single file per email would be very wastefull of disk space. Also many small files makes actions such as disk checking and file copying far slower.
IMO a more sensible answer is multiple small but not tiny files. e.g. maybe use one file for all the email downloaded during one session.
DO NOT TRY AND MOVE A DOMAIN THAT IS ABOUT TO EXPIRE IN THE NEXT MONTH OR SO. The combination of imminent expiry and a move attempt is a recipie for mixups. If you have a name with less than a couple of months left on it and you want to keep that name the first thing you should do is renew it where it is.
It has always seemed to me that having the registrar and registry for your domain in different judristrictions would increase your legal exposure not reduce it.
At least for GSM phones the soloution is not to buy your phones from the network but to buy them with plain manufacturer firmware either direct from the manufacturer or from a small dealer. Sure you will miss out on the subsidy from the network but from the sounds of the project you were doing that would be a relatively small part of the overall cost.
Last mile communication service is a natural monopoly. The only reason quite a few areas have a duopoly is historic (prior to the digital revoloution phone and TV required different types of infrastructure).
The only real answer is to seperate out the running of the bits that are a natural monopoly from the rest of the service and then heavilly regulate the bits that are a natural monopoly. E.g. your problem would have been solvable if there was a independent complains body you or your ISP could turn to who had the power to force bell to sort the line out.
Symbian didn't seem that bad to me, you could do basic stuff (including internet access and access to the user data areas of the filesystem) with a self signed cert (ones with generic nokia firmware anyway, I hear some providers disabled that in the phones they sold). You could do a lot more on your own phone by applying for a free devcert.
Yes deploying apps that needed restricted capabilites to people not prepared to get thier own devcerts was a pain and the extra locking down that some providers did was also a pain but in general it seemed a lot better than the impression I am getting here of what iPhone dev will be like.
Afaict nowadays there are two main reasons to buy MSDN
* You really need the extra features that are in the higher editions of microsofts development tools (afaict theese extra features are mainly targeted at building "corportate" style apps) * You want the ability to download and install lots of different versions of microsoft software for really thorough testing. * You want the ability to download almost anything MS from one place (for example the WDK can be obtained without going through MSDN but it requires seperate signup to do so)
Yes MSDN is nice to have but it is not in any way a requirement for developing and selling apps on windows.
for example: if i sell you a gun, i am not responsible for how you use that gun If you go round knowingly selling guns to street gangs who it is reasonable to suspect are using them for criminal purposes imo you deserve a share of the blame for what is done with those guns.
Similarlly if you go arround selling big military weapons to dictatorships who it is reasonable to suspect will use them for agressive purposes then imo you deserve a share of the blame for what is done with them.
plenty of seeds too, over four times as many seeds as leachers right now. It took me a while to download last night (i'm seeding now) partly because I have a shitty ISP and partly because I cba setting up a port forward.
Then why license the whole album under creative commons thereby opening the floodgates for legal torrenting of the whole damn thing? Doesn't that seem at all contradictory to you? Not really, it sounds like a statement of not wanting to criminalise fans who share his music while still encouraging fans to pay for the music.
you can easilly set up a tracker to require authentication and it wouldn't be too hard to set up a system which generated authentication keys on the fly and put some limits on the use of one key.
But if you know the IP of a machine in the swarm and that machine has finished downloading and become a seed then there is nothing the tracker can do to stop you downloading from them. There are also peer-peer tracking systems though I belive most clients will respect requests from the tracker not to use them.
looks like your post on/. has caused the leaches counter to shoot up again and a few peers have dropped off. 318:180 (seed:leacher) is what my client reports now and it's going to be downloading all night.
It doesn't matter, because the only thing that matters is the positive contribution he made by founding Wikipedia and his later life or his personal details don't effect that. It DOES matter because the wikimedia foundation (who own/run wikipedia along with various other related sites) has not at this time made the transition from a single person dominated organisation (iirc there is a board of directors but it is a 5 member board two of which are jimbo and his cronies 2 of which are elected effectively giving wales absoloute power over the project) to an organisation with a broader power base.
Yes you can take a copy the main content easilly enough but you can't get the images so easilly (and if you could they would take up a huge ammount of storage) and you will either have to accept changes from wikipedia without much oversight or fork (and if you fork your fork will go stale).
But if you take the time to record the results of a single roulette wheel over the course of a month or so, you'll find that certain numbers are more frequent than others.
I would think the obvious countermeasure to this would be to swap the wheels arround every so often (maybe once a week or so).
I don't think they ever used hard drives. Afaict they went straight from tape to flash.
The big problem I see with streaming the data off is keeping it working under adverse conditions. Afaict in a large proportion of crashes some kind of adverse weather conditions or unusually low flight or power failures or other things that are likely to screw up communications are involved.
what for? They know what the pilot is doing to the controls from the flight data recorder (which is seperate from the cockpit voice recorder to increase the chances of recovering at least one of them). They know what the pilots were saying to each other from the cockpit voice recorder. Afaict that is all they really need to know to work out what the pilots did in the runup to the crash.
no what really matters is the community.
The software is free software and there are plenty of alternatives anyway. The main data is freely downloadable (the images aren't downloadable en-masse anymore unfortunately due to thier huge size but I doubt a serious fork operator would have that much trouble getting hold of them all) and released under a free license..
but without a community of users large enough to effectively maintain it you just have a huge body of mostly static information that is getting steadilly more and more outdated. Think of the problems of forking a large peice of open source software and getting a sufficiant team that the fork doesn't rot. Now understand that the number of contributors to wikipedia is huge compared to even very large open source software.
To sumerise your post, due to regulatory (must use this exact part or go through recertification) and supply (manufacturer discontinuation) your company was pushed into taking the desperate measure of buying ICs from dubious suppliers without knowing thier original source.
I wonder how often counterfiet chips end up in things like medical gear without being noticed, it is a rather scary thought and potentially far more dangerous than a carefully chosen substitution by engineers who know the product.
At least according to what I have read on microsofts site the only time vista needs periodic reactivation (that is a requirement for reactivation that is triggered by time rather than hardware changes) is when you are activating against your companies internal KMS server. Do you have any evidence to the contary.
I thought the real reason they wanted to replace copper with fiber was because of the lack of laws forcing them to open up thier fiber lines to competition.
I have used microsofts scanpst file to repair corrupt PST files in the past. One big problem I have run into is emails that can be read and even moved about within the repaied PST file but any attempt to copy them to a clean PST file causes errors.
any ideas how to get arround this issue?
given the rather large number of windows systems that are still on fat with it's famous large cluster sizes using a single file per email would be very wastefull of disk space. Also many small files makes actions such as disk checking and file copying far slower.
IMO a more sensible answer is multiple small but not tiny files. e.g. maybe use one file for all the email downloaded during one session.
probablly the most important point
DO NOT TRY AND MOVE A DOMAIN THAT IS ABOUT TO EXPIRE IN THE NEXT MONTH OR SO. The combination of imminent expiry and a move attempt is a recipie for mixups. If you have a name with less than a couple of months left on it and you want to keep that name the first thing you should do is renew it where it is.
It has always seemed to me that having the registrar and registry for your domain in different judristrictions would increase your legal exposure not reduce it.
At least for GSM phones the soloution is not to buy your phones from the network but to buy them with plain manufacturer firmware either direct from the manufacturer or from a small dealer. Sure you will miss out on the subsidy from the network but from the sounds of the project you were doing that would be a relatively small part of the overall cost.
you do know that there is nothing forcing developers to use the layout managers in awt/swing right?
Last mile communication service is a natural monopoly. The only reason quite a few areas have a duopoly is historic (prior to the digital revoloution phone and TV required different types of infrastructure).
The only real answer is to seperate out the running of the bits that are a natural monopoly from the rest of the service and then heavilly regulate the bits that are a natural monopoly. E.g. your problem would have been solvable if there was a independent complains body you or your ISP could turn to who had the power to force bell to sort the line out.
The real questions is can you leave it on the iphone after disconnecting from the mac
Symbian didn't seem that bad to me, you could do basic stuff (including internet access and access to the user data areas of the filesystem) with a self signed cert (ones with generic nokia firmware anyway, I hear some providers disabled that in the phones they sold). You could do a lot more on your own phone by applying for a free devcert.
Yes deploying apps that needed restricted capabilites to people not prepared to get thier own devcerts was a pain and the extra locking down that some providers did was also a pain but in general it seemed a lot better than the impression I am getting here of what iPhone dev will be like.
can you develop an app and use it on your own phone without paying apple a thing?
Afaict nowadays there are two main reasons to buy MSDN
* You really need the extra features that are in the higher editions of microsofts development tools (afaict theese extra features are mainly targeted at building "corportate" style apps)
* You want the ability to download and install lots of different versions of microsoft software for really thorough testing.
* You want the ability to download almost anything MS from one place (for example the WDK can be obtained without going through MSDN but it requires seperate signup to do so)
Yes MSDN is nice to have but it is not in any way a requirement for developing and selling apps on windows.
for example: if i sell you a gun, i am not responsible for how you use that gun
If you go round knowingly selling guns to street gangs who it is reasonable to suspect are using them for criminal purposes imo you deserve a share of the blame for what is done with those guns.
Similarlly if you go arround selling big military weapons to dictatorships who it is reasonable to suspect will use them for agressive purposes then imo you deserve a share of the blame for what is done with them.
the big flac archive I grabbed from TPB ( http://thepiratebay.org/tor/4061815/Nine_Inch_Nails_-_Ghosts_I-IV_%5B2008_FLAC_Lossless%5D ) contains a PDF full of cover art which includes the statement
"This album is licensed under a Creative Commons
Attribution-Noncommercial Share Alike license.
More information: www.creativecommons.org"
someone posted a link to one on the other /. story about this release
http://thepiratebay.org/tor/4061815/Nine_Inch_Nails_-_Ghosts_I-IV_%5B2008_FLAC_Lossless%5D
http://slashdot.org/comments.pl?sid=476150&threshold=-1&commentsort=0&mode=thread&cid=22652156
plenty of seeds too, over four times as many seeds as leachers right now. It took me a while to download last night (i'm seeding now) partly because I have a shitty ISP and partly because I cba setting up a port forward.
Then why license the whole album under creative commons thereby opening the floodgates for legal torrenting of the whole damn thing? Doesn't that seem at all contradictory to you?
Not really, it sounds like a statement of not wanting to criminalise fans who share his music while still encouraging fans to pay for the music.
you can easilly set up a tracker to require authentication and it wouldn't be too hard to set up a system which generated authentication keys on the fly and put some limits on the use of one key.
But if you know the IP of a machine in the swarm and that machine has finished downloading and become a seed then there is nothing the tracker can do to stop you downloading from them. There are also peer-peer tracking systems though I belive most clients will respect requests from the tracker not to use them.
looks like your post on /. has caused the leaches counter to shoot up again and a few peers have dropped off. 318:180 (seed:leacher) is what my client reports now and it's going to be downloading all night.
It doesn't matter, because the only thing that matters is the positive contribution he made by founding Wikipedia and his later life or his personal details don't effect that.
It DOES matter because the wikimedia foundation (who own/run wikipedia along with various other related sites) has not at this time made the transition from a single person dominated organisation (iirc there is a board of directors but it is a 5 member board two of which are jimbo and his cronies 2 of which are elected effectively giving wales absoloute power over the project) to an organisation with a broader power base.
Yes you can take a copy the main content easilly enough but you can't get the images so easilly (and if you could they would take up a huge ammount of storage) and you will either have to accept changes from wikipedia without much oversight or fork (and if you fork your fork will go stale).