- Venetian Snares - Mutant Cunt Sniffer
- Biosphere - The Things I tell You
- edIT - More Lazers
- Coldcut - Everything Is Under Control
- Kid 606 - She's=Defective
- Xanopticon -Constant
- Zazen Boys - Himitsu Girl's Top Secret
- Stendeck - Run Amok
- Goddess in the Morning - Flower Crown
- Kashiwa Daisuke - Requiem
- Ryoji Ikeda - Dissonanz
- Cycheouts Ghost - Kingdom of Dreams
- Gocoo - Celebration
- Middle 9 - Island Pull Out
- Worriedaboutsatan - You're in My Thoughts
- Dalek - Asylum
- Teeth of the Sea - Red Soil
- Royksopp - Eple
- Hauschka - No Sleep
- Tunturia - Silence Is Consent
- The Ascent of Everest - As the City Burned
◊ saw the other approaching, ghostly light cascading down extended tendrils. ◊ signaled back assent, a complex pattern of blue and green flickering through ◊'s own extents. The two worked with the spiraling air currents, transferring processing to their aft sections to take advantage of convection.
In time they grew closer, and each flashed indications of intent, identification, internal structure. ◊ spread its tendrils on the side of the other, and observed the other doing the same. Currents and light propulsion brought them together, thin, luminous tendrils intertwining, Thought-light flickered, brightening on the overlapping tenders as they aligned, closed, and, at last, *connected*.
◊'s thoughts spread, traversing familiar but alien paths. Its mind stretched, widened, split and combined, moving across the other's mind-net and returning different, better. The other's mind passed through ◊'s, ideas, memories, and plans colliding and merging where they crossed the same mind-path.
For a brief moment, there was no ◊ or the other, but something else, grand and new. And then the currents carried them apart, the connection broke, and they drifted apart, forever changed, carrying a small part of the other.
Internet hacking savants under the name 'Anonymous (Anon)' disabled multiple government and corporate websites including the Department of Justice, the FBI, Universal Music and more Thursday...That's from The Lantern. Those websites were disabled by Low Orbit Ion Cannon, or High Orbit Ion Cannon, simple tools which can be used by anyone with enough knowledge to load a web page. Thousands of people took part in the Distributed Denial of Service attacks that actually knocked those websites offline. It takes no skill to participate in such activities. James Garcia obviously has no real grasp of his subject matter. Those tools are available in numerous locations, to anyone.
As requested, what follows is a list of email addresses for every Teachta Dála in Ireland's Parliament, beginning with long time representative Gerry Adams, as per alphabetical:
firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org,*Northern Ireland does not have any representation in the Oireachtas. This information was provided by CabinCr3w and #OpIreland. It would have been easier to just tell you that every TD uses @oireachtas.ie, but shortened names made a full list necessary (e.g. pat.rabbitte for Patrick Rabbitte). Good luck in your endeavors, and here's to hoping Ireland's parliamentarians have a higher opinion of their constituents than do some of our House members.
email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com,
firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com
After the Blackout: LOIC
Anonymous is bombarding the DoJ, RIAA and Universal Music, and promises have been made that campaign raising abilities of SOPA supporting Democrats will be targeted in the near future. Anonymous has asked that opponents of SOPA not inclined to use LoIC follow #StopSOPA on Twitter and retweet all tweets. (see pic)
This comes on the heels of a unilateral takedown of Megaupload earlier.
Justice dot gov has been down for at least half an hour. Mike Masnick at TechDirt made a very good point earlier today: Democrats may think young people aren't paying attention to this issue, but they are WRONG. If they aren't careful they are going to alienate an entire generation of potential supporters with their asinine authoritarianism, an authoritarianism that is hugely invalid because of the very high level of ignorance among Congressmen concerning the technical aspects of these bills. [writer stops before rage causes temporary blindness again]
We won, for now, but only against SOPA/PIPA. OPEN is next and is very much alive. The fight is just beginning.
The following is another relic:
STOP PIPA (Senate 968) & SOPA (HR 3261)
Imagine a world without Wikipedia, Google, Craigslist, multi-channels [your favorite sites here]...
News Corp, RIAA, MPAA, Nike, Sony, Comcast, VISA & others want to make that world your reality.
80 Members of Congress are in their sway, 30 against, the rest undecided or undeclared.
Please take a minute to tell your Members of Congress you OPPOSE PIPA & SOPA
The sweetness deepens: Operating benchmarks for Debian kFreeBSD are phenomenally inviting. H264 video encoding is faster on AMD64 kFreeBSD than on any other kernel. Benchmark tests show the kernel chalks up almost a frame and a half per second more than in normal Debian 64 bit operations.
That's not as impressive as the 23% improvement in speed over straight Linux during 7zip compression. kFreeBSD wasn't the top performer in every test. It came in second on Gzip and LZMA compression, and in GnuPG encryption. All these tests were reported by Phoronix, and are slightly dated. It would be nice to see a bleeding edge redux of the study because this one was damned impressive and kernels generally improve over time.
There are other nice traits of kFreeBSD. Here's one: Further reading has shown that BSD-loyal developers tend to merge new features rather than create a distribution fork. Having to commit to development course deviations based on progress that could potentially move the system away from improvements in other areas has always been a troublesome aspect of Linux.
Further. A positive quality of FreeBSD which probably would not affect my systems anytime soon is the hardware support advantage FreeBSD has over Linux with a couple of companies. FreeBSD does include some proprietary binary in its hardware driver source code. Agreements have been made in the past to allow proprietary closed code into the FreeBSD kernel to enable a closer working relationship with some hardware manufacturers. That code has been excluded from the Debian_GNU/kFreeBSD release in order to keep it 100% compliant with FOSS standards, but the working relationship still exists. Some hardware may be functional under this kernel that may not be supported under Linux, or at least not supported as quickly. [It is irresponsible and disrespectful to say that Linux reverse engineering and driver hacking could ever entirely fail to support some form of hardware, considering how hard the developers work and the seemingly miraculous things they have pulled off in the past, hence the italics.]
I just had a conversation a few days ago about how much I missed Debian, brought on by the complications I encountered during the aborted migration to BSD. If I had known there was a Linux/BSD hybrid before this week I would have been running it already. There's only one other thing on the planet that gets me as excited as I am right now, and that's sex. An-tici ... pation!
ZFS by itself will run with as little as 1 gb RAM, but performs optimally with 4 gb and upward. The way ZFS has been linked into PC-BSD makes 4 gb a requirement. 3.25 causes prefetch disable. Working around that problem hovers on the edge of the catastrophic. Booting into the system can only be accomplished by using BIOS to limit RAM to an OS install 256 mb setting, which isn't really enough to run KDE in PC-BSD. The system makes a valiant effort to work, so at least it dies gallantly as it chokes and collapses.
For me using ZFS was one of the selling points for making the switch to BSD. The idea of a file system that detects and self-corrects file integrity problems makes my mouth water. Having been through some insanely painful data loss debacles because of things like electrical current anomalies, learning about ZFS brought an actual tear to my eye. It sounds so beautiful, and, realistically, it is as wonderful as it sounds. Unfortunately my current system doesn't meet the criteria.
Anybody who does have the requirements should consider using ZFS. Keep in mind that I only decided on PC-BSD out of laziness. Partitioning into a ZFS format can be done with FreeBSD, with a certain amount of hassle. Webmasters and server guardians are migrating to it enthusiastically, heedless of the extra effort required to implement the file system using back door methods. I simply have not done so yet. And it's very simple to migrate during a new install of PC-BSD 9.
PC-BSD has a couple of other sweet points. The ease of file encryption is staggering to someone like me, who has gone through all the partition mounting and unmounting necessary to use file encryption with Linux. Encrypting user data is automated during install, and entering one's password at a prompt during boot completely takes care of enacting usability.
PC-BSD also sports a bubbling test tube background during login. Ahh, science. It may sound like I'm scraping the bottom of the barrel for positive characteristics of the operating system, but mad scientist lab nostalgia is its own brand of awesome. Yeah, though, unfortunately PC-BSD is about to get scrapped because without ZFS there aren't enough checks in the pros category for it to stay. Back to the drawing board!
One more thing should be mentioned. Booting into the system using the OS install RAM limiter caused the computer to sound like an airplane taking off. That's a huge red "x" in the cons column. It never sounded like it was going to explode before. It sounded bad, people, it sounded bad. That experience comes on the heels of reading this quote from a BSD developer: "Sometimes hardware damage is a good thing." Uh, no.
[I am not a computer expert, merely have a lot of experience and a good background. I am not absolutely sure as to the reason why PC-BSD exhibited such problems. I simply hazarded an educated guess.]
I-yie-yie kawaii - Image for tldr:
After a couple of days tinkering with FreeBSD's latest stable release I decided to chunk it and do an install from PC-BSD. That decision primarily resulted because using ZFS systemwide can be implemented in FreeBSD, but it's a pain in the ass to get it in place. PC-BSD 9.0 Isotope allows ZFS partitioning from the very beginning, as opposed to the default UFS. After much reading, passing up ZFS while switching to BSD seemed like buying a new Corvette body with an old engine. A lot of people hoped that FreeBSD 9.0 would enable ZFS at installation, but it didn't. In fact, it became more difficult to implement because the old method, using fixit, is no longer available.
Not only does PC-BSD support ZFS installation, it uses a graphical installation utility. Having brushed up on installing all packages and enabling a desktop manager from the command line, it became easy to remember just how time consuming the process really is. For me switching over to a new operating system means upwards of four installations, the tedium I would face became tangible. The brevity of the primary requisite command, pkg_add -r packagename, does not cover all of the other steps that are automated by a graphical installer. Bsdinstall made FreeBSD is definitely a lot simpler than the old sysinstall menu, but that's because it completely sidesteps package installation.
The downside to using PC-BSD is that the community is smaller, so any problems that might arise will have to be solved by a much smaller group of people. It's not that the support at pcbsd.ord lacks in any way, but fewer people means greater demands on those who are available. I personally hope to never need support, but in case anybody out there wants to try PC-BSD they should know what they are getting into.
The first step to installation is getting the medium. PC-BSD compact disc and DVD images are available here. Once you've downloaded the iso it needs to be burned to a blank disc. If you're using Windows that means you need Nero, or a program much like it. In Linux you'll need K3B or Brassero. Once it's burned you're ready to boot into install mode. Switching over to BSD means using a file system that's different from Windows and Linux, so any data you have on the target hard drive will be lost during formatting and partitioning.
It is highly recommended that you read up on installing and using BSD before jumping in. Not only does it use a different file system, but the organization is different. This operating system is extraordinarily stable and versatile for web servers and on machines used for data transmission and retrieval. You can still do everything on BSD that's done on Linux and Windows, it just takes a little tweaking. Conversely, BSD does things that would take a lot of work to do from Linux and Windows. BSD is well suited to the use of Nmap and remote shell operations. Another fine example is that virtual honeypots work best from BSD.
After I use PC-BSD for a couple of weeks I'll report back about it. It's based on FreeBSD to the extent that it's almost a clone. You'll hear anything out of the ordinary about it, positive or negative, and about ordinary excellence as well.
The original post follows. I figured it wouldn't hurt to illustrate the difference in my mindset between then and now. The cutesy, matter-of-fact sarcasm sort of makes me want to barf. "Too Easy!:"
Operating system switched from openSuSE 12.1 to FreeBSD 9.0. Essentially I was tired of having an operating system that no longer required any advanced open source system knowledge whatsoever, and by that I mean command line knowledge. I was not disappointed. FreeBSD immediately failed to install on first try, hung up on the ACPI driver, which evidently is sometimes shaky.
Slight headache began to form after disabling ACPI only to have install hang up again a mere two seconds farther down the line. Fixing the failure of the BIOS to assign an IRQ spot proved a lot more difficult. Backed up, regrouped. Still hadn't made it to the SysInstall screen. Turned off all but 256 mbs of RAM of 3 gb. Still failed. Turned ACPI back on, install kicked in, made it to first screen.
Installed hostname, minimal packages [doc, game, man, ports, src], boot daemons, configured IPv4, IPv6, DHCP, added user, added user to groups, set password, then exited base install to get to package installation. That was when having a CD instead of a DVD became a huge handicap. Everything has to be installed from the shell without the DVD. Wouldn't it have been funny if I had been installing to the only available computer in the house and the Internet wasn't available without it? No, it would not be funny, because that's what happened. It was not funny. It was not funny at all, but could have been so much worse.
Many long pages of hand written instructions tediously transcribed to make the installation process easy in the absence of Internet access became completely worthless due to the implementation of bsdinstall over sysinstall. Luckily I just had to switch wires to use Linux again. Detiled installation instructions can be found at Freebsd.org.
Back in the day every Linux distribution upgrade of my operating system required manually configuring KDM because of the fancy schmancy Nvidia graphics. In the case of FreeBSD, dbus and hald had to be added to rc.conf and started, and .xinitrc to start kde4 had to be added. Init 6 and startx enabled the graphical desktop environment people like me use. I would say "people like me" means those whose time is too valuable to waste on doing everything from the command line, but I'll be honest. I'm just lazy, so I like to use windows and widgets and buttons and a mouse.
Anyway, if you ever get bored with your operating system, install FreeBSD. If it doesn't install properly right away you're bound to get a minimum of 4 or 5 hours out of the experience. The installation could get nearly FUBAR, like mine did, in which case you could easily burn 6-7 hours on the install. Ask yourself, is using your computer too easy?
Kurt Havelock completely dropped the ball during final exams for Batshit Insane Manifesto Distribution 101. Due to his failure to target specific individuals instead of just corporations alongside his threats to blow up every airplane that "looked at him wrong," charges against him have been dropped. Justice has been miscarried! Or has it...
This is a victory for the NDAA. The indefinite detention law will apply to someone. It's just a matter of time before Havelock releases the manifesto's second draft. Doing away with guaranteed protections of the law for United States citizens was a good idea after all. We can either have habeas corpus or we can have safety. That's the bottom line. Just ask NDAA supporters. Meanwhile, Havelock fans have a message for their guy: "Don't give up! We know you can prove you're dangerously crazy!"
Hana Beshara received a sentence of two years in prison for making pirated movies and television shows available for download. Evidently she never read any of those disclaimers from tracker sites that say "no content is hosted on our servers." Ninja Video's Queen Phara went the extra distance for users of her service and hosted everything. Authorities may have become suspicious because of the website's giant logo that read "Stolen Stuff Here."
Wait... oh no! Terms of her sentencing says she can't have any computers at her residence. Well, the choice is clear. Beshara can't stay at my place when she gets out; the computers are staying.
Warning: The following game has hentai sex scenes featuring handicapped, crippled people. Also, this post was so not fair. The game is brimming with sensitivity. If the players who keep falling in love with the characters are any measure, the game is overly sensitive. Biggest complaint heard so far: Can't play more than once, feels like cheating on the character from the first run through. That's why I say the game makes them basket cases.
Do you have no life? Katawa Shoujo! Do you have a life and want to get rid of it? Katawa Shoujo! Extra brain cells? Missing socks? Racing thoughts and voices in your head? Katawa Shoujo! Katawa Shoujo! Katawa Shoujo!
[Note: Author would not play the game for any amount of money, just gets a good laugh when people's lives are ruined. Don't tell anyone the game turns normal people into basket cases. It's a secret.]
Having a hard time working up the nerve to change header image. It's tough to just discard it. Spent like no time on this 5cm image, a minute or two getting it and getting it into png. That doesn't rep it well to head the site like the hours and hours spent on the current header image.
Take this, lawsuit happy association Internet goons: File sharing is now an official religion. It's currently only recognized in Sweden, but practitioners are everywhere. We don't want peyote, just to share knowledge. Can't wait until this gets to SCotUS so Bush appointees can empty the bile pouches in their throats against it. You have to sing hymns, you poor bastards. We sing Rush (well, at times). *__*
"We weren't really sure what viruses were, or how to cripple Norton and Symantec, but then we got this stolen source code." Source code for the corporations anti-virus software was stolen this week. Symantec was so all over security they found out someone got root when their code was released, not because they detected it. Thank goodness for them Sec exploits didn't happen without a release. "Credit cards or it didn't happen" did not apply in this case, but you Windows users who pay hefty fees for Norton should be sweating balls over this.
Anonymous: "This attention is relevant to my interests. Can be famous tiem nao?" Online hactivists look around and realize they have the world's attention. Suddenly the movement as they envisioned it is a huge success. Some just don't know what to do with themselves, don't see the massive amount of danger and work involved and ahead. Criminal genius (pfft) of the morning: jargon7.
Live Out Doors
There's a business bearing the name J Day in the middle of it. Thank God it was in Bucky Larson and not one of the gaggle of worthless horror movies that come out every year. Seeing that was no pleasure, however. Considering how much differently things may have gone down for a writer with those letters in his name had the publish button not been so easy to hit, that scene felt like a knife in the stomach. Thank God all of my plans for success aimed at posthumous recognition. Having a name similar to one on a marquee in Bucky Larson is so far my claim to fame.
To be very honest this movie may be funny as hell to some people. It's impossible for a person such as myself to know. I couldn't sit through the entire thing. Whereas little of what I write makes it to the public anymore, shamefully I don't even save most of it, I do a hell of a lot of it. I watched 45 minutes of the movie and went back to typing, because I knew I could get laughs out of that. Yet despite all that negativity, overall, seeing Ricci in a different kind of role made Bucky Larson worth the time I spent on it.
This version of Chapter Seventeen will likely never reach the completed work, just as the last one is also gone forever. It went too far in the ghastly direction. This title was chosen because I intend to wash my hands of it the way it now stands, just as most people I know will. It's too out of place with the rest of the content. Have a lot of very good ideas along this storyline, though, so there will be salvaging. [the work continues to pile up, book should be called Set's Back]
- Freedom Box: http://wiki.debian.org/freedombox
The list came from Cryptome. I had a great many of the sites bookmarked already, but can not take credit for compiling the entire thing. Would have mentioned this sooner, but find it bothersome linking to the same site repeatedly.
[Personal drivel moved to "Comments."]