Okay, but say that you're in Michigan. The age of consent is 16 (I believe). You can go to Ontario and have sex with a 14 year old, as long as you a) are not in a position of authority over said minor, b) don't do her in the butt, and c) don't bring her into Michigan.
If a neighbouring state has a restriction of 17 or 18, you cannot bring her into Michigan for the purposes of sex, otherwise you are transporting a minor across state lines for the purpose of sex (or something like that), but if she is visiting relatives, then things are different.
To wrap it up, which is more exploitive? Having sex with someone under 18, or photographing it? I don't want to get into a big philosophical debate, but the main point that I'm trying to make, is that if you're going to sue a company that is essentially worldwide, you might want to better ensure that the rules are comparable across the board, or try to make them moreso. It's hard to prevent child pornography if it's only child pornography in one little hamlet. You can filter and control it all you want, but you'll never eliminate it.
I consider Windows Update as an administration task, so I use the administrator account.
If I need a quick fix, runas, spawn an MMC or explorer link, and do what I need to do. Albeit, that's in an enterprise setting. I don't run XP pro at home, and just have an isolated XP home laptop which I run everything as an admin user anyway.
Terribly sorry, I got to the part that said "More than a month after St. Cloud launched what analysts say is the country's first free citywide Wi-Fi network, Lusardi and others in this 28,000-person Orlando suburb are still paying to use their own Internet service providers as dead spots and weak signals keep some residents offline and force engineers to retool the free system." and thought, "Hmm, more than a month, that can't possibly be 24 months."
After reading the article, I found out that it "... launched the network on a trial basis in May 2004 in a new division of town to help give businesses an incentive to relocate. After further exploring the benefits, officials decided to expand it citywide." Which means that it worked well in the trial, and they had issues as they expanded and added users.
Now let's dissect all of that. May 2004, St. Cloud launches test bed. Works. Continue to run testbed. Sometime between 01/01/06 and 03/24/06, after having to go through committees, raise funding, and implementation of the full scale wi-fi network, they release it to the public. People complain (Which is their nature, and some of them their sole function) that they can't get wireless coverage, or that the access points are maxxed out. When they do connect, it's slow. Some lady at the beach, which has really decent line of sight when compared to, say an apartment building, can use it.
So, after RTFA, I think that I'm still right. But I could be wrong about that. It's been known to happen,
Also, using XML mining and standardized forms, a wizard could be greated to generate conglomerate reports from other reports using transforms and data-mining/screen scraping techniques. Ex. Grab pie chart from April 05 and place on current page. Using the repository as a data source, if the data changes in April 05, the pie chart would be automagically updated on the new report. Which could update your webpage, or your PDA, or whatever.
So, the whole thing would be like SVN on steroids, with a nice GUI interface.
Management tools: I.E. Ability to finalize documents, remove documents from the repository, control access to the documents, display revisions and users who revised, accessed, etc.
Yes, but more than that. CVS/subversion/WebDav/whatever can be the ultimate backend, but there needs to be better integration with programs like openoffice. If you have to use a third party program to save the document into the repository, then nobody is going to use it. Put it in the options as "Save to server" and then people will use it.
Open Document Format (odf, or.odf) is... doomed to failure, unless we make it useful.
As it stands right now, ODF is nothing more than a rallying cry. The geeks of the world are tired of being held a slave to business demands. They don't want to have to support Microsoft Word, they want more flexibility, more control, and more fun. As of right now, they don't have the tools to do any of it. The tools are easy enough to build, given the right motivation, but what tools need to be created? And more importantly, how will they interact with each other?
At the top of the list, I see the need for an enterprise-grade versioning and repository server. One that is connectable from anywhere in the enterprise, with flexible security and controls that integrates into the enterprise architecture. That might seem like a lot of buzzwords jammed into one little sentence, so I'll expand on that. Instead of saving your document to a file, it will save it into a server. The server will save the document, and save subsequent changes. It will have the ability to give you the old version if you've bunged up completely. It will allow you to take the file home, work on it, and bring it back to the enterprise. If Bob works on the file, it will branch that file, and keep track of the changes that happen. Finally it will allow you to merge the branches, so that you don't have a million disparate file revisions which have no resemblance to the original file. Support for this should be built into the program that you use to edit the file, without a need to call an external program.
Next, there should be more leveraging of XML translations. Using the aforementioned server as a data source, data should be able to be pulled and new documents created, using an XML translation. Think of the high level manager that wants a report summarizing all of the departments monthly financials. Instead of having someone make the report every month, the report is auto-generated. Any changes in any of the source files is automatically mirrored into the new report. Translations could be leveraged so that all the reports could be (more or less) viewed in any web browser or e-mail client. Statistics and graphs could be added to the company's website, and translations of translations would work the same.
After that, there needs to be a wizard to do all of this. Now, I know that this is going to sound very MS Access-ish, but a business would have a standard template for a great deal of its memos, spreadsheets, faxes, and everything inbetween. If there's one thing that a company is good at, it's creating bureaucracy, and this is a natural extension of that. The wizards would use that structure and create the needed transforms. The suits could point and click until their hearts content, generating millions upon millions of reports and feeling like God on the third day. Us geeks would have already purchased stock in toner companies, so things would be good for us, even though we already realize that the documents are, with the right transforms, completely portable, and we can read the latest financial data from our PDA's on the bog.
Lastly, there needs to be management tools, from server to desktop. Auditing software, role management, whatever we need. Those are the tools that the open source community excel at. These would all be built on an as-needed basis, and they would be quick in coming. Once adoption takes off, I'm certain that other software will leverage the power and flexibility of the system, and be able to use it as a data source as well, providing even more reason why opendocument would succeed, but only if we actually make it useful for what it is and what it's supposed to be: A data source as well as a presentation engine.
If we don't, however, it will fall by the wayside, used only by geeks and the technical elite.
Slashdot Mirror
A little from coulmn A, a little from column B. --Abe Simpson
What's the downside?
Okay, but say that you're in Michigan. The age of consent is 16 (I believe). You can go to Ontario and have sex with a 14 year old, as long as you a) are not in a position of authority over said minor, b) don't do her in the butt, and c) don't bring her into Michigan.
If a neighbouring state has a restriction of 17 or 18, you cannot bring her into Michigan for the purposes of sex, otherwise you are transporting a minor across state lines for the purpose of sex (or something like that), but if she is visiting relatives, then things are different.
To wrap it up, which is more exploitive? Having sex with someone under 18, or photographing it? I don't want to get into a big philosophical debate, but the main point that I'm trying to make, is that if you're going to sue a company that is essentially worldwide, you might want to better ensure that the rules are comparable across the board, or try to make them moreso. It's hard to prevent child pornography if it's only child pornography in one little hamlet. You can filter and control it all you want, but you'll never eliminate it.
I think that you have one too many words in the subject line. Try taking out 'knee' and see what happens.
Why don't they go after the purveyors of said pornography?
Better yet, why doesn't every country get together and decide what a child is? Or how about every U.S. state?
I consider Windows Update as an administration task, so I use the administrator account.
If I need a quick fix, runas, spawn an MMC or explorer link, and do what I need to do. Albeit, that's in an enterprise setting. I don't run XP pro at home, and just have an isolated XP home laptop which I run everything as an admin user anyway.
ZDNet, Where Technology meets Business...
And business stabs tech in the face!
runas command not good enough? I haven't had any problems with it.
The one who makes the laws.
But one that will help you fix your product, not just tell you what they like and don't like. And they'll do tech support for free, too.
And all the girls will have huge boobs.
Put two or three NIC's on this guy, and you can bet that it won't fail. Why should my firewall require a 250 watt PSU?
Nice comeback, NineNine, and a decent way to pimp your site.
Terribly sorry, I got to the part that said "More than a month after St. Cloud launched what analysts say is the country's first free citywide Wi-Fi network, Lusardi and others in this 28,000-person Orlando suburb are still paying to use their own Internet service providers as dead spots and weak signals keep some residents offline and force engineers to retool the free system." and thought, "Hmm, more than a month, that can't possibly be 24 months."
After reading the article, I found out that it "... launched the network on a trial basis in May 2004 in a new division of town to help give businesses an incentive to relocate. After further exploring the benefits, officials decided to expand it citywide." Which means that it worked well in the trial, and they had issues as they expanded and added users.
Now let's dissect all of that. May 2004, St. Cloud launches test bed. Works. Continue to run testbed.
Sometime between 01/01/06 and 03/24/06, after having to go through committees, raise funding, and implementation of the full scale wi-fi network, they release it to the public. People complain (Which is their nature, and some of them their sole function) that they can't get wireless coverage, or that the access points are maxxed out. When they do connect, it's slow. Some lady at the beach, which has really decent line of sight when compared to, say an apartment building, can use it.
So, after RTFA, I think that I'm still right. But I could be wrong about that. It's been known to happen,
I would be suprised if there weren't hiccups in a rollout this large. Give it six months, and then we'll see. Until then, let's all reserve judgement.
Looks promising. Added to my bookmarks.
Also, using XML mining and standardized forms, a wizard could be greated to generate conglomerate reports from other reports using transforms and data-mining/screen scraping techniques. Ex. Grab pie chart from April 05 and place on current page. Using the repository as a data source, if the data changes in April 05, the pie chart would be automagically updated on the new report. Which could update your webpage, or your PDA, or whatever.
So, the whole thing would be like SVN on steroids, with a nice GUI interface.
Management tools: I.E. Ability to finalize documents, remove documents from the repository, control access to the documents, display revisions and users who revised, accessed, etc.
Yes, but more than that. CVS/subversion/WebDav/whatever can be the ultimate backend, but there needs to be better integration with programs like openoffice. If you have to use a third party program to save the document into the repository, then nobody is going to use it. Put it in the options as "Save to server" and then people will use it.
shamelessly stolen from my website:
.odf) is ... doomed to failure, unless we make it useful.
Open Document Format (odf, or
As it stands right now, ODF is nothing more than a rallying cry. The geeks of the world are tired of being held a slave to business demands. They don't want to have to support Microsoft Word, they want more flexibility, more control, and more fun. As of right now, they don't have the tools to do any of it. The tools are easy enough to build, given the right motivation, but what tools need to be created? And more importantly, how will they interact with each other?
At the top of the list, I see the need for an enterprise-grade versioning and repository server. One that is connectable from anywhere in the enterprise, with flexible security and controls that integrates into the enterprise architecture. That might seem like a lot of buzzwords jammed into one little sentence, so I'll expand on that. Instead of saving your document to a file, it will save it into a server. The server will save the document, and save subsequent changes. It will have the ability to give you the old version if you've bunged up completely. It will allow you to take the file home, work on it, and bring it back to the enterprise. If Bob works on the file, it will branch that file, and keep track of the changes that happen. Finally it will allow you to merge the branches, so that you don't have a million disparate file revisions which have no resemblance to the original file. Support for this should be built into the program that you use to edit the file, without a need to call an external program.
Next, there should be more leveraging of XML translations. Using the aforementioned server as a data source, data should be able to be pulled and new documents created, using an XML translation. Think of the high level manager that wants a report summarizing all of the departments monthly financials. Instead of having someone make the report every month, the report is auto-generated. Any changes in any of the source files is automatically mirrored into the new report. Translations could be leveraged so that all the reports could be (more or less) viewed in any web browser or e-mail client. Statistics and graphs could be added to the company's website, and translations of translations would work the same.
After that, there needs to be a wizard to do all of this. Now, I know that this is going to sound very MS Access-ish, but a business would have a standard template for a great deal of its memos, spreadsheets, faxes, and everything inbetween. If there's one thing that a company is good at, it's creating bureaucracy, and this is a natural extension of that. The wizards would use that structure and create the needed transforms. The suits could point and click until their hearts content, generating millions upon millions of reports and feeling like God on the third day. Us geeks would have already purchased stock in toner companies, so things would be good for us, even though we already realize that the documents are, with the right transforms, completely portable, and we can read the latest financial data from our PDA's on the bog.
Lastly, there needs to be management tools, from server to desktop. Auditing software, role management, whatever we need. Those are the tools that the open source community excel at. These would all be built on an as-needed basis, and they would be quick in coming. Once adoption takes off, I'm certain that other software will leverage the power and flexibility of the system, and be able to use it as a data source as well, providing even more reason why opendocument would succeed, but only if we actually make it useful for what it is and what it's supposed to be: A data source as well as a presentation engine.
If we don't, however, it will fall by the wayside, used only by geeks and the technical elite.
gave me a quite good impression of what ifolder is about."
neither in the blurb, nor the article, do you actually state what ifolder is or isn't.
Yeah, but if China is cow-towing to this, would they kill the dragon/godson processor for personal PC's?
you can even buy DVD's of movies there before the movie is released in theaters over here (not camcorder-made either) !
Geez, you would think that having the dvd presses in China and paying the workers peanuts would amount to a very tight supply chain.
So I guess that this means that the Dragon/goodson processor is DOA now.
Clinton's leak ruined dresses. Bush's ruined lives.