You're probably not going to make anything close to what you're using, but if you're looking to build something more modest, that's definitely possible. It really depends on what your goal is, and how advanced of parts you're willing to accept as a starting point. Ben Eater (https://eater.net/) has a guide on building an 8bit computer from low level gates. It's a really good basis to be able to build some primitive devices that would be capable of something a little more advanced. I'm building a 16 bit version, with a display and keyboard. If one was interested, they could definitely build off something like this, adding encryption and a network interface that would allow them a fairly trustworthy device. Another approach that you could take is auditing the devices you use. There are guides on how to go from XRays of chips to decoding them. Ken Shirriff is a ninja at this, and I HIGHLY recommend his talk: https://www.youtube.com/watch?...

"this requires leaving childish tantrums, abusive language, and toxic environments behind."

"this is more important than the coddling of a whiny child who has never reached the emotional maturity to treat people decently."

These two statements from the author seem at odds with each other.

I think the whole thing is a misnomer. Neither the US nor the UN *can* control the internet. The more any entity tries to squeeze the internet, the more virtual darknets will appear on it, outside the reach of those entities. That being said, they cannot achieve any of the goals that prevent bad behavior on the internet... The argument is parallel to the one regarding making guns or drugs or other substances illegal. You cannot stop criminals from getting access to these things, you can only stop honest people from getting access to them. You cannot stop criminal use of the internet, only honest use of it.

not sure if you saw my reply elsewhere, but there's an epic specific build of connectbot that you might enjoy here: http://mobile.slashdot.org/comments.pl?sid=1938638&cid=34776884

I like my samsung Epic for it. There's a version of connectbot built with mappings for that particular phone at http://forum.xda-developers.com/showthread.php?t=813176 that adds support for just about every key you need--control, escape, etc. I've used vi on it pretty comfortably.

Ah... Well maybe I can convince you that it's not all bad. It doesn't seek to limit what you as a manufacturer, or retailer want to sell your items for. You are free to act independently and price it at whatever point you'd like. The only time the law comes into play is to thwart anti-competitive behavior--where all of the vendors get together and agree on a minimum price for an item... thereby defeating open market competition and acting in the same vein as a monopoly.

While you may not agree with the fact that it is government meddling in what seems it as though it should be the rights of the companies to do what they want with their prices; if it weren't for these laws, EVERY industry would do this, and the net effect would be very harmful to the economy as a whole, and would devastate the quality of living for all but the upper class.

It has nothing to do with the pricing of the item, and everything to do with the back-room dealing to defeat the competitive benefits of capitalism.

I think you're confused on what the price fixing law is about. The item does not have to be a necessity in order for them to illegally fix the price of it.

Unless of course you understand it, and you just don't agree with it... in which case you should probably make that more clear.

It's not at all well structured. It could have been laid out better without being OO, but going OO would definitely help. There is a complete lack of isolation, interfaces are pretty much defined by giving modules access to the entire core, which is a cop out for interface design that puts the entire burden of making modules work together on the module writers and moreso on the site owners. If the module API isolated internals and only made available methods that would allow customization without incompatibility (an interface that by definition defined compatibility between modules), I'd have more respect for it... but this is just the one thing that jumped out at me right away. The code is garbage all the way through. It makes heavy use of globals, and other magic that you just have to know about... the code is definitely not self-documenting. There's no separation of view, logic, and database access... queries are spread across everywhere. Files are thousands of lines long, with no clear separation of ownership of tasks. Methods are sometimes very long, doing 15 completely different things themselves instead of being responsible for only one thing. The same chunks of code are repeated throughout many methods due to poor abstraction.

It's a 2 letter english word. If you want to be able to claim someone is ripping off your name, be more creative. There are only 676 combinations of two letters, 101 of which are words in the english language, about 90% of which you've probably never heard of unless you play scrabble (things like "Ar" which is apparently how you spell the letter "R"). I will mention though, that it's a dumb assed name for a programming language. Name it something that will allow me to search the web for it in a reasonable manner.

Agreed a thousand times over. I really don't see how a community as geeky as slashdot can take drupal seriously. I get it when other sites dominated by the non-techies see drupal and think, hey that seems to work pretty well... but seriously open up the fucking source code and look at it.

I never give out references unless I've already interviewed for a position and I liked it. I just tell them that I'd be happy to give them references once we get to that stage, but my references are very busy people and they can't be bothered by every headhunting firm that wants to submit me for some position. I also setup the time that they are allowed to call, fitting both my reference's schedule and their schedule. It sets the tone that these aren't people that they can call at will.

I can tell you that having dealt with headhunters from both sides, as an employee, and as the person doing the hiring, I hate the bad ones no less regardless of my current role. I have quit good jobs because the contracting company I was working through were being jackasses. I hated to do it, but it had to be done. The problem from the interviewers side is, even if they like you, you've pointed out that the contracting company misrepresented you to them. That means that the contracting company is disreputable, and they likely won't want to do business with them anymore. If they hire you, they have to continue to do business with them, and deal with potential issues that will arise between them and the contracting company, and you and the contracting company. Unfortunately, they typically can't just circumvent the contracting company at this stage, so you might not get the job, simply because they don't like the contracting company. The two of you get hired or passed up as a team, so you need to work as a team. They need to understand that if they place you somewhere you're not happy, it won't last, so they're better off putting you somewhere you're going to be happy, and to do that, it involves working together and not lying about things to either side. As a side note, I tell every headhunter before they submit me to any job that they are not permitted to change my resume in any way. I've never had them say no to that request, however, they have gone ahead and changed it once, in which case I informed them I was no longer interested in the position. Contracting companies/headhunters work for you, which you seem to get, now the second part you need to get is that there's a million of them out there, and they're all fighting over you and the positions, they aren't in a position to pull that kind of crap, and you should be sure to let them know.

Someone tell me exactly how having an iphone app that shows you where all the 12yo's that posted nude pictures of themselves on facebook/myspace is going to protect the children, please?

Fork php to change the namespace separator :)

You made a much wiser decision in going with perl. You have virtually no risk of an update coming out that breaks backwards compatibility.