It would be impossible to keep track of all of the transactions, and anyone implementing this would be hated. Just what we all need, sales tax and now web tax? Perhaps sales tax on subscriptions, i can almost understand, but still.
It could be very useful for sharing of documents when you don't need something so heavy duty as apache or even ncsa. Think about it.
It's the easiest way to share your documents quickly, and if someone adds some code, in a securer manner. Just a quick and dirty module to do file listings on directories and its browsable in your favourite browser. Running Apache for sending a couple of users alone might be a bit much to run and config.
I know of many companies who use apache to serve documents across the net simply because netbios is a nasty overkill. No more NFS/Netbios shares.
The smallest HTTP getter? Possibly snarf. The usage of these two tools is great for information passing. Slap on a small html interpreter; they come in a few hundred kb's for the pilot already.
I mean something for like apache 1.0, linux 0.8.1 and what not. its too much of a scavanger hunt to find some of the old software. they are so much like historic works of art that we can learn from.
No, not being sarcastic. I browsed through the code, and it is kinda impressive. I've never written a compiler before, but I must admit, I see some of the errors I used to make in programming plus some of the inginuity that leads up to today.
An idea for those with disk space, and some unf.. a software repository for old code?
Hey, when I used to collect musical lyrics and put them on my web site.. it was a fetish. By then lyrics.ch had popped up as leo went down. We all remember that.
The fetish part of it is the consistent, driving to go further, with something. In this case, people are trying to drive thier palm's (yes you momo's.. they've been renamed a year or two back) to do more. It's not a geek thing.. it's a motivational thing. I'm a psych minor.
I am not too sure how random patches from random pepole would work. Putting togehter a top notch team of good coders would be 'good'. If they like the ability of a coder, bring him on the team. If he says no, no terrible loss. just so long as there is an authority handling the code.
I'm quite sure some knucklehead out there will hack a client to deaht and mess with their heads a little. Its not as if not using an OSS solution is circumventing hacking of any sorts.
Re:Stop panicing. (whoa.. i lost half a sentence)
on
UCITA is passed
·
· Score: 1
I give you that on the patent example.. it is a bad one at that. Sometimes patents take too long to go through at times.. but that's neither here nor there.
For the sysadmins that need to worry about licensing, the companies, it becomes easier. All of our basic rights, I dunno about that.
The UCITA deregulates product licensing and covers software, multimedia interactive products, data and databases, and the Internet and online information. It further allows vendors to disable software remotely as a means for repossessing products; makes shrinkwrap licensing terms more enforceable; prevents license transfers from one party to another without vendor approval; outlaws reverse engineering; and lets vendors disclaim warranties.
This sounds like the days of putting bad practices with good as the good would not be refused.
But honestly.. the concept of reposession, great idea. Just as if you are using your phone for 'wrong' they can disable it, if you use software for illegal reasons (use), cool. I would like to see how this would be enforced in a fassion that it won't be easily crackable. Encrypt most of the program so that the small encrypted portion decrypts?
Enforcable licensing and reverse engineering. I would hope that GPL would be marked as one. So stop whining if it is. Else, it scares me.
Reverse engineering is bad and its good. Its good in the sense as it doesn't restrict and allows free development on the code. It lets alternatives sprout. Its bad in the sense that how something is done, the concept, can be patentable and this is just a further way of enforcing it. Depends on which side of the line you are on. OSS vs non-OSS.
The upside on tracked licensing, easy transfer of warantee or other promised services. Down side, who the heck is going to be patient enought to use it? Those new to computers. Hell, we already do this with cars, no? This forces the companies to get off their ass and do better tracking of who owns what. This allows a company to even sell its software to different departments or branches with less trouble.
Disclaiming warantees is my big issue. Wouldnt' the disclaiming of warranty considered a form of false adavertising? To say that a warranty claims that we give support with this product but we, the company, say no since we want to?
I guess because I use only OSS, it won't affect me as much. This also is more a fight for the companies over idiot p1r4t3s. But you reap what you sow.
Why not to use sendmail with its local default mailer:
The mbox format it uses is very nice for moving things around, but don't forget, if one acct gets bogged down, it gets blocked due to file locking problems. (if you use the default local mailer). Multiple mail files are nicer. May run out of inodes quicker if you aren't careful.
Its ruleset bogs things down just a bit. Significant if you want to get more than 10k emails out in an hour. (I haven't really benchmarked it yet.) Power versus speed, configurability versus mail handled per sec.
Sendmail is a big program. Qmail is smaller and more modular in the sense. The operating system's process scheduler can handle things better than sendmail's internals. I've had server loads of 10 with higher traffic on a dual 300mhz machine.
Why not to use qpopper
To download your mail, a second copy of your mail spool file gets made so that qpopper can sort out which mail you wish to keep. Effectively you get only 50% of the diskspace.
All users must exist on the system. Bad system administrators (like at my old job) would make home dirs for all users, leaving ftp open at times. Virtual local users kick butt.
There is your reliable software. For network stuff, I would highly recomend FreeBSD, but Linux would do fine. I would recomend qmail as it is both a popper, mta and local mailer. It doesn't give the problems above.
Apparently, these people didn't try better ways of protecting content. What they are equivalently doing is if a person hears a song, you can't hum it to yourself later.
If you really want to protect it better, forcing people to use an account/w ip checking to ensure multiple people aren't using the same one would work better.
It's about time someone defined what is copyright enfringement on the web and how public data is when it is put on the web. I haven't checked the site, but perhaps some sniplet on the bottom explicitly saying that linking is illegal?
I've heard many of the posts you have made and that you are..well.. to say, not of the better opinion. Only reason I haven't read is the articles don't interest me, but this one..
Some ideas for circumventing fake piety, including making Labor Day "Take a Geek Kid To A Restricted Movie Day". This could be an annual event in the ascending Geek Nation.
Sounds catchy, but if you try to make an event of it, you'll have parents forming a mob against their children, as a good parent might not want their children seeing 'inappropriate things'. You are aiming at the wrong people.
How to strike back against the petty harassment of kids trying to see movies like "South Park?, " and the usurping of decisions that should be theirs and their parents?
Um, the parent could take the child to the theatre, buy the ticket and be done. If its the parent's choice, leave it be. Rated 'R' is for a good reason.. or did you miss the funny truth in the South Park movie...
Hit them in their pocketbooks. " If movie chains are going to refuse admission to movies that contain explicit sexual imagery or profanity, MP3 them. Download the movies on ICQ or Hotline, or other sites where they are becoming readily available, just as many kids did with the postponed "Buffy" finale. Watch how quickly they'll lighten up on ticket-booth vigilanteism. Harmless, funny, or overtly rebellious and political movies - "South Park," "American Pie," " Something About Mary" - are not in any sense dangerous to kids over the age of nine, or probably, even under. They are bristling with outsider geek humor and nerd sensibility.
Well isn't this ethical. This also puts fire under mp3's in general (if you could mp3 video). You want action? Petition and boycott. Are you suggesting that when these kids get older, they do other illegal things to get what they want? That IS what you are teaching.. er.. taught them.
They don't really care about the dumb rules they're enforcing.
Great, I didn't know anything you disagree with is dumb. What really scares me here is that you do not see why these rules are good. If you could fight back and prove why there are no good points, maybe more people would listen. But then again, maybe that is why slashdot keeps you as a 'writer'.
Btw, a child doesn't need to have the parent in the movie, just in the theatre.. or so it goes in NYC at the theatres I've gone to... But this isn't an arguement on how things are in which areas, but how your arguement is just terrible.
I believe the saying goes, a picture is worth a thousand words. Depicting something so physical as paper money in terms of bits and what-not seems more forgable than before.
Someone may bring up, ATM's.. but we never have direct access to their programming. With a PDA, we can just dump memory and inspect.
I am not saying there are no advantages, just the danger seems more ominous.
it's refreshing to see yet another compiler for c/c++ out there. I hope people don't start thinking it's an intrusion in the unix world to have a commercial compiler.
it seems to be that it is no longer a commercial environment with little patches of freeness such as linux and *bsd (most of at least) but a free world with some great commercial products out there as well as great fre ones.
Who's to blame a/o are you whining? I have said, for many years, only users and administrators can secure a system/network. Also, if it breaks, then the user is never held responsible, because the user can be blamed for system/network problems, but the administrator must always resolve the problem. In other words never blame the customer-user of a system a/o network - for the designed and/or innate weaknesses and problems of the systems/networks.
That's like blaming the parent who's kid left his key in the front door lock. I would most certainly agree with you if the user or administrator is the person to fix if it's their fault for weak passwords.
A stupid user with the same password on multiple systems or an enterprise/corporate/research network that requires a user to maintain 10 to 20 passwords for day to day work is ?almost? as stupid as the user.
To a point, it's not help-able. NIS and LDAP for example. What about when on the same box, a user has shell, pop and ftp? I'll admit, I do it myself. Call me stupid, but for certain levels of security or differnet groups of services/machines, I use different passwords. There is a level of practicality that a person has to evaluate. Will I be researching passwords for different machines all day long instead of working? For the 30 accounts, in which I can't memorize all the passwords, should I write them down? And if I do, triple encrypt them under one password? But that's bad enough...
I don't think it's so much stupidity as just ignorance. Was it an end to stupidity or an end to not knowing that too much causes cancer?
I can deal with users who are want to argue why is a bad passwd. It is the users who are more educated and tend to forget that the workstation/network they use at work, is not theirs.
It's the responsibility of the company, the department who generates policy in coordination with others within it, to generate company policy regarding their computer policy. It's the office administration to say who gets analog and why. Furthermore, it's the IS fo the company who decides to blow the wistle on people who try to mess with their machines. Of course, this might be just ignorance or just plain old stupidity of different parts of the company.
I see users bring in modems from home and hook them up.
A simple clause such as "Installing, deletion or modification of software with your any computer hardware will lead to imediate diciplinary action," would circumvent some problems. And anyone who signs something they don't understand, such as a work contract, usually get what they deserve.
Personally, I like the smarter users, they don't make idiotic mistakes such as bad passwords, and install software. They understand rules better and what is implied in them, along with their consequences.
The problem isn't the users or the administration of the company. It isn't the administrator either. It is really the ignorant. It is the users who fail to use good passwords, the administration who want access from anywhere and the bad administrators who leave their broadcasts open for network packets to be accepted from. It is the bad programmers who trust user input to work with strcat in C or using open(F," $fromUserForm"); in perl.
Problems from my old job? The usage of sniffers, since everything was on hubs.
Unix machines used from inside the network that is not secure.
Access from anywhere for ftp without restriction other than username and password
Age of oldest backups, 2 weeks. Hard drives also quadrupled the space of the tape drives.
Bad backup schemes: if you can't fit all of it one one tape, do a full backup for a fraction on different days, otherwise use an incremental for that day. I don't feel like sorting through 25 tapes if a system goes down.
That's the great thing about Unix design, you can easily get rid of the basic service and replace it with something else that is just as functional if not more.
Because of PAM, you don't need to use <sarcasm> the "stupid password file" which is so "insecure" since it's a file on a filesystem </sarcasm>. Hell.. if I wrote a program in pc assembler, i'm quite sure moving the needle over the right part of the disk and reading the bytes where the root password is, is NOT the hardest of things, providing that one knows assembler *grin*.
The moral fo teh story is that *nix has more ability for possibilities while NT is more about using MS's possibilties for lowerlevel functionality.
I work(ed) for a company that has media, video and audio that we have to protect from others linking to. Other than financial reasons of linking a particular video to a particular page, there are legal reasons to do this. It's similar to public viewing of movies and licensing. There are licensing issues where a video cannot look like it is linked to some random site, because it causes confusion of ownership and/or who has the right to host it on their website. Think of it as some knucklehead on NBC broadcasting a CBS tv show and it has the CBS logo on there. It's clear to the more intelligent where it came from, but otherwise it's an NBC show. It's silly on the outside, but for ownership problems, it's quite relevant.
Slashdot Mirror
It would be impossible to keep track of all of the transactions, and anyone implementing this would be hated. Just what we all need, sales tax and now web tax? Perhaps sales tax on subscriptions, i can almost understand, but still.
It's the easiest way to share your documents quickly, and if someone adds some code, in a securer manner. Just a quick and dirty module to do file listings on directories and its browsable in your favourite browser. Running Apache for sending a couple of users alone might be a bit much to run and config.
I know of many companies who use apache to serve documents across the net simply because netbios is a nasty overkill. No more NFS/Netbios shares.
The smallest HTTP getter? Possibly snarf. The usage of these two tools is great for information passing. Slap on a small html interpreter; they come in a few hundred kb's for the pilot already.
Mm.. the possiblities...
I would hope so... continuously modifying assembler is such a pain. Think of the C coding like dynamic macros.
I mean something for like apache 1.0, linux 0.8.1 and what not. its too much of a scavanger hunt to find some of the old software. they are so much like historic works of art that we can learn from.
An idea for those with disk space, and some unf.. a software repository for old code?
mother's womb probably.. each and every cast member they ever used.
Hey, when I used to collect musical lyrics and put them on my web site.. it was a fetish. By then lyrics.ch had popped up as leo went down. We all remember that.
The fetish part of it is the consistent, driving to go further, with something. In this case, people are trying to drive thier palm's (yes you momo's.. they've been renamed a year or two back) to do more. It's not a geek thing.. it's a motivational thing. I'm a psych minor.
Well... if you expand the disc a bit and put in a hole, you can put it into a type of caddy system.
I'm quite sure some knucklehead out there will hack a client to deaht and mess with their heads a little. Its not as if not using an OSS solution is circumventing hacking of any sorts.
I give you that on the patent example.. it is a bad one at that. Sometimes patents take too long to go through at times.. but that's neither here nor there.
For the sysadmins that need to worry about licensing, the companies, it becomes easier. All of our basic rights, I dunno about that.
I give you that on the patent example.. a pad one at that. Sometimes patents take too long to go through at times.. but that's neither here nor there.
For the sysadmins that need to worry about licensing, the companies, it becomes easier. All of our basic rights, I dunno about that.
But honestly.. the concept of reposession, great idea. Just as if you are using your phone for 'wrong' they can disable it, if you use software for illegal reasons (use), cool. I would like to see how this would be enforced in a fassion that it won't be easily crackable. Encrypt most of the program so that the small encrypted portion decrypts?
Enforcable licensing and reverse engineering. I would hope that GPL would be marked as one. So stop whining if it is. Else, it scares me.
Reverse engineering is bad and its good. Its good in the sense as it doesn't restrict and allows free development on the code. It lets alternatives sprout. Its bad in the sense that how something is done, the concept, can be patentable and this is just a further way of enforcing it. Depends on which side of the line you are on. OSS vs non-OSS.
The upside on tracked licensing, easy transfer of warantee or other promised services. Down side, who the heck is going to be patient enought to use it? Those new to computers. Hell, we already do this with cars, no? This forces the companies to get off their ass and do better tracking of who owns what. This allows a company to even sell its software to different departments or branches with less trouble.
Disclaiming warantees is my big issue. Wouldnt' the disclaiming of warranty considered a form of false adavertising? To say that a warranty claims that we give support with this product but we, the company, say no since we want to?
I guess because I use only OSS, it won't affect me as much. This also is more a fight for the companies over idiot p1r4t3s. But you reap what you sow.
- The mbox format it uses is very nice for moving things around, but don't forget, if one acct gets bogged down, it gets blocked due to file locking problems. (if you use the default local mailer). Multiple mail files are nicer. May run out of inodes quicker if you aren't careful.
- Its ruleset bogs things down just a bit. Significant if you want to get more than 10k emails out in an hour. (I haven't really benchmarked it yet.) Power versus speed, configurability versus mail handled per sec.
- Sendmail is a big program. Qmail is smaller and more modular in the sense. The operating system's process scheduler can handle things better than sendmail's internals. I've had server loads of 10 with higher traffic on a dual 300mhz machine.
Why not to use qpopper- To download your mail, a second copy of your mail spool file gets made so that qpopper can sort out which mail you wish to keep. Effectively you get only 50% of the diskspace.
- All users must exist on the system. Bad system administrators (like at my old job) would make home dirs for all users, leaving ftp open at times. Virtual local users kick butt.
There is your reliable software. For network stuff, I would highly recomend FreeBSD, but Linux would do fine. I would recomend qmail as it is both a popper, mta and local mailer. It doesn't give the problems above.HTTP_REFERER spoofing breaks this. User accounts and ip checking is a way of circumventing this a bit more..
If you really want to protect it better, forcing people to use an account /w ip checking to ensure multiple people aren't using the same one would work better.
It's about time someone defined what is copyright enfringement on the web and how public data is when it is put on the web. I haven't checked the site, but perhaps some sniplet on the bottom explicitly saying that linking is illegal?
Btw, a child doesn't need to have the parent in the movie, just in the theatre.. or so it goes in NYC at the theatres I've gone to... But this isn't an arguement on how things are in which areas, but how your arguement is just terrible.
Disapointedly,
Spencer
I believe the saying goes, a picture is worth a thousand words. Depicting something so physical as paper money in terms of bits and what-not seems more forgable than before.
Someone may bring up, ATM's.. but we never have direct access to their programming. With a PDA, we can just dump memory and inspect.
I am not saying there are no advantages, just the danger seems more ominous.
it's refreshing to see yet another compiler for c/c++ out there. I hope people don't start thinking it's an intrusion in the unix world to have a commercial compiler.
it seems to be that it is no longer a commercial environment with little patches of freeness such as linux and *bsd (most of at least) but a free world with some great commercial products out there as well as great fre ones.
I don't think it's so much stupidity as just ignorance. Was it an end to stupidity or an end to not knowing that too much causes cancer?
---
When in doubt, scream and shout!
Personally, I like the smarter users, they don't make idiotic mistakes such as bad passwords, and install software. They understand rules better and what is implied in them, along with their consequences.
- Problems from my old job? The usage of sniffers, since everything was on hubs.
- Unix machines used from inside the network that is not secure.
- Access from anywhere for ftp without restriction other than username and password
- Age of oldest backups, 2 weeks. Hard drives also quadrupled the space of the tape drives.
- Bad backup schemes: if you can't fit all of it one one tape, do a full backup for a fraction on different days, otherwise use an incremental for that day. I don't feel like sorting through 25 tapes if a system goes down.
- Bad passwords galore
Its too bad one can talk, but no one listens.Yeah.. but OS/2 4.0 == OS4/2 == OS/2!
That's the great thing about Unix design, you can easily get rid of the basic service and replace it with something else that is just as functional if not more.
Because of PAM, you don't need to use <sarcasm> the "stupid password file" which is so "insecure" since it's a file on a filesystem </sarcasm>. Hell.. if I wrote a program in pc assembler, i'm quite sure moving the needle over the right part of the disk and reading the bytes where the root password is, is NOT the hardest of things, providing that one knows assembler *grin*.
The moral fo teh story is that *nix has more ability for possibilities while NT is more about using MS's possibilties for lowerlevel functionality.
I work(ed) for a company that has media, video and audio that we have to protect from others linking to. Other than financial reasons of linking a particular video to a particular page, there are legal reasons to do this. It's similar to public viewing of movies and licensing. There are licensing issues where a video cannot look like it is linked to some random site, because it causes confusion of ownership and/or who has the right to host it on their website. Think of it as some knucklehead on NBC broadcasting a CBS tv show and it has the CBS logo on there. It's clear to the more intelligent where it came from, but otherwise it's an NBC show. It's silly on the outside, but for ownership problems, it's quite relevant.