https://www.amazon.com/dp/B075WC3LZG/ref=cm_sw_r_cp_awdb_t1_fiupBb28ZM5DB

Obviously, not a solution for every case. But in many, many cases, these are all you need to stop the scourge of "Plugspreading". As an aside, if this term has not yet been co-opted by the adult community, clearly this post will be its genesis. I expect an entire category on pornhub within weeks!

This is just the chip design. We would still need ASUS, MSI, Gigabyte, Intel (I would LOL if they released a board for a competing chip), etc, to provide a working platform to integrate these into. A standard socket, PGA or LGA, or soldered on to each board. Maybe we'll see them in a littany of SoC or SBC designs first, that seems much more likely honestly.

If anyone has read the Manga all the way through, the parallels there are pretty obvious. Iron Jim gets the task of bringing it to the big screen it seems: http://www.imdb.com/title/tt0437086/?ref_=fn_al_tt_2

I read it all 20 years ago, so theres a lot I don't remember, but preserving and resurrecting consciousness (in the form of peoples brains-- or brains turned into FPGAs quite honestly) was a huge part of the series. At the time it really made me question what it meant to be human. It was the series that introduced me to the prospect of having multiple brains, something I had never even considered. Great Sci-Fi if you don't mind more than a touch of gore: https://en.wikipedia.org/wiki/Battle_Angel_Alita

I wrote this 17 years ago:

https://web.archive.org/web/20040301010936/http://darkaxis.com:80/devel/c/network/http/deepweb/deepweb.c

Got me in trouble with the Naval Surface Warfare center... it seems they had some sensitive stuff out on port 80 back then.. and I hit it at random.

Anyhow, I wish I would have kept going and developed it into a full fledged spider. There is so much content that never sees the light of day because it's not linked to a site with a high enough "page rank" for it to be deemed worth while. With the coming proliferation of cheap massive SSD's, it would be fun to revisit it. I had a dedicated T1 in my home at the time I was researching, so there was little fear of retribution from my "ISP", because they were also my employer, and this was the kind of thing I was expected to be proficient in. These days, I wonder how long you can run a spider from a residential connection before they terminate your access, lol.

Well said, and sadly true. Just towing the party line to keep the barge moving.. awards and all.. How can *anyone*, regardless of political affiliation, think that legalized deep packet inspection (Not just for the NSA now!) and QoS-based extortion are tantamount to freedom?! How doubly-fucked are the 4G (and soon 5G..) crowd going to be when their metered connections now require extra monthlies for the privilege of streaming the same shows we've all been watching forever, at the bit rate (and thus resolution) they were used to. We're right around the corner from escaping this shitstorm:

https://www.sciencealert.com/scientists-have-achieved-direct-counterfactual-quantum-communication-for-the-first-time

Imagine a mesh network of quantum routers, one in every home, directly communicating without the need for subsidizing "right of ways" or a god damned monthly bill that is on par with a decent car payment for many families in America. This is also most likely why the quantum router will be the most heavily regulated device in human history. It's going to be a fun century.

Orwell got so many things right in 1984, the only thing he really got wrong were the size of the screens...

Altavista was still the best search engine available at the time google was released. For the amount of conent, and lack of barriers to that content. Also, the search operators available. Being able to force the inclusion of a specific phrase or keyword while simultaneously excluding another, was revolutionary for search in the late 90's. Google's own search operators eventually surpassed Altavistas, and the amount of content they had indexed. For a while I went between the two as they produced wildy different results on the same search string. Results
these days seem so filtered, and you know the top results are paid for, even the so-called 'organic' results are endlessly gamed using botnets and for-pay services. I feel like search is ripe for a new revolution, and I can't wait to see who delivers the best alternative to the pay-to-win mess we have now.

Great catch here! It looks very much like someone at Level 3 screwed up the BGP tables introducing a much more specific /15 CIDR where a less specific /12 was already in place, which encapsulated a huge portion of Comcasts regional traffic and re-routed it through Level 3, which could not handle the load. Bonus points if anyone has the footage of the Level 3 tech getting flogged in the Noc ;)

