Archive for the ‘Tech’ Category

 

WordPress SFTP

Tuesday, June 16th, 2009

Note: This post has been superseded by a newer post. Read it here.

wordpress-logoI don’t like to use FTP at all when I can help it. It’s an old protocol and doesn’t hold up in regards to security. I could use FTPS, which is a Secure Sockets Layer over FTP, requiring a key exchange, but frankly, that sounds like too much work for me. Since I already use SSH and SSH has file transfer capability, I usually use that to manage things. It’s commonly called SFTP. Unfortunately, this breaks many apps that expect you to be using FTP, such as WordPress.

Little known to me was that this wasn’t the fault of WordPress; those glorious developers had already added ssh file transfer support to it some time ago. What was lacking was communication between PHP and SSH. When I researched online, I found instructions on how to get them talking to each other, which kicks in the SFTP support in WordPress. I’ll detail them here for reference. (Note, this is on Ubuntu Hardy, and I’m using Apache 2 and PHP5.)

user@computer:~$ sudo apt-get install libssh2-1-dev php-pear
user@computer:~$ sudo pecl install -f ssh2
user@computer:~$ sudo nano /etc/php5/apache2/php.ini

Find the section titled “Dynamic Extensions” and below, add:

extension=ssh2.so

Save it and exit, and then just do an Apache restart.

thanks to [Kevin van Zonneveld]

Project Upstream

Tuesday, May 5th, 2009

Project Upstream LogoEarlier today I got a random message from xenophobiccoho on AIM. Something along the lines of “Politicians kissing babies… how much tongue is too much?“. I, naturally, am unfazed by such a question from a random person, having done quite a bit of trolling myself. Unfortunately, I missed the message by a couple of hours, or I would have answered the query. I remembered getting a similar message at some point in the past, from a *trout, so I figured I’d look up this screen name and see what info traces I could find on the net. What I found was way stranger and awesomer than I could have ever imagined.

It turns out they’re actually some sort of fish bot network. That’s fish as in the thing that swims in the water, not so much the malicious hacker kind. There’s a ton of them (names here), usually ending with *coho, *trout, and *salmon. It’s something called Project Upstream. From their web page:

“Project Upstream is an organization dedicated to promoting social ideals through the use of exciting new technology. Our most well-known service is our swarm of robotic fish, which connects AIM users to each other. Robotic fish connections occur spontaneously, and also by request.”

Their mischievous method is they will message two people at random, pulling names from Google, twitter, digg, etc.. They’ll act as a middleman, disguising each chat participant’s screen name from one another, basically enticing them to talk to each other randomly. Both users will usually cluelessly think the other has messaged them, and most of the time respond accordingly to that. However, you might also end up talking to a more knowledgeable user, as you can request your own fish. Chat messages are sometimes modified with a pirate theme, or old tymey english, or other variants. You can opt out of the program by sending a message containing $optout to one of the bots.

To me, it seems like a Discordian version of the Omegle project. Also, it’s a great social experiment and good natured fun all around. Good luck little fishies!

[project upstream] [request a fish] [wikipedia] | via [nixie pixel]

Frist Psot!

Friday, May 1st, 2009
screenshot of my "d" issue

screenshot of my "d" issue

WordPress is crazy weird. I had this problem when I set up this server, where I was trying to have the domains switch from looking like “domain.com” and force the addition of www, to make it look like “www.domain.com”. I’ve done this before and it’s generally pretty easy. Little did I know, but WordPress seems to set itself up the opposite way. I spent a good part of the day wrecking my Apache configuration before I realized that it was a setting in the WordPress admin panel screwing with me the whole time.

Also, I noticed the Helvetica I have installed in Ubuntu has some weird dropped “d” thing going on. Quite interesting really.