Yeah, if he's working with ISP's then, this system
is going to be on the backend. And is the system
going to 'know' if a child is reading the web,
or is it just going to log everything? My guess
is it's the latter.
Imagine this. You're accused of a crime. And
every website, you've ever visited for the last
5 years comes into evidence. Prosecution says,
"Research has proven that 75% of Pedophiles
have viewed teletubbies.com at least three times in the last 4 years. Look at these web logs."
Heh, heh.
It seems to me that each user should have his
own RPM database. So, that if I want to, say,
install a game in my 'cathryn' directory, wouldn't
have to go to root to do it. Ideally every package, could have a 'root' install for everyone, and a 'non-root' install for an individual user, I'd think. Am I missing something?
Still, now after the CSS debacle, I'm always inclined to hold out the possibility that someone designing the system has screwed up royally. And even though the obvious thing is to assume that nobody will figure any of these out -- the possibility is still there, that somebody's code is just fucked up.
Let's say, you're making a cyper, and the restriction is that your spies can't have any codebook of any kind on their body to be kept around as evidence. Say, for example, that your spies can know what time the secret message is coming, but they can't just sit and listen all day. I'm trying to think through, given restrictions like this, what the encryption would look like. Is there Phd-type research on exactly this kind of thing?
And, it seems to me, that Microsoft has to be divided according to where the income is. Seems to be the best 3-way split would be as...
1. Windows 98 OS. Include the consumer level operating system stuff here. Put IE in this company.
2. Windows NT OS. Put all the backend stuff in this company.
3. Microsoft Office
This would result in some kind of OS competition, between the OS and 98 style operating systems. Also, all three of these groups would be viable companies. If Microsoft baby's still played weird monopoly games, the DOJ, could also divide it up again to even more companies later on, I guess.
Is there a way to disable html viewing of email in Outlook Express? I'd like to see Email the way God (with a capitol G) intended, that is as plain ascii. The only html formatted mail I get is from spammers. Hmm, though come to think of it, maybe I should just kill all the html formatted mail in sendmail.
Yeah, I suspect the Russians, if they want to make an economy out of this stuff have to pick their battles carefully. And, that they could go after just enough of the high level, blatant pirates to keep the US happy, but let some of these other issues, where there's copyright legality involved, but not a whole lot of lost income involved, like this music lyric thing slide. And, probably there wouldn't be a huge international issue over this.
Hey, I thought the point of C++ was so that the programmers could surf the internet during the long compile times. Except you can debate the finer points of object oriented structure with your fellow programmers while your 2 hour compile is going.
Or, what I suspect is that C++ or not, something is going to end up being obfuscated, however you put it together. So, if you have a 'message oriented' setup, that is components queue messages to one another and those queues are processed later, your high level components might be well-organized, but then the actual flow of control can be confusing.
I think this is what makes Windows programming confusing. On paper it seems simple enough. message comes in, process the message, do the code. But the order of the messages, and what system calls creates what messages, the weird race conditions and weird recursion problems make it tricky to completely debug all the peculiar conditions.
There's a pattern I've seen at some companies. Programmer comes in, spends 2 hours looking at the source. Says, "This is Crap, I need to re-write all this stuff." Then, he spends a long time, basically re-writing the entire thing, and breaking tons of stuff. At the end of a long process, the program is sort of where it was at the start, that programmer moves on and someone new comes in. He says "This is crap, I need to rewrite it all" and then the whole thing starts all over again. I would say that most programmers, coming into lot of 'someone else's code,' whatever the state of that code is, will tend to say it's crap no matter how it's put together. Just as a matter of reflex. And, partially, I think this is because they understand the stuff they wrote themselves, and when they read other code, they don't get the same warm fuzzy feeling they get reading their own code.
I used to run a PC Hardware configuration testing company, and the testers always used to sneak in and overclock the machines. But, like, I kept telling these guys, that in order to be sure we found real bugs, we needed to run stock machines. But, noooo, these guys just had to do it, even when I told them they couldn't. I think I fired someone over this. Overclocking is an addiction -- seems to me.
Slashdot Mirror
Yeah, if he's working with ISP's then, this system is going to be on the backend. And is the system going to 'know' if a child is reading the web, or is it just going to log everything? My guess is it's the latter. Imagine this. You're accused of a crime. And every website, you've ever visited for the last 5 years comes into evidence. Prosecution says, "Research has proven that 75% of Pedophiles have viewed teletubbies.com at least three times in the last 4 years. Look at these web logs." Heh, heh.
It seems to me that each user should have his
own RPM database. So, that if I want to, say,
install a game in my 'cathryn' directory, wouldn't
have to go to root to do it. Ideally every package, could have a 'root' install for everyone, and a 'non-root' install for an individual user, I'd think. Am I missing something?
Still, now after the CSS debacle, I'm always inclined to hold out the possibility that someone designing the system has screwed up royally. And even though the obvious thing is to assume that nobody will figure any of these out -- the possibility is still there, that somebody's code is just fucked up.
Let's say, you're making a cyper, and the restriction is that your spies can't have any codebook of any kind on their body to be kept around as evidence. Say, for example, that your spies can know what time the secret message is coming, but they can't just sit and listen all day. I'm trying to think through, given restrictions like this, what the encryption would look like. Is there Phd-type research on exactly this kind of thing?
And, it seems to me, that Microsoft has to be divided according to where the income is. Seems to be the best 3-way split would be as...
1. Windows 98 OS. Include the consumer level operating system stuff here. Put IE in this company.
2. Windows NT OS. Put all the backend stuff in this company.
3. Microsoft Office
This would result in some kind of OS competition, between the OS and 98 style operating systems. Also, all three of these groups would be viable companies. If Microsoft baby's still played weird monopoly games, the DOJ, could also divide it up again to even more companies later on, I guess.
Is there a way to disable html viewing of email in Outlook Express? I'd like to see Email the way God (with a capitol G) intended, that is as plain ascii. The only html formatted mail I get is from spammers. Hmm, though come to think of it, maybe I should just kill all the html formatted mail in sendmail.
Yeah, I suspect the Russians, if they want to make an economy out of this stuff have to pick their battles carefully. And, that they could go after just enough of the high level, blatant pirates to keep the US happy, but let some of these other issues, where there's copyright legality involved, but not a whole lot of lost income involved, like this music lyric thing slide. And, probably there wouldn't be a huge international issue over this.
Hey, I thought the point of C++ was so that the programmers could surf the internet during the long compile times. Except you can debate the finer points of object oriented structure with your fellow programmers while your 2 hour compile is going.
Or, what I suspect is that C++ or not, something is going to end up being obfuscated, however you put it together. So, if you have a 'message oriented' setup, that is components queue messages to one another and those queues are processed later, your high level components might be well-organized, but then the actual flow of control can be confusing.
I think this is what makes Windows programming confusing. On paper it seems simple enough. message comes in, process the message, do the code. But the order of the messages, and what system calls creates what messages, the weird race conditions and weird recursion problems make it tricky to completely debug all the peculiar conditions.
There's a pattern I've seen at some companies. Programmer comes in, spends 2 hours looking at the source. Says, "This is Crap, I need to re-write all this stuff." Then, he spends a long time, basically re-writing the entire thing, and breaking tons of stuff. At the end of a long process, the program is sort of where it was at the start, that programmer moves on and someone new comes in. He says "This is crap, I need to rewrite it all" and then the whole thing starts all over again. I would say that most programmers, coming into lot of 'someone else's code,' whatever the state of that code is, will tend to say it's crap no matter how it's put together. Just as a matter of reflex. And, partially, I think this is because they understand the stuff they wrote themselves, and when they read other code, they don't get the same warm fuzzy feeling they get reading their own code.
I used to run a PC Hardware configuration testing company, and the testers always used to sneak in and overclock the machines. But, like, I kept telling these guys, that in order to be sure we found real bugs, we needed to run stock machines. But, noooo, these guys just had to do it, even when I told them they couldn't. I think I fired someone over this. Overclocking is an addiction -- seems to me.