Used it remotely before I ever installed it. Lots of vulnerable 1.3.x boxes floating around on Efnet/Dalnet/Undernet back in the mid-90's, with public IP addresses, in unlocked channels.. For a teenager with a lot of free time, it was a wonderland. 1st distro I installed at home was Slack 3.x, just the A, D, and N floppy sets. Got it dual booting with Win 3.1 on a 486 DX2/33MHz with 8MB of RAM. Kernel was 2.0.25, I was told on IRC that recompiling it and taking out all the drivers you don't use would speed it up. And on a 33MHz machine, it was true! Compiled 2.0.29 and got LILO to boot it, with the distribution kernel as a fall-back just in case. I removed the windows partition the next year and for the rest of the 90's and all of last decade I ran Linux on the desktop. WindowMaker was my WM of choice back then (a NeXTStep clone interface). I had a separate machine for gaming, but if Blizzard had released the WoW Linux client to the public, I probably wouldn't have. Tried it in Wine many times, and I hear it's actually pretty stable now, but that's all in the past for me. If Linux is ever going to 'win', it will be because OEMs like Dell/HP/Lenovo pre-install it. People getting a computer for the 1st time have no idea what an OS is, they use what they have been given. If we had a "Universal App Store" that was OS-agnostic (and populated with the software we actually use to run modern businesses) then Linux's sticker price might convince a few OEMs to jump ship. The "Microsoft Tax" is tolerated because that is where the majority of useful business software exists, tied to legacy applications in that environment. These days I work in a heterogenous environment with many different OSs, Linux is there as a firewall and a web server, as the kernel behind phones/tablets we use, and on the laptops we run Kali on for pentesting. We use the OS that matches the function, and I'm typing this on an iMac from 2008 because it was a free donation and it has a larger screen, lol. There will be so many OSs after Linux (ESXi was Linux before VMware optimized it as a hypervisor). We put so much time and so much code into it, why not start there to fork a new tree and try a new direction? I see Linux in 20 years as the great-grand-father of the OSs we'll all be arguing about then, just like UNIX/POSIX is now.

https://www.contextis.com/resources/blog/wap-just-happened-my-samsung-galaxy/

So, after thinking about this a little more, there is nothing preventing the Botnet operators from doing a DNS lookup and simply targeting the new IP address. However, that would let us weed out legitimate traffic from botnet traffic over enough iterations. ISPs could have a three strikes rule for clients. 1st time you attempt to contact an IP address on the DDoS target list, strike one, most "strike one traffic" is probably legit, people pressing F5 trying to reload the site, etc. Strike two, and you start to see exactly which addresses are following the DNS chain and propagating the attack, by strike three+ (if ISPs are reporting their "repeat offenders" to a central clearing house), you have a pretty decent picture of all the end nodes in the Botnet. You Null Route those, too, in a separate list. Same TTL expiration as the DDoS target list. When people call their ISPs to bitch, the tech on the other end notices the red flag on the account and asks the owner to kindly unplug their smart toothbrush (or whatever brain dead IoT device is being utilized) if they would like to have their internet turned back on. Avoiding false positives on Botnet membership would require the targeted site to put up some kind of "This site is under attack!" notice so people know to stay clear while the members of the Botnet are identified and blocked.

If we had a global registry of DDoS targets that we added new addresses to when the bandwidth of an attack broached limit X from number of sources Y (100gbps / 1million bots?), then we could require ISPs to run automated scripts that Null Route those addresses in the database for time period Z (1 day?) The Botnet gets rejected at the edge in those cases, but the end result is the same for the target, they have to move or wait. If you can get the move done fast enough (up on new IP addresses in an automated fashion within seconds, DNS propagation for those new addresses at the same rate), then there is no loss of service, and no profit for the operators of the Botnet. Or no fun if its "just for the Lulz". So the real problem with DDoS is the inherent lack of configuration speed in the current internet. Blocking IP addresses at the edge routers is a manual process and takes time. Bringing NIC cards up on new IP addresses or changing static NATs in firewalls is a manual process and takes times. Changing DNS records and allowing for propagation, etc, etc. So to beat DDoS, we need to have more automated systems in place for migrating services from one address to another. You destroy the perception that there was any effect from the flood, and you beat DDoS.

That was called Windows 3.x, and it worked very well. Every program had one (or a set) of *.ini files that governed the settings for that program. Need to start fresh? Delete the .ini file. Want to preserve your settings when a new version of a program comes out? Copy the .ini sections that mattered back into place. The registry hides SO much... and if it gets fucked up, pray you have a recent system restore point. If you combine all the advances in crypto with a decent revision control system like Git, .ini's could be secure and easy to work with in todays world. The UNIX world has had individual text based config files for 40+ years, and we keep improving things there. I feel like the change from config files to registry was about stopping "t3h p1rat3s!", and it didn't stop them at all..

IIRC, we were trying (my dad and I) to stay within a certain budget, and we had opted for an EISA (https://en.wikipedia.org/wiki/Extended_Industry_Standard_Architecture) video card with a whopping *1MB* of VRAM. So yes, the initial ram on that build was only 2MB =P Even after we went to 8MB I spent a lot of time setting up config.sys / autoexec.bat to run memmaker with just the right settings. I vaguely remember that you wanted as much free ram as possible in the initial 640KB range, and you could move some things into an area reserved for Monochrome displays to free up a little more. I kept that machine until 1997 (we were poor), and in the end it was dual booting Win 3.1 and Slackware 3.1. I remember kernel compiles on a 486, good god... I'm pretty sure the first one I did was 2.0.29, upgrading from 2.0.25. That was back when taking out all the modules that didn't apply to your hardware (stock kernels always support as much as they can) would net you a HUGE performance gain. Id software made the transition from Windows to Linux pretty easy, as Doom (and more importantly Quake!) ran just fine =) SVGALib for the win.