Well if the government buys stuff with currency it creates or "prints" (aka borrows with a low chance of paying back), it's basically taxing everyone who holds net positive amounts of that currency.
Yes, how very true...
But, what about the people who hold net negative amounts of that currency? Their debt becomes less.
Now, why would you want to reduce the overall debt load.... its not like the government has 10 trillion dollars in debt, and this entire economic meltdown was based on excessive amounts of debt or anything like that...
Quantum communication isn't FTL. Two entangled photons "transmit" information at the speed of light - a change on alters the other within the limits of relativity.
However, quantum communication would in theory be a lot less expensive. Entangle two photons, separate them, and you can communicate without having to worry about all the other fun stuff like wiggling a piece of light at some massive amplitude.
Quantum communication makes a LOT of sense, if we can nail it down. Assuming how close we are to it, if another species was around for a millennium, they probably would be using that exclusively.
The downside for us - its completely impossible to eavesdrop on it.
I thought such attacks were a thing of the past. I am disappointed. But on a serious note, is there a way to completely "immunize" oneself against such attacks? If so, where is the howto?
tl;dr: no.
You can do quite a bit to reduce the risk and react well to the situation, but as long as you're on the internet and there are botnets, DDOS is possible. It might even look like too much "normal" traffic. Given this is a DNS attack based on DNS traffic, its quite possible the only reason they know its a DDOS is because its a whole hell of a lot more traffic than usual.
Unless you spend tens of billions on infrastructure, you're not very resilient. Even IF you do, that doesn't mean certain pipes cant be filled and certain sections of the internet become unreachable.
The problem seems to kick in for DNS servers that arent rejecting the queries. Someone is channeling ye 'ole smurfing methods.
They're requesting a list of all DNS root servers. If the server don't reject the query, a 17 byte query becomes a 50k response (or something like that) to the spoofed address.
This is DNS hosting provided by Network Solutions for people who buy domains from them and choose to have them host the DNS rather than host it themselves.
How do you hope to architect a fix for this? Thought I don't know the specifics, they said that they were using the same UDP socket to transmit from multiple threads. That means you have one kernel space data structure across the entire UDP/IP stack being shared by multiple threads. Therefore you need a lock around updates to that data structure.
No idea, I haven't reviewed the kernel either. But from this line:
Fixing the kernel by breaking up the lock is not easy.
It would appear that they did. It is not impossible to write a lockless queue mechanism.
Wow, you're uninformed on multiple levels with this post.
1. "They" didn't write memcached. Livejournal did, and then they open sourced it. "They" didn't provide a half-assed implementation. They pushed a piece of open source software further than it had before, and found problems.
2. If you'd read the next sentence right after your bold line, you'd notice they were talking about a kernel lock. Not a lock in memcached. Thats a totally valid reason to blame linux.
If you bothered to actually spend some time programming hugely complex high performance applications, you'd realize quite quickly that the Linux kernel, while damn near the best kernel out there, isnt perfectly suited to your application. I can list off five or six things right now that I have problems with in the Linux kernel. But -every- application designer with sufficient experience (especially in large-scale performance apps) can probably do the same.
Before you say: well why don't you fix it yourself.. look at the quote you referenced again. They considered it, and took a different route.
Thats because Unions work well for labor industries, not white-collar industries.
I know some people in a union locally, in a labor industry. Even they hate it - people fly through to better jobs and better pay based on seniority and not ability. If you want to be measured based on seniority and education purely instead of ability and skill, by all means, unionize.
I can not imagine the tech industry unionizing. It would be like saying 'anyone can do this job, it takes no skill'.
I have no formal education, but I consider myself fairly good at what I do. Unions would have crushed my ability to move up.
Break something important. Calculate how much time is spent bitching about it for the next 24 hours. Multiply by 365 days and by the average salary. Thats how much you save!
What about getting a ham radio license? That's fine and all, provided you don't ever use encryption, don't mind people intercepting your data, and remember to identify your station periodically.
I don't know much about ham radio (or radio in general) but I thought that the frequencies of ham simply did not provide the bandwidth that would allow a reasonable highspeed rate... can you explain how that would be set up? You've piqued my curiosity.
Also can anyone actually explain why we should be bailing out these banks in the first place?
Sure. Note I'm not necessarily advocating this, but I've had this well explained to me - and I like sharing it, because its horrifying.
Instead of looking at the banking system, first lets look at the insurance system. Its a bit easier to understand. There are a handful of big insurance companies, and hundreds of little insurance companies. Because of the risk involved in everything, they insure each other. So lets say there is a major catastrophe somewhere that requires hundreds of millions of dollars in payouts. Now, the small insurance company out there can't absorb that hit without going under. So by insuring themselves with OTHER insurance companies, they build a web of disbursed risk.
Therefor, when a major event happens, the whole system generally absorbs the shock. This allows the entire insurance industry to exist - otherwise the risk involved insuring someones house for half a million dollars for a measly $50 a month becomes much more risky. If you spread that risk over a huge number of houses - and companies - it makes sense. Economies of scale - insuring one house makes no sense.
This means the failure of a major insurance company is very unlikely. But it also means that if one of the major insurance companies folds because of payouts, they ALL fold. The entire system collapses.
The banking system is exactly like this. If one of the major banks were to actually, really, truly fail the entire financial system would collapse. The banks are too interdependent. All the money in your chequeing account, your investments, mutual funds offered by your bank, all of it would disappear along with your bank. You could probably get some FDIC insurance coverage, but that would be about it.
The choice is being made, actively, to devalue currency in order to eliminate the debt we've built up. There are only two options we have in the current situation: deal with long, severe depression and financial system collapse or large amounts of inflation.
Why this isn't being reflected in the market currently is quite confusing actually. You can't dump two trillion dollars into an economy and see the value of the dollar go -up-. Someone is screwing with the system right now, and I would bet we'll see a heavy reset in the next 12 months.
I don't see anything in here that requires two separate companies.
From an organization or technology perspective, no, there isnt any reason to split into two companies. From a financial perspective, this makes a huge amount of sense. You'll note that this new company is receiving an enormous amount of new funds from investors, and taking a lot of the AMD debt. They're effectively splitting off R&D from Manufacturing, and people are free to invest in just the R&D component or just the manufacturing component.
Some folk out there thought the manufacturing side was worth a huge investment of cash. Lots of assets there that are worth a fair bit - but not if they're tied to work purely on AMD products. If the R&D side of AMD failed, then there are a crapload of perfectly good assets that would be lost, in effect. This allowed investors separate AMDs chips from AMDs fabs when investing. There is no inherent value in splitting the fabs off - except when someone is willing to spend $8 billion to fix them up, separate from the R&D side.
This doesn't mean they think AMD R&D is going to fail - its just about risk. Why tie your $8 billion investment to the ADD of the consumer chip market instead of to physical assets that will be worth something regardless of the mood of the x86 CPU market?
Honestly, this shouldn't be modded flamebait. While Dawkins is most definitely an incredible evolutionary biologist, and an incredible lecturer - he wouldn't be nearly as recognizable if he hadn't gone on his rant against religion.
I bought a PS3 and picked up a handful of Blu-Ray titles since. Not until I got a copy of the BBC documentary Planet Earth did I feel that anything justified Blu-Ray.
That series is incredible. And having it in High-Def was worth the money for me, hands down.
I've been working on my open source project for about ten years now, and it has played a major role in every single job that I've held.
I got my present job through someone I worked on the project with. I've been there 4.5 years.
I also got involved in a local unix users group by way of hearing about it from some friends of the open source project. The connections I made at that users group have gotten me the job I will be starting in one month.
My open source project, however idle it has been for the last several years, has contributed significantly and directly to my career.
And I've been looking for a job for over 5 months now, and mainly in tech support and system administration because really, no one wants to hire me for a coding job.
Get used to it. Unless you want to crank out business rules written in Java, systems administration/engineering/architecture is the place to be, IMHO. In those teams you can actually do work in C, mess around inside the kernel, and actually make use of all your skills. "Programmers" these days actually seem pretty boring unless you're working for a tech company that has an exceptional software engineering department doing something interesting.
I take my entire coat off and threw it in a bin for the x-ray machine. They didn't catch it. It was on my key chain, in an open pocket along a handful of coins.
Its more than that. Its about making money. For private corporations.
Why else would the TSA allow you to get special ID for a few hundred dollars to bypass security.. designed and maintained by a private company? Specially designed TSA approved bags.. designed by private companies. Not to mention the billions of dollars filtered through to private corporations for those expensive x-ray and other fancy security devices.
And they do shit all. I've flown twice in the last two years with a swiss army knife in my pocket without realizing it.
yeah, you know, 'cause when you have 50 programmers on a project, java l33tnesses like
Blah x = new Blah();
is so cool and easy to understand. and just forgetting about memory management completely is so efficient. and horizontal clustering is for wussies, if you need less than 8 gigs of memory on linux, it is because you're unl33t or because you obviously aren't using as many threads as you should.
now when you program in C you forget all that crap, you just code. need a bigger app? Abstract session management to central storage and add servers. add nodes a needed to keep performance. node dies? no problem, your IP load balancer takes it out of rotation.
Migrated from mysql to Oracle or DB2? no problem, you abstracted your DB layer, right?
Tired of Windows Server and want to run opensolaris, linux or OS X Server? no problem, you wrote everything POSIX, right? it's working.
wanna add more coders to your project? point 'em to the oxygen docs and let they read through the verbose (and thus self-explaining) code.
Compliers stop you from doing somthing stupid, and since you're scaling horizontally, service outages are absorbed by the network level. With your logging systems you can always tell what the program IS going to do in all situations, because your coding review standards force you to.
but you're too cool for C.
I dont normally feed trolls, but wow, everything has its place - and java's place is much smaller than some people seem to think it is
Given that many filesystems are designed specifically with the spinning magnetic disk in mind, what open source filesystems are out there that will work to the advantages of solid state storage? Has anyone started thinking about that one as something to address before the major switches start taking place?
Or... does solid state storage take care of those oddities in firmware with the whole automatic write leveling technology?
The fundamental cause of the trouble comes from C's "pointer=array" equivalence. That was a terrible mistake, borrowed from BCPL.
Borrowed? Sorry, I don't know much about programming languages, but I do know C. The whole "pointer=array" thing is bunk. Pointers are NOT arrays. You're misunderstanding whats happening. Pointers only point to memory locations. Arrays are only a different way of referencing the same memory locations. There are dozens of other ways to look at the same area.
The trouble is that the compiler knows neither which variables are arrays nor how big the arrays are. You can't even talk about arrays properly. I mean, of course, int read(int fd, char* buf, size_t len); That's just trouble waiting to happen. "read" has no information about how big "buf" is.
Actually, the compiler knows exactly how big buf is. Its the size of a pointer on that system. Of course, if you want to copy data into the memory space POINTED to by buf, then you should tell it how far to write. Thats what len is for.
C works how computers work. It is not a language that tries to hide it from you. If you want to code in C, you should understand this. Realize that in terms of CPU operations, having a language track every begining and end of every separately allocated memory space is very expensive. Try compiling a C app with the bounds checking GCC extensions sometime (its a separate gcc patch), and see how well your app performs while it is checking every single allocation and memory reference.
Oh, and before you say that the compiler should figure out if that happens, think about how much flexibility would be lost if every single allocation was static in size.
So not only do they screw the Tolkien trust, but they also screw the guy who MADE the movie. Good job Newline, I have a feeling you may have a hard time attracting talent in the future.
Stories like this, and the various others I have heard since I involved myself in this have made it feel like one of the best things I've ever done. You give me the drive to continue.
I hope you'll come out, and perhaps be able to tell your story at one of the protests next month. It needs to be heard.
Thats one. There are hundreds, if not thousands, more. Including the niece of David Miscavish (the current leader of scientology).
Come on people, the information is out there. You can easily take a balanced view by READING the accounts of the hundreds of people who've been victimized. Look up Paulette Cooper. Shes still alive today to tell her story of being harassed and sued for 15 straight years.
London, UK - around 500 people. LA - around 500 people Sydney, Australia - around 300 people. Clearwater, Florida - around 250 people. This one is scientology headquarters. New York - around 320 people Boston - around 270 people Atlanta - around 250 people. They called out the riot squad in full gear, with a helicopter. There was no incidents at all. Washington DC - around 200 people. Toronto - around 200 people.
In total, the estimates are around 8000 people worldwide. The aim was, of course, to get over 9000.
grip: i submitted details of these protests to slashdot twice before this took place, hoping we could get some of you folks out. *shakes fist at editor*
Slashdot Mirror
Well if the government buys stuff with currency it creates or "prints" (aka borrows with a low chance of paying back), it's basically taxing everyone who holds net positive amounts of that currency.
Yes, how very true...
But, what about the people who hold net negative amounts of that currency? Their debt becomes less.
Now, why would you want to reduce the overall debt load.... its not like the government has 10 trillion dollars in debt, and this entire economic meltdown was based on excessive amounts of debt or anything like that...
Quantum communication isn't FTL. Two entangled photons "transmit" information at the speed of light - a change on alters the other within the limits of relativity.
However, quantum communication would in theory be a lot less expensive. Entangle two photons, separate them, and you can communicate without having to worry about all the other fun stuff like wiggling a piece of light at some massive amplitude.
Quantum communication makes a LOT of sense, if we can nail it down. Assuming how close we are to it, if another species was around for a millennium, they probably would be using that exclusively.
The downside for us - its completely impossible to eavesdrop on it.
I thought such attacks were a thing of the past. I am disappointed. But on a serious note, is there a way to completely "immunize" oneself against such attacks? If so, where is the howto?
tl;dr: no.
You can do quite a bit to reduce the risk and react well to the situation, but as long as you're on the internet and there are botnets, DDOS is possible. It might even look like too much "normal" traffic. Given this is a DNS attack based on DNS traffic, its quite possible the only reason they know its a DDOS is because its a whole hell of a lot more traffic than usual.
Unless you spend tens of billions on infrastructure, you're not very resilient. Even IF you do, that doesn't mean certain pipes cant be filled and certain sections of the internet become unreachable.
The problem seems to kick in for DNS servers that arent rejecting the queries. Someone is channeling ye 'ole smurfing methods.
They're requesting a list of all DNS root servers. If the server don't reject the query, a 17 byte query becomes a 50k response (or something like that) to the spoofed address.
Hi! You're wrong. That would be Verisign.
This is DNS hosting provided by Network Solutions for people who buy domains from them and choose to have them host the DNS rather than host it themselves.
Thanks for playing.
How do you hope to architect a fix for this? Thought I don't know the specifics, they said that they were using the same UDP socket to transmit from multiple threads. That means you have one kernel space data structure across the entire UDP/IP stack being shared by multiple threads. Therefore you need a lock around updates to that data structure.
No idea, I haven't reviewed the kernel either. But from this line:
Fixing the kernel by breaking up the lock is not easy.
It would appear that they did. It is not impossible to write a lockless queue mechanism.
Wow, you're uninformed on multiple levels with this post.
1. "They" didn't write memcached. Livejournal did, and then they open sourced it. "They" didn't provide a half-assed implementation. They pushed a piece of open source software further than it had before, and found problems.
2. If you'd read the next sentence right after your bold line, you'd notice they were talking about a kernel lock. Not a lock in memcached. Thats a totally valid reason to blame linux.
If you bothered to actually spend some time programming hugely complex high performance applications, you'd realize quite quickly that the Linux kernel, while damn near the best kernel out there, isnt perfectly suited to your application. I can list off five or six things right now that I have problems with in the Linux kernel. But -every- application designer with sufficient experience (especially in large-scale performance apps) can probably do the same.
Before you say: well why don't you fix it yourself.. look at the quote you referenced again. They considered it, and took a different route.
Thats because Unions work well for labor industries, not white-collar industries.
I know some people in a union locally, in a labor industry. Even they hate it - people fly through to better jobs and better pay based on seniority and not ability. If you want to be measured based on seniority and education purely instead of ability and skill, by all means, unionize.
I can not imagine the tech industry unionizing. It would be like saying 'anyone can do this job, it takes no skill'.
I have no formal education, but I consider myself fairly good at what I do. Unions would have crushed my ability to move up.
Perfect!
Break something important. Calculate how much time is spent bitching about it for the next 24 hours. Multiply by 365 days and by the average salary. Thats how much you save!
What about getting a ham radio license? That's fine and all, provided you don't ever use encryption, don't mind people intercepting your data, and remember to identify your station periodically.
I don't know much about ham radio (or radio in general) but I thought that the frequencies of ham simply did not provide the bandwidth that would allow a reasonable highspeed rate... can you explain how that would be set up? You've piqued my curiosity.
Also can anyone actually explain why we should be bailing out these banks in the first place?
Sure. Note I'm not necessarily advocating this, but I've had this well explained to me - and I like sharing it, because its horrifying.
Instead of looking at the banking system, first lets look at the insurance system. Its a bit easier to understand. There are a handful of big insurance companies, and hundreds of little insurance companies. Because of the risk involved in everything, they insure each other. So lets say there is a major catastrophe somewhere that requires hundreds of millions of dollars in payouts. Now, the small insurance company out there can't absorb that hit without going under. So by insuring themselves with OTHER insurance companies, they build a web of disbursed risk.
Therefor, when a major event happens, the whole system generally absorbs the shock. This allows the entire insurance industry to exist - otherwise the risk involved insuring someones house for half a million dollars for a measly $50 a month becomes much more risky. If you spread that risk over a huge number of houses - and companies - it makes sense. Economies of scale - insuring one house makes no sense.
This means the failure of a major insurance company is very unlikely. But it also means that if one of the major insurance companies folds because of payouts, they ALL fold. The entire system collapses.
The banking system is exactly like this. If one of the major banks were to actually, really, truly fail the entire financial system would collapse. The banks are too interdependent. All the money in your chequeing account, your investments, mutual funds offered by your bank, all of it would disappear along with your bank. You could probably get some FDIC insurance coverage, but that would be about it.
The choice is being made, actively, to devalue currency in order to eliminate the debt we've built up. There are only two options we have in the current situation: deal with long, severe depression and financial system collapse or large amounts of inflation.
Why this isn't being reflected in the market currently is quite confusing actually. You can't dump two trillion dollars into an economy and see the value of the dollar go -up-. Someone is screwing with the system right now, and I would bet we'll see a heavy reset in the next 12 months.
I don't see anything in here that requires two separate companies.
From an organization or technology perspective, no, there isnt any reason to split into two companies. From a financial perspective, this makes a huge amount of sense. You'll note that this new company is receiving an enormous amount of new funds from investors, and taking a lot of the AMD debt. They're effectively splitting off R&D from Manufacturing, and people are free to invest in just the R&D component or just the manufacturing component.
Some folk out there thought the manufacturing side was worth a huge investment of cash. Lots of assets there that are worth a fair bit - but not if they're tied to work purely on AMD products. If the R&D side of AMD failed, then there are a crapload of perfectly good assets that would be lost, in effect. This allowed investors separate AMDs chips from AMDs fabs when investing. There is no inherent value in splitting the fabs off - except when someone is willing to spend $8 billion to fix them up, separate from the R&D side.
This doesn't mean they think AMD R&D is going to fail - its just about risk. Why tie your $8 billion investment to the ADD of the consumer chip market instead of to physical assets that will be worth something regardless of the mood of the x86 CPU market?
Honestly, this shouldn't be modded flamebait. While Dawkins is most definitely an incredible evolutionary biologist, and an incredible lecturer - he wouldn't be nearly as recognizable if he hadn't gone on his rant against religion.
Sensationalist? Probably. Twat? Definitely not.
If you were paying attention when you read any of Steven Hawkings' books, Penrose was mentioned several times.
Penrose and Hawking have done significant amounts of work together. In fact, Penrose corrected errors in Hawkings' PHd thesis.
I bought a PS3 and picked up a handful of Blu-Ray titles since. Not until I got a copy of the BBC documentary Planet Earth did I feel that anything justified Blu-Ray.
That series is incredible. And having it in High-Def was worth the money for me, hands down.
I've been working on my open source project for about ten years now, and it has played a major role in every single job that I've held.
I got my present job through someone I worked on the project with. I've been there 4.5 years.
I also got involved in a local unix users group by way of hearing about it from some friends of the open source project. The connections I made at that users group have gotten me the job I will be starting in one month.
My open source project, however idle it has been for the last several years, has contributed significantly and directly to my career.
And I've been looking for a job for over 5 months now, and mainly in tech support and system administration because really, no one wants to hire me for a coding job.
Get used to it. Unless you want to crank out business rules written in Java, systems administration/engineering/architecture is the place to be, IMHO. In those teams you can actually do work in C, mess around inside the kernel, and actually make use of all your skills. "Programmers" these days actually seem pretty boring unless you're working for a tech company that has an exceptional software engineering department doing something interesting.
Had it in my coat pocket.
I take my entire coat off and threw it in a bin for the x-ray machine. They didn't catch it. It was on my key chain, in an open pocket along a handful of coins.
Its more than that. Its about making money. For private corporations.
Why else would the TSA allow you to get special ID for a few hundred dollars to bypass security.. designed and maintained by a private company? Specially designed TSA approved bags.. designed by private companies. Not to mention the billions of dollars filtered through to private corporations for those expensive x-ray and other fancy security devices.
And they do shit all. I've flown twice in the last two years with a swiss army knife in my pocket without realizing it.
yeah, you know, 'cause when you have 50 programmers on a project, java l33tnesses like
Blah x = new Blah();
is so cool and easy to understand. and just forgetting about memory management completely is so efficient. and horizontal clustering is for wussies, if you need less than 8 gigs of memory on linux, it is because you're unl33t or because you obviously aren't using as many threads as you should.
now when you program in C you forget all that crap, you just code. need a bigger app? Abstract session management to central storage and add servers. add nodes a needed to keep performance. node dies? no problem, your IP load balancer takes it out of rotation.
Migrated from mysql to Oracle or DB2? no problem, you abstracted your DB layer, right?
Tired of Windows Server and want to run opensolaris, linux or OS X Server? no problem, you wrote everything POSIX, right? it's working.
wanna add more coders to your project? point 'em to the oxygen docs and let they read through the verbose (and thus self-explaining) code.
Compliers stop you from doing somthing stupid, and since you're scaling horizontally, service outages are absorbed by the network level. With your logging systems you can always tell what the program IS going to do in all situations, because your coding review standards force you to.
but you're too cool for C.
I dont normally feed trolls, but wow, everything has its place - and java's place is much smaller than some people seem to think it is
Given that many filesystems are designed specifically with the spinning magnetic disk in mind, what open source filesystems are out there that will work to the advantages of solid state storage? Has anyone started thinking about that one as something to address before the major switches start taking place?
Or... does solid state storage take care of those oddities in firmware with the whole automatic write leveling technology?
The fundamental cause of the trouble comes from C's "pointer=array" equivalence. That was a terrible mistake, borrowed from BCPL.
Borrowed? Sorry, I don't know much about programming languages, but I do know C. The whole "pointer=array" thing is bunk. Pointers are NOT arrays. You're misunderstanding whats happening. Pointers only point to memory locations. Arrays are only a different way of referencing the same memory locations. There are dozens of other ways to look at the same area.
The trouble is that the compiler knows neither which variables are arrays nor how big the arrays are. You can't even talk about arrays properly. I mean, of course,
int read(int fd, char* buf, size_t len);
That's just trouble waiting to happen. "read" has no information about how big "buf" is.
Actually, the compiler knows exactly how big buf is. Its the size of a pointer on that system. Of course, if you want to copy data into the memory space POINTED to by buf, then you should tell it how far to write. Thats what len is for.
C works how computers work. It is not a language that tries to hide it from you. If you want to code in C, you should understand this. Realize that in terms of CPU operations, having a language track every begining and end of every separately allocated memory space is very expensive. Try compiling a C app with the bounds checking GCC extensions sometime (its a separate gcc patch), and see how well your app performs while it is checking every single allocation and memory reference.
Oh, and before you say that the compiler should figure out if that happens, think about how much flexibility would be lost if every single allocation was static in size.
Actually, it would appear that Newline is a bunch of crooks. They did the same thing to Peter Jackson himself.
Article on it
So not only do they screw the Tolkien trust, but they also screw the guy who MADE the movie. Good job Newline, I have a feeling you may have a hard time attracting talent in the future.
Thank you.
Stories like this, and the various others I have heard since I involved myself in this have made it feel like one of the best things I've ever done. You give me the drive to continue.
I hope you'll come out, and perhaps be able to tell your story at one of the protests next month. It needs to be heard.
Easy. You talk to the people who've left it.
Voiceless
Thats one. There are hundreds, if not thousands, more. Including the niece of David Miscavish (the current leader of scientology).
Come on people, the information is out there. You can easily take a balanced view by READING the accounts of the hundreds of people who've been victimized. Look up Paulette Cooper. Shes still alive today to tell her story of being harassed and sued for 15 straight years.
Heres the rundown:
London, UK - around 500 people.
LA - around 500 people
Sydney, Australia - around 300 people.
Clearwater, Florida - around 250 people. This one is scientology headquarters.
New York - around 320 people
Boston - around 270 people
Atlanta - around 250 people. They called out the riot squad in full gear, with a helicopter. There was no incidents at all.
Washington DC - around 200 people.
Toronto - around 200 people.
In total, the estimates are around 8000 people worldwide. The aim was, of course, to get over 9000.
grip: i submitted details of these protests to slashdot twice before this took place, hoping we could get some of you folks out. *shakes fist at editor*
COME NEXT TIME - MARCH 15TH.