No matter how much effort goes into securing the transport layer, it means absolutely nothing if the end nodes themselves are insecure. Something as simple as a SQL injection or remote code execution could easily deanonymize an end node. With how quickly many of those sites sprung up, one of the current theories is lack of security on the end-points themselves is what was attacked, not the Tor network itself.
Since I was able to get off a wise ass crack joke for a first post, let me follow it up with something actually insightful for you other readers out there.
What makes a "good" or "bad" boss anyways? Well, this article is one that I've always lived by, and it explains things quite well for both us techies and for those who are not of the tech mindset and skill set.
NO SHIT. We needed a paper to tell us what we already knew? Damn, why didn't I write that paper... Here goes.
"INCOMPETENT BOSSES ARE THE LEADING CAUSE OF CAPSLOCK RAGE ON THE INTERNET"
While I'm sitting here reading about other people bitching about abstraction libraries such as jQuery, my first thought was actually about testing processes.
Pretty much everywhere I look online, projects are FLOODED with automated testing tools to ensure their code works. And sure enough, every bug that I submit has an "automated test" that didn't test that particular condition. Developers are relying more upon these testing tools and less upon actually USING their own services they're developing to ensure they work properly.
A great example: a recent bug I had to file was brain dead simple. File opening ignored current working directory, so if you changed directories, the file open command would still assume you're in the base directory. Why wasn't this caught? All of their file handling automated testing routines ONLY checked absolute paths, none checked relative paths. On top of that, when they finally did add relative path testing after my bug report, they only added it as relative to the base path, and not testing against current working directory.
Now, let's think about this for a second. How long has the concept of changing directories been around? While most of us will go "oh, DUH!" to the bug mentioned above, newer developers may simply not be in that same mindset, because they're not actively traversing their filesystems themselves. The automated toolkits are doing all that work for them, leaving the developers less experienced in this area, and thus less forethought when building the next generation of tools to test these exact sorts of issues. It is a downward spiral.
Yes, because this is SUCH a problem on sites like Twitter... where if a user feels a particular account is flooding their feed too much, they are just a click or two away from an "unfollow" button.
I don't need a computer telling me that I've had too much information and to restrict how often new content can appear on my feed, I'm quite capable of doing this myself!
Progressive technological evolution, adding a new finger every year!
I thought this article would be about the sound chamber inside of the Amazon Echo, now I'm disapointed
Hey, remember back when Sony had the big PS4 announcement, and they brought Blizzard on stage. During this time, Blizzard said they would be showcasing a brand new IP at the following PAX East... and it turned out to be a fucking card game.
So is this what they were SUPPOSED to showcase a year and a half ago?
And in five years, we'll all be using a system where we wave our hands around in the air to do gestures to control our computers!
So, a file server service running on top of OpenWRT with a HTTP capture portal? I remember doing this with a WRT54G way back in the day...
Now if only we could get general USB storage instead of this MTP bullshit back without having to root the phone and download some random apps to make it work.
MTP is slow as hell, especially when dealing with thousands of files (directory listings alone take several minutes). It also requires specific OS support.
Yeah, I get that MTP is supported on Windows/Mac/Linux, but this isn't always where we're working. I used to use my phone in place of carrying around a USB thumb drive for system servicing. I had my Micro SD card loaded up with things like NIC drivers for Windows XP/Vista/7 (once it has NIC, it generally has net to download the rest of the drivers). It had patches for server systems that didn't have net access. It even had my XBox360 gamer profile on it.
ALL of these have since been lost and had to result in going back to carrying around an extra device or two just to accomplish the same task that was possible just a few years ago with a cell phone and USB cable.
I stopped buying DRMed products after purchasing Unreal Tournament 2004 a decade ago. That game had two releases: the normal release (7 CDs) or a special collectors edition that shipped on a DVD and came with a ton of bonuses. This was one of the first big commercial titles to ship on DVD instead, and was supposed to be a super simple install process. The game was supposed to install faster, and no disc swapping during install! Clean and simple, right?
Well, the DRM that existed on the DVD version was absolutely broken. After a few hundred (maybe even a few thousand?) of us went to the Epic forums to bitch about the issue, they finally admitted that the errors occurring during install were related to the DRM, a bug which didn't exist in the CD copy. Yes, that's right. Only those of us that paid the premium to purchase the collectors addition were screwed in our asses due to the DRM.
After a few days, there was no fix, so a buddy of mine brought over a pirated copy he downloaded of the 'net, so I could play the game.
The game was still mass pirated. Those of us who legitimately purchased it were totally screwed over. This really helped the company, so I've yet to purchase any more of their games on disc since then, and never again will.
BASIC evolved, too. Tools like Visual Basic (which had a WYSIWYG form editor) emerged. And then even that evolved again too into VBA (the scripting language for Microsoft Office). Yeah, I get the security bullshit with their implementation, but that doesn't deny the fact that it was a quick, simple, and extremely powerful tool for non software engineers to get in there and build some tools needed to get the day's job done. Especially with Excel, the ability to just hit "record macro", and then see the resulting code it generated as you preformed operations manually on a spreadsheet. Then analyse this code, and modify it to meet one's needs. This was an amazing way to get someone introduced to programming, as they can preform functions manually, and then get a listing of commands, they could then visualize the code back into those execution steps.
I always thought that WIMP (Windows IIS MsSQL PHP) was the opposite of LAMP (Linux Apache MySQL PHP)?
My #1 complaint about that BS article every time I see it pop up is this: there is a few false assumptions in it. Firstly, "Computer Science" isn't the ONLY school route to teach computer programming. It is also offered under the label of "Information Technology", or as elective classes under other fields such as "Network Administration" or "Database Administration" - And the other assumption is that SCHOOLING is the only way to learn things. Pretty sure just about everyone here on Slashdot can easily agree that they've learned a hell of a lot more tech either on the job or on their own than they could have ever imagined learning in a classroom environment.
8 Catfish = 1 Octo-puss
