Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Fun (Score 5, Insightful) 449

I have thought the same thing.

Of course there are a few fundamental differences between then and now from my point of view:

1. I was a young teen and had tons of time (and energy) on my hands to play with these things.
2. Everything you learned you figured out on your own or as a group share with close friends, supplemented with a few manuals and magazines.
3. The hardware was finite enough you could basically learn everything from the low level access to the hardware to all the software features (basic or machine language). You could literally learn what every location in IO or memory did (53281 anyone??).
4. With a few days or at most weeks time with even modest skill levels you could put together something that could "wow" your friends and perhaps even non-computer family members.
5. Atari / TI / Commodore computer overnight parties where a bunch of us get together to compete to show off the best games etc. in an attempt to prove we had the best platform.

Today we have a lot more learning resources out there, and the hardware is much more powerful but in my mind it just isn't as fun. There is certainly no way to whip up something that would "wow" anyone. It's more a tool now than a fun hobby.

Comment Multipass (Score 2) 285

Almost sounds to me like they have switched to multiple pass encoding, rather than a fixed quality/bandwidth setting.

"The new system will encode from the raw source material more intelligently, considering whether or not the material itself can really benefit from higher bit-rates, or whether identical quality can be maintained with less space and bandwidth."

Comment Re:Solution (Score 1) 90

When you are talking these large DDOSs that generate 60Gb of data, you are talking millions of hosts. You need to get them blocked upstream from yourself, otherwise you are still getting the flood and things will crawl on all of your services irregardless. However upstream blocking is generally not source address based, just destination -- sure we will blackhole all packets destined to _YOUR_ server. Therefore you are still down. Yes, you can move the target but the DDOS will just follow.

If you deal with that problem and they are also generating traffic on your HTTPS port to tie up your services, how do you differentiate DDOS traffic from the normal user who is trying to connect? Sure, you can examine the activity of each connection but there is no time for that when you have thousands and thousands coming in per second.

It's like playing whack-a-mole but blindfolded and your wife has her head in there so you better watch out!

The only way to deal with this is to use raw processing and huge network pipes against it, which is what the protection services provide.

Slashdot Top Deals

"If it's not loud, it doesn't work!" -- Blank Reg, from "Max Headroom"