the number of decimal places is arbitrary since we could always sell things to 3 decimal places if we really wanted (i.e. - $2.848 - of course, we would need new coins to do so).
Maybe you don't buy gasoline in the US but gas is sold to three decimal places. e.g. $2.059 in my neck of the woods(~15 cent jump in three days).
Define "crime". If you murder someone and post the video online, then I believe it's OK for Google to provide information to authorities, of course.
There is part of rub; what is a crime? Only the law makers & courts of that country can define what is illegal.
But in the case I mentioned I would expect Google to do some screening on what is exactly defined as a "crime". If the law says it's a felony for you to say "I believe marijuana should be legalized", then I don't think Google should comply with that.
And there is the other part of rub; who is fit to judge a country's laws? Your statement implies you are in favor of multinational corporations of having the right to decide what laws are just. That leads to the path of multinational corporations becoming the next step in global governance. Which not I'm sure is such a good idea.
The code of conduct I think is Google's & et all's attempt to find a solution to how to act in a global marketplace with multiple conflicting laws they must abide by and might not agree with(e.g. chinese bloggers). The UN's Universal Declaration of Human Rights is probably a good place to start.
Basically, I believe freedom of speech is meaningless if you only are allowed to state things that everyone agrees about.
I agree. For an interesting US based freedom of speech case checkout Bong Hits 4 Jesus
Google is taking the opposite way, the dictator's freedom, where you are only allowed to say things that the government likes.
That in a nutshell is the problem. To access the dictator's marketplace, the entity(e.g. Google) has to abide by the dictator's rules.
One recent example: they handed over IP addresses of people who participated in an Orkut community called "Eu sei dirigir bêbado" ("I know how to drive drunk"). The reason was that this was, allegedly, "apology of crime", a felony according to the draconian "liberty of expression" laws in Brazil.
Curious. So, you would be against say myspace.com providing information to the authorities when someone posts about their crimes(e.g. randomly shooting people with a paint-ball gun from a moving car)
If you communicate in a public forum about a crime you have committed(or planning to commit), you can expect the local law enforcement to use that speech against you. Yes/No?
Please note that be convicted is another matter altogether.
He's stated he wasn't a programmer, and that his job had nothing to do with programming, but (on his own time) he threw together some quick & dirty utilities to make his life easier, and willingly shared those utilities with his co-workers. That's the definition of a resourceful, generous employee.
Agreed. But when he got huffy about not getting paid, then the generous adjective no longer applies.
You seem to think that every program is used in a 'production' environment.
If a program is used by an employee to accomplish their job, then that program is being used in a production capacity. You have another definition?
In fact, the sort of utility he's talking about is a special-purpose thing that makes doing a difficult/tedious/repetitive part of the job easier/faster/quicker.
Oh, so only the general-purpose things that don't make doing a difficult/tedious/repetitive part of the job easier/faster/quicker are production programs./did you see the memo on the new TPS coversheets?
As an example, my wife is an insurance adjuster. To make her life easier, she spent a couple hours one weekend putting together some spreadsheets designed to make tracking of insurance payouts vs. policy limits easier and less error-prone. She did it to make her life easier, and willingly shared the spreadsheets with any of her coworkers who were interested. If she leaves, it's *not* her responsibility to make sure that said spreadsheets are kept around.
Agreed, it is not her responsibility to make sure that the spreadsheets are kept around. But I'll guess her employer has a location that she could copy the spreadsheets to so they get backed up. i.e. She could(and should) ask that the spreadsheet be backed up.
It is also likely that in the act of sharing the spreadsheet with her co-workers it already got backed up. If she emailed it to them, the email system back-ups will have a copy of it. New Federal laws require employers to keep a copies of all emails for several years.
Would your wife actively try to keep the spreadsheet from being backed up? The parent poster actively avoided backing up his tools.
Do you think the spreadsheet is being used in production and should be backed up?
In this post you say he appears to be lazy and dishonest
Wasn't me. Please check your link.
The exact wording of your accusation is as quoted above "you tried to extort them for something they had already paid for".
I said no such thing. Please apologize for the false accusation.
Alternatively: he made a generous decision (deciding to write a work related tool in his free time) and to complement his first generous decision, he decided to leave the tools available for use by his ex-employer. However, when his ex-employer deleted the tools, he set the limit at going in at no charge to rebuild them and offered to work on contract to replace them. This is good behaviour!
You have an interesting moral compass. You, yourself would be comfortable doing what he did?
My problem(as stated is several other replies) is that he knowingly put a tool used by others in a location that he knew wouldn't be backed up and most likely deleted upon his termination(his word). This is disrespectful of those that are left there(fellow employees).
Yes, there is onus on the IT dept to take a snap-shot of his workstation before wiping it.
Yes, if his former employer wants him to re-create the tool(s) the employer will have to pay for his time. But again the situation where the tools would need to be re-created was created thru his actions of keeping his tools from being backed up. I view the act of intentionally keeping the tools from being backed up as acting with malice.
The "but he wasn't responsible for XXXX" reasoning doesn't work for me personally. Regardless of who is responsible for XXXX, the author of the tool had it within his power to see that the tool wasn't deleted. He decided not to.
I worked state gov once, and wrote some very useful code, useful to me and handy for co-workers. But I was never hired to write it,nor was I paid for writing it
I see no reason I should provide MY tools to another though as a curtesy you can borrow my 5/16ths. When I leave, the toolbox goes with me.
Sounds like he's a little miffed about not getting paid.
and he didn't screw them.
Oh, really?
When I left, I left the code in a file location that was not archived, was not backed up, and was not saved. Still available, still used and everyone was happy till... 30 days later it went bye bye.
Actually, those files were in my own/usr... directories which in the normal clean-up sweep of terminated employees were wiped.
If a tool is used in production, the author is obligated to document it & put it in a location that is backed up.
In fact, if I were IT for that agency, I'd have been pissed off if he moved something out of his/usr directory to a more permanent location, no matter how important he thought it was.
The tool he wrote was being used in a production environment by multiple users. Since the tool disappeared when they wiped his workstation, this implies he had his/usr(or at least/usr/bin) directory shared/exported out. You prefer that over a standard shared directory of tools?
Since it did get deleted, and they wanted him to recreate the work, they're obligated to pay for it, as they're no longer on his payroll.
Yes, since he is no longer on his former employer payroll he should be paid for any time he spending helping his former employer. However the situation arose because he created it by not putting the tool in a location that would be backed up. He wasn't happy with his employer and as a parting shot he purposely left a tool he wrote, that was being used in production, in a location he knew it would be deleted.
Yes, the IT dept is also responsible because they failed to take a snap-shot of his workstation. That is were the poster took advantage of poor IT practices to create the situation were the former employer would be calling him for help.
The poster's underlaying intent wasn't positive, he wanted to cause his former employer some pain.
I don't see why it's disrespectful of him to not ensure availability of something to people who neither paid to have it nor are owed anything by him.
The reason he didn't get paid for writing the tool was because he decided to write the tool in his own free time. He could have just as easily wrote the tool was he was at work and then would have been paid for his efforts. Pissing & moaning about not getting paid when it was his decision to not get paid doesn't get any sympathy from me.
Standard IT practices dictate that all software/tools are documented and backed up. He again decided not to follow that and kept the tools in a location that weren't backed up and he knew would be wiped after he left.
It is disrespectful to those that follow after him because the tool(s) were used in production and he didn't document them or keep them in a location that would be backed up.
You appear to be in error. You speak of karma, you might consider how your karma is affected by these apparently false accusations. An apology is in order.
Basically he made a bad decision(deciding to write a work related tool in his free time) and to get "revenge" for his first poor decision, he decided to not to backup his tools knowing his employer will eventually lose them and that will provide him an opportunity to get paid to re-create the tool. This is good behavior?
The software was written ON MY OWN TIME as a tool to help me do my own job which had absolutely nothing to do with programming.
It wasn't clear that you wrote the tools on your own time for use at your job. It is safe to guess that you freely chose to use your free time to write the software in question? If you chose to write the software in your free time, then you can't really fault the employer for not paying you. You chose not to be paid by writing the software in your free time.
If the software you wrote was used in production, then standard IT practices dictate that the tool/software is to be documented and backed up. You knew your workstation won't be backed up and likely wiped when you left. You took advantage of poor IT practices with the intent of screwing your employeer. Which is kinda funny because you said you worked for a state agency, so in affect by screwing your employer you end up screwing yourself; providing you still live in the same state.
Software tools are different than physical tools. You can leave a copy of your software tools at a location without depriving yourself of those tools.
Every IT job I have had, had that ever so magical cause "and other duties as needed".
Yup - And that ends the second I (or they) terminate my employment. Which sounds pretty much like the situations to which you replied... People wrote small programs for their own use, which others found useful. Their employers' had the chance to retain that work, and blindly did not do so. I fail to see the problem.
Aye, no problem. The only rub is if the software author "hides" the tool/software in a location know not to be backed up; i.e. taking advantage of poor IT practices. Regardless my statement was answering the "I was never paid to write X software" claim of the parent.
I can understanding not having loyalty to an employer but one should at least some respect for those that will come after you and/or left there.
"Respect" does not equal "volunteer work", into which category anything I do for the company after I stop drawing a paycheck would fall. If someone has a 30 second question, I'd probably chat, just for the sake of basic human decency. If they wanted me to recreate a few hours' of work lost due to their own negligence, well, they damned well better expect an invoice for my time.
Agreed, "Respect" doesn't mean "volunteer work". Respect for those that follow means keeping tools in locations that are backed up and documenting how one set things up and/or how-to use tools. Look at a Linux Wiki(e.g. Gentoo Wiki) and imagine something like that for your IT dept.
He was paid to do his job and in effort to make his job easier he wrote some software while at work to that end. Who is responsible for making sure that software is backed up is the real question.
Not really - Let me pose a similar but non-backup-related concept, and see what you think:
Not really? Not really... the real question isn't who is responsible for what is backed up? Not really... he wasn't paid? I'm not sure what you are disagreeing with.
In my job, I write a lot of small one-off tools to automate common tasks I perform. I've shared them freely with my coworkers, who use them once then promptly forget about it, until they need to perform a similar task... At which point they come to me asking for a quick refresher in how to use tool-X.
I'm familiar with that. But I dislike being bothered to read the manual to someone. My solution was to document the tool. Yes, for quickie scripts the "man page" ends up taking more time to write than the tool but in the end the tool remains useful after you have moved on. (respect for those that follow) I have found a quick wiki page on the tool to be the easiest for me and others.
As I firmly believe in backups, they would have no trouble finding various version of my tools scattered across both the network and backup DVDs of my own system. Including source code (though keep in mind I wrote these as quick-n-dirties for personal use, so good luck reading the source code, and goddess help you if you trust that I did any input validation whatsoever).
Two words -> Version Control. Use the existing in-house version control system or set-up your own preferably with a web interface. This keeps the tools in a central location(ease of backups) and provides continuity after you have moved on.
If I left my job, by your stance, would I have to write them a manual, on my own time, to keep using the tools I wrote for my own convenience?
No, you should have written the manual while you were there and getting paid. Part of writing a tool that is used in production is documenting that tool. That part of the process is typically forgotten about. Think about those that will follow after you. Then won't be asked to write a manual after you have moved on.
I worked state gov once, and wrote some very useful code, useful to me and handy for co-workers. But I was never hired to write it,nor was I paid for writing it.
Every IT job I have had, had that ever so magical cause "and other duties as needed". Heck, even my non-IT jobs have had something similar to that, if not that exact phrase. One could argue writing utilities/software to help do your job falls under that cause.
It sounds like the software in question was useful to more than the author(the handy to co-workers bit). Maybe the parent is bitter that the tools he wrote weren't recognized in his reviews, so he is taking it that he wasn't paid for them./shrug
He was paid to do his job and in effort to make his job easier he wrote some software while at work to that end. Who is responsible for making sure that software is backed up is the real question.
Taking advantage of known poor IT practices is another matter; e.g. putting the files in an out of the way location, knowing they won't be backed up. And that it only took 30 days before the files disappeared is a little odd. How did the author keep his software from disappearing?
I can understanding not having loyalty to an employer but one should at least some respect for those that will come after you and/or left there./shrug Karma will get him in the end.
Yeah, I've used the cross-over cable solution before... it does work well.
My main frontend only has the three pci slots and they're filled with capture cards. So I'm stuck with the on-board 100mbps nic. Backend has a gigabit nic on-board and there is one other dedicated mythbox as well as a few more workstations with myth installed. The cheap-o gigabit switch works well enough.
Just to add a little to the other reply - your mythtv stream is only a few megabits/sec. Certainly not 700Mb/s!
True, enough... I did state that the network link is only 100mbps. Recording three HD streams uses about 6.5 megabytes per second of disk & network. Three streams is about 24GB of disk space an hour.
For a better point of reference the Colts vs Raven game yesterday was broadcast in 1080i. The recording schedule is configured to run late 45 minutes, I ended up with 4 hours 15 minutes worth of video. That file is 38GB in size.
Aye, my MythTV backend with the disk dump has two 320GB 7200 RPM 16MB Cache SATA 3.0Gb/s Hard Drives in a RAID 0 array. The frontend has three HDTV capture cards(two HD-5500 & one HD-3000). A Lowly 100mbps full-duplex network link between the two boxes.
I'm able to record three HD streams at once via nfs(nfs ver3, ver4 cause kernel panic under that load). Playback of one of the three streams while it is being recorded isn't do-able but recording two and watching an earlier(yet to be transcoded) one all at the same time works.
An hour of 1080i is a little shy of 8.5GB. The network link is the bottleneck in my setup, the disk array handles the task without a problem.
I do something similar. I use businessname@subdomain.mydomain.com. When I start receiving spam at that address I setup an alias to automatically forward it to spam@uce.gov. I do like your idea of adding a date to the name, I'll probably start doing that.
I can't see handing out a new email address every year... just too much of PITA, especially with the older relatives and ones I only hear from a couple times a year.
Yes, and I've build a HTPC. However, you still have an issue getting DVD's onto it. (Of course, I can just stick in the DVD to watch it, but then it can't act as a server).
Is it that they didn't put all tracks on one CD because Nellie may have wanted two CDs in order to fulfill her contract faster?
Yes
Would Sony want 1 CD with 18 tracks or 2 separate albums with 9 tracks each?
Sony wants 1 CD(album) because then Nellie still owes them another album
If the artist(e.g. nellie) has a contract with the distributor(e.g. sony) to produce two albums, the artist can only get out of the contract by producing two albums or having someone make the distributor an offer they can't refuse ala The Godfather.
The grey area is how many songs make an album. By saying those 18 songs are two albums, she has fulfilled her contract obligations and can now distribute her new albums herself or sign with another distributor.
When musicians sign with a label, their work is generally "work for hire" meaning they don't retain the copyrights to the work they produced for the label. The label(e.g. sony) get the copyright. If the artist signed a poor contract(e.g. they're paid shit) and become popular, they'll want to get out of their contract.
Relax Francis, it was just a little friendly ribbing. As for surfing for porn in the 80s, it was an option... you just needed to know where to look and what tools to use. Your middle & high school experience was not universal.:)
Almost no one had ever heard of www.anything.com when I started college (1990). Surfing for porn wasn't an option when I was in middle or high school, though I do have a few fond memories of strip poker for the C64.;-)
Noob;) There was plenty of porn to be found before http hit the 'net(hint: ftp & gopher). There were also plenty of bbs with porn. There was also porn for apple II but dad's stack of penthouse & playboy were better.:)
But you're right games&porn were my moviation to "learn computers" and I see that trend continuing in others around me. e.g. neighbor asking about porn sites and how to cover his tracks. neighborhood kids seem to be more interested game consoles(xbox, etc) than online games./shrug
And as soon as someone cracks the PGP client app then PGP is useless to.
The thing is, it's much easier said than done.
Don't be naive.
Huh?
The PGP client app is just a program that does some math. The math is public key encryption. "Cracking" a PGP client app doesn't invalidate the underlaying math but could comprimse the security of those using the cracked app. Attacking an app doesn't always mean you're attacking the math. For example the Buffer overflow in PGP Outlook Encryption Plug-In
You might be interested in Torque. It is an open-source engine but not free.
There is a fair collection of how-toarticles and one author has put together an "add-on" product for the engine.
I've played with the Torque engine a bit and it's interesting. The thing I like the most is the server-side can be linux and the client side can be both windows & linux. I haven't played with the MyDreamRPG products, so I can't comment on them but they look interesting.
Slashdot Mirror
And for an added bonus the link to Wal-Mart's video store within the story is broken.
Article link
Wal-Mart Video Store note: the site renders horribly in Mozilla & Firefox... at least for me.
the number of decimal places is arbitrary since we could always sell things to 3 decimal places if we really wanted (i.e. - $2.848 - of course, we would need new coins to do so).
Maybe you don't buy gasoline in the US but gas is sold to three decimal places. e.g. $2.059 in my neck of the woods(~15 cent jump in three days).
There is part of rub; what is a crime? Only the law makers & courts of that country can define what is illegal.
And there is the other part of rub; who is fit to judge a country's laws? Your statement implies you are in favor of multinational corporations of having the right to decide what laws are just. That leads to the path of multinational corporations becoming the next step in global governance. Which not I'm sure is such a good idea.
The code of conduct I think is Google's & et all's attempt to find a solution to how to act in a global marketplace with multiple conflicting laws they must abide by and might not agree with(e.g. chinese bloggers). The UN's Universal Declaration of Human Rights is probably a good place to start.
I agree. For an interesting US based freedom of speech case checkout Bong Hits 4 Jesus
That in a nutshell is the problem. To access the dictator's marketplace, the entity(e.g. Google) has to abide by the dictator's rules.
Curious. So, you would be against say myspace.com providing information to the authorities when someone posts about their crimes(e.g. randomly shooting people with a paint-ball gun from a moving car)
If you communicate in a public forum about a crime you have committed(or planning to commit), you can expect the local law enforcement to use that speech against you. Yes/No?
Please note that be convicted is another matter altogether.
"I am the devil and I am here to do the devil's work." -- Charles "Tex" Watson
But you are right that generally people don't see their actions as being evil.
Agreed. But when he got huffy about not getting paid, then the generous adjective no longer applies.
If a program is used by an employee to accomplish their job, then that program is being used in a production capacity. You have another definition?
Oh, so only the general-purpose things that don't make doing a difficult/tedious/repetitive part of the job easier/faster/quicker are production programs.
Agreed, it is not her responsibility to make sure that the spreadsheets are kept around. But I'll guess her employer has a location that she could copy the spreadsheets to so they get backed up. i.e. She could(and should) ask that the spreadsheet be backed up.
It is also likely that in the act of sharing the spreadsheet with her co-workers it already got backed up. If she emailed it to them, the email system back-ups will have a copy of it. New Federal laws require employers to keep a copies of all emails for several years.
Would your wife actively try to keep the spreadsheet from being backed up? The parent poster actively avoided backing up his tools.
Do you think the spreadsheet is being used in production and should be backed up?
Wasn't me. Please check your link.
I said no such thing. Please apologize for the false accusation.
You have an interesting moral compass. You, yourself would be comfortable doing what he did?
My problem(as stated is several other replies) is that he knowingly put a tool used by others in a location that he knew wouldn't be backed up and most likely deleted upon his termination(his word). This is disrespectful of those that are left there(fellow employees).
Yes, there is onus on the IT dept to take a snap-shot of his workstation before wiping it.
Yes, if his former employer wants him to re-create the tool(s) the employer will have to pay for his time. But again the situation where the tools would need to be re-created was created thru his actions of keeping his tools from being backed up. I view the act of intentionally keeping the tools from being backed up as acting with malice.
The "but he wasn't responsible for XXXX" reasoning doesn't work for me personally. Regardless of who is responsible for XXXX, the author of the tool had it within his power to see that the tool wasn't deleted. He decided not to.
Sounds like he's a little miffed about not getting paid.
Oh, really?
If a tool is used in production, the author is obligated to document it & put it in a location that is backed up.
The tool he wrote was being used in a production environment by multiple users. Since the tool disappeared when they wiped his workstation, this implies he had his
Yes, since he is no longer on his former employer payroll he should be paid for any time he spending helping his former employer. However the situation arose because he created it by not putting the tool in a location that would be backed up. He wasn't happy with his employer and as a parting shot he purposely left a tool he wrote, that was being used in production, in a location he knew it would be deleted.
Yes, the IT dept is also responsible because they failed to take a snap-shot of his workstation. That is were the poster took advantage of poor IT practices to create the situation were the former employer would be calling him for help.
The poster's underlaying intent wasn't positive, he wanted to cause his former employer some pain.
The reason he didn't get paid for writing the tool was because he decided to write the tool in his own free time. He could have just as easily wrote the tool was he was at work and then would have been paid for his efforts. Pissing & moaning about not getting paid when it was his decision to not get paid doesn't get any sympathy from me.
Standard IT practices dictate that all software/tools are documented and backed up. He again decided not to follow that and kept the tools in a location that weren't backed up and he knew would be wiped after he left.
It is disrespectful to those that follow after him because the tool(s) were used in production and he didn't document them or keep them in a location that would be backed up.
Basically he made a bad decision(deciding to write a work related tool in his free time) and to get "revenge" for his first poor decision, he decided to not to backup his tools knowing his employer will eventually lose them and that will provide him an opportunity to get paid to re-create the tool. This is good behavior?
I fail to see how I am in error. Please explain.
It wasn't clear that you wrote the tools on your own time for use at your job. It is safe to guess that you freely chose to use your free time to write the software in question? If you chose to write the software in your free time, then you can't really fault the employer for not paying you. You chose not to be paid by writing the software in your free time.
If the software you wrote was used in production, then standard IT practices dictate that the tool/software is to be documented and backed up. You knew your workstation won't be backed up and likely wiped when you left. You took advantage of poor IT practices with the intent of screwing your employeer. Which is kinda funny because you said you worked for a state agency, so in affect by screwing your employer you end up screwing yourself; providing you still live in the same state.
Software tools are different than physical tools. You can leave a copy of your software tools at a location without depriving yourself of those tools.
Aye, no problem. The only rub is if the software author "hides" the tool/software in a location know not to be backed up; i.e. taking advantage of poor IT practices. Regardless my statement was answering the "I was never paid to write X software" claim of the parent.
Agreed, "Respect" doesn't mean "volunteer work". Respect for those that follow means keeping tools in locations that are backed up and documenting how one set things up and/or how-to use tools. Look at a Linux Wiki(e.g. Gentoo Wiki) and imagine something like that for your IT dept.
Not really? Not really... the real question isn't who is responsible for what is backed up? Not really... he wasn't paid? I'm not sure what you are disagreeing with.
I'm familiar with that. But I dislike being bothered to read the manual to someone. My solution was to document the tool. Yes, for quickie scripts the "man page" ends up taking more time to write than the tool but in the end the tool remains useful after you have moved on. (respect for those that follow) I have found a quick wiki page on the tool to be the easiest for me and others.
Two words -> Version Control. Use the existing in-house version control system or set-up your own preferably with a web interface. This keeps the tools in a central location(ease of backups) and provides continuity after you have moved on.
No, you should have written the manual while you were there and getting paid. Part of writing a tool that is used in production is documenting that tool. That part of the process is typically forgotten about. Think about those that will follow after you. Then won't be asked to write a manual after you have moved on.
Every IT job I have had, had that ever so magical cause "and other duties as needed". Heck, even my non-IT jobs have had something similar to that, if not that exact phrase. One could argue writing utilities/software to help do your job falls under that cause.
It sounds like the software in question was useful to more than the author(the handy to co-workers bit). Maybe the parent is bitter that the tools he wrote weren't recognized in his reviews, so he is taking it that he wasn't paid for them.
He was paid to do his job and in effort to make his job easier he wrote some software while at work to that end. Who is responsible for making sure that software is backed up is the real question.
Taking advantage of known poor IT practices is another matter; e.g. putting the files in an out of the way location, knowing they won't be backed up. And that it only took 30 days before the files disappeared is a little odd. How did the author keep his software from disappearing?
I can understanding not having loyalty to an employer but one should at least some respect for those that will come after you and/or left there.
Yeah, I've used the cross-over cable solution before... it does work well.
My main frontend only has the three pci slots and they're filled with capture cards. So I'm stuck with the on-board 100mbps nic. Backend has a gigabit nic on-board and there is one other dedicated mythbox as well as a few more workstations with myth installed. The cheap-o gigabit switch works well enough.
True, enough... I did state that the network link is only 100mbps. Recording three HD streams uses about 6.5 megabytes per second of disk & network. Three streams is about 24GB of disk space an hour.
For a better point of reference the Colts vs Raven game yesterday was broadcast in 1080i. The recording schedule is configured to run late 45 minutes, I ended up with 4 hours 15 minutes worth of video. That file is 38GB in size.
Aye, my MythTV backend with the disk dump has two 320GB 7200 RPM 16MB Cache SATA 3.0Gb/s Hard Drives in a RAID 0 array. The frontend has three HDTV capture cards(two HD-5500 & one HD-3000). A Lowly 100mbps full-duplex network link between the two boxes.
I'm able to record three HD streams at once via nfs(nfs ver3, ver4 cause kernel panic under that load). Playback of one of the three streams while it is being recorded isn't do-able but recording two and watching an earlier(yet to be transcoded) one all at the same time works.
An hour of 1080i is a little shy of 8.5GB. The network link is the bottleneck in my setup, the disk array handles the task without a problem.
Amen, Brother!
Mod parent up.
I do something similar. I use businessname@subdomain.mydomain.com. When I start receiving spam at that address I setup an alias to automatically forward it to spam@uce.gov. I do like your idea of adding a date to the name, I'll probably start doing that.
I can't see handing out a new email address every year... just too much of PITA, especially with the older relatives and ones I only hear from a couple times a year.
MythTV has an option to import DVDs & CDs.
Yes
Sony wants 1 CD(album) because then Nellie still owes them another album
If the artist(e.g. nellie) has a contract with the distributor(e.g. sony) to produce two albums, the artist can only get out of the contract by producing two albums or having someone make the distributor an offer they can't refuse ala The Godfather.
The grey area is how many songs make an album. By saying those 18 songs are two albums, she has fulfilled her contract obligations and can now distribute her new albums herself or sign with another distributor.
When musicians sign with a label, their work is generally "work for hire" meaning they don't retain the copyrights to the work they produced for the label. The label(e.g. sony) get the copyright. If the artist signed a poor contract(e.g. they're paid shit) and become popular, they'll want to get out of their contract.
The problem with irradiation of veggies & fruits is the high-energy radition tends to ruin the flavor and/or flesh of the food good.
Relax Francis, it was just a little friendly ribbing. As for surfing for porn in the 80s, it was an option... you just needed to know where to look and what tools to use. Your middle & high school experience was not universal. :)
Noob
But you're right games&porn were my moviation to "learn computers" and I see that trend continuing in others around me. e.g. neighbor asking about porn sites and how to cover his tracks. neighborhood kids seem to be more interested game consoles(xbox, etc) than online games.
Ok, try Endless Ages if you want MMORPG + FPS shooting.
Huh?
The PGP client app is just a program that does some math. The math is public key encryption. "Cracking" a PGP client app doesn't invalidate the underlaying math but could comprimse the security of those using the cracked app. Attacking an app doesn't always mean you're attacking the math. For example the Buffer overflow in PGP Outlook Encryption Plug-In
You might be interested in Torque. It is an open-source engine but not free.
There is a fair collection of how-to articles and one author has put together an "add-on" product for the engine.
I've played with the Torque engine a bit and it's interesting. The thing I like the most is the server-side can be linux and the client side can be both windows & linux. I haven't played with the MyDreamRPG products, so I can't comment on them but they look interesting.