holy christ, who modded this INTERESTING??? Obviously, it was the great GPL conspiracy coming to the defense of their valiant knight Twitter. They are in constant battle with the forces of the M$ for the supremacy of the cyberverse.
wtf is wrong with you people? Um, I just said, it's the great GPL conspiracy. That speaks volumes in itself.
He seems like an asocial, obnoxious person who needs to be chewed out until he understands what he's doing wrong. Yeah, every popular site has one. Some of us even have em in real life. People like that are boat anchors on any site with user generated content, they slow the site down and get a lot of crap stirred up in the process.
I'm going to go out on a limb and say both Twitters have a roughly equal amount of 'suck', but one of them might actually amount to something one day. (Hint: It's not going to be the M$ one)
I'm amazed more sites don't use a NNTP server to be the backend of their forums. NNTP is designed to handle millions of messages with relative ease.
I guess it's the NNTP to HTTP interface that is a big headache. When you think about it, using a SQL database for something like messages is a huge waste of resources.
As has been said down the thread, there is nothing crazy about this book that would drive people away from the church, but this now allows for tons of things to be taken out of context (things taken out of context are the main reason that people think the LDS church is so weird... that, and flat out lies about it). Because it's always better to withhold information and an informed populace is a very dangerous thing.
I knew we couldn't get decent ad revenue at the time due to the site content. Also I didn't handle the finances so I couldn't tell you how much came in. I do know it was barely enough to cover hosting and sometimes development.
Copyright is a legal right granted by the government. Making an unauthorized copy is a violation of the copyright holders rights. Copyright is a limited monopoly to promote the arts.
I stopped caring about copyright holders rights when the government decided that limited was longer than the average American lifespan.
Motivated abusers tanked a site that I worked with a few years back (Started up in 1996, closed in 2002). I would love to have had a way to identify them.
First we started tracking with email. Free email ruined that. Then we started tracking with cookies. They figured out to erase cookies. Then we started tracking with IP addresses. Too many proxies. Proxy blockers never stay up to date, so they eventually get around that. Then we got some moderators. They became abusive fairly quickly. We were working on tracking using Flash when we realised it would be easier to shut the site down. It wasn't earning enough to warrant the non-stop work on something stupid like overcoming the Greater Internet Fuckwad Theory (http://www.penny-arcade.com/comic/2004/03/19/).
Why not ask your ISP if it is legal to "sublet" your connection and thereby deprive them of a revenue stream? Oh, the poor ISP is being deprived. My heart bleeds for them. Being a monopoly is SUCH HARD WORK.
Fuck em. Around here you have two choices, the tel co or the cable co, both are monopolies and both suck to some degree. I would like to personally thank the city council for granting exclusive contracts to Verizon and Time Warner. (By thank, I mean kick each council member in the groin, repeatedly).
Right and wrong would assume you have a choice, you don't have a choice. Do it, let them sue you, and have the courts figure it out.
guilty or not, the evidence was not substantial enough to prove guilt; as such, he should still be presumed innocent. That's a bold statement moving out of the realm of IMHO and into the realm of 'the jury was obviously wrong'. That's part of the point I was trying to make. You can't come to that conclusion based on facts.
The fact that "the system" says he's guilty, doesn't mean he is. Yes, but the fact that "the system" says he's guilty is the basis we use in our society to determine guilt or innocence. Unless someone provides evidence that the system failed, I'm going to take the verdict at face value. I don't have to defend the system, you have to prove that it failed.
guilty or not, the evidence was not substantial enough to prove guilt; as such, he should still be presumed innocent. Did you read the entire court transcript? Were you in the court every day? Did you read any third-party summaries or stories about the case?
What it boils down to is this: You don't get to make that call, the jury does.
Anything else is just an opinion. He's no longer presumed innocent, he's now deemed guilty, that's how the system works.
I've always maintained that the database should enforce data integrity. Not just hold data, but actually stop bad data from ever getting saved.
That being said, I might be spoiled using SQL server. I've done some setups where a SQL server (sometimes MSDE) runs on the app server and enforces the rules (with some server caching tables as well) and passes data out to a SQL server cluster which holds the actual data. (It's really hard to explain without showing diagrams and violating my NDA, but it worked well for the project at the time, saved a good chunk of money too)
While I do try to use stored procedures for all projects, parameterised queries is a very good second choice. I don't understand why they're not used as much.
When you get into unvalidated inserts and selects, that's what drives me nuts.
A properly designed database layer shouldn't have the ability to take in bad data from any source and shouldn't trust the app server (if possible).
One method that I used that worked amazingly well was to use stored procedures with strict validation for all data access to/from the databases. No one had any access except explicit execute access to the stored procedures. Yeah, it was harder to design, but it flew. Porting to other app servers was really easy too, the procedures did all of the data work.
Some designers think this is overly complex, it's not really. It's just a matter of letting your database do your data work (what it was designed for), not your application server (what it wasn't designed for).
Too many poor developers just make the web app run as dbo. They also tend to use 'select * from' all too often.
Drives me nuts, because I'm the exact opposite, you don't get any (yes including read) access except a few stored procedures you need to read/write data.
Validate at the client tier. (To save a return trip) Validate at the application server tier. (to save a database trip) Validate at the data tier. (to save your data)
Should I expect you to be able to discuss this without ridiculous, fallacious comparisons? Nope. Welcome to Slashdot.
Our territorial waters (which are US sovereign territory) border Canadian territorial waters (which are sovereign Canadian territory). If you were going to attempt pedantry, you should have tried to be correct. If you were going to attempt an ad hominem attack, you could have done better.
notice you conveniently leave out that the San Juan Islands border Canada (thus being an international border) Islands really don't border countries, the water around them does. Boat patrol in international water is fine, detaining domestic ferry passengers isn't.
are accessible from open, international water The same way New York City is, should I expect to be stopped on the ferry from Queens? After all, the Atlantic Ocean borders dozens of countries.
Slashdot Mirror
I'm going to go out on a limb and say both Twitters have a roughly equal amount of 'suck', but one of them might actually amount to something one day. (Hint: It's not going to be the M$ one)
I'm amazed more sites don't use a NNTP server to be the backend of their forums. NNTP is designed to handle millions of messages with relative ease.
I guess it's the NNTP to HTTP interface that is a big headache. When you think about it, using a SQL database for something like messages is a huge waste of resources.
I use outlook, it can be quirky, which is my biggest frustration with it. It's a good email program/pim when it's working properly.
Damn you and your something.
I knew we couldn't get decent ad revenue at the time due to the site content. Also I didn't handle the finances so I couldn't tell you how much came in.
I do know it was barely enough to cover hosting and sometimes development.
I stopped caring about copyright holders rights when the government decided that limited was longer than the average American lifespan.
Motivated abusers tanked a site that I worked with a few years back (Started up in 1996, closed in 2002). I would love to have had a way to identify them.
First we started tracking with email. Free email ruined that.
Then we started tracking with cookies. They figured out to erase cookies.
Then we started tracking with IP addresses. Too many proxies. Proxy blockers never stay up to date, so they eventually get around that.
Then we got some moderators. They became abusive fairly quickly.
We were working on tracking using Flash when we realised it would be easier to shut the site down. It wasn't earning enough to warrant the non-stop work on something stupid like overcoming the Greater Internet Fuckwad Theory (http://www.penny-arcade.com/comic/2004/03/19/).
I think you might be on to something.
Microsoft can tank Yahoo's stock for next to nothing. Then wind up buying the company for less. Actually, it's pretty smart.
The bottom line is, Yahoo should not have let itself get in this situation.
Fuck em. Around here you have two choices, the tel co or the cable co, both are monopolies and both suck to some degree. I would like to personally thank the city council for granting exclusive contracts to Verizon and Time Warner. (By thank, I mean kick each council member in the groin, repeatedly).
Right and wrong would assume you have a choice, you don't have a choice. Do it, let them sue you, and have the courts figure it out.
What it boils down to is this: You don't get to make that call, the jury does.
Anything else is just an opinion. He's no longer presumed innocent, he's now deemed guilty, that's how the system works.
Because the automated injection script was written for asp/asp.net and Apache rarely uses asp or asp.net.
Please scan your news sites for past and future php scripts if it makes you feel any better.
I've always maintained that the database should enforce data integrity. Not just hold data, but actually stop bad data from ever getting saved.
That being said, I might be spoiled using SQL server. I've done some setups where a SQL server (sometimes MSDE) runs on the app server and enforces the rules (with some server caching tables as well) and passes data out to a SQL server cluster which holds the actual data. (It's really hard to explain without showing diagrams and violating my NDA, but it worked well for the project at the time, saved a good chunk of money too)
I agree completely.
While I do try to use stored procedures for all projects, parameterised queries is a very good second choice. I don't understand why they're not used as much.
When you get into unvalidated inserts and selects, that's what drives me nuts.
I see you met my old boss.
A properly designed database layer shouldn't have the ability to take in bad data from any source and shouldn't trust the app server (if possible).
One method that I used that worked amazingly well was to use stored procedures with strict validation for all data access to/from the databases. No one had any access except explicit execute access to the stored procedures. Yeah, it was harder to design, but it flew. Porting to other app servers was really easy too, the procedures did all of the data work.
Some designers think this is overly complex, it's not really. It's just a matter of letting your database do your data work (what it was designed for), not your application server (what it wasn't designed for).
Then the project manager should be lectured on proper development techniques.
Too many poor developers just make the web app run as dbo. They also tend to use 'select * from' all too often.
Drives me nuts, because I'm the exact opposite, you don't get any (yes including read) access except a few stored procedures you need to read/write data.
The 3 minimum levels of validation:
Validate at the client tier. (To save a return trip)
Validate at the application server tier. (to save a database trip)
Validate at the data tier. (to save your data)
Why is this so hard for developers to understand?