Tag: website

Large Files Don’t Move Well

The internet is great for small files. Email, Twitter, Tumblr. When we make webpages, we push to make them lean and mean. So what happens when you have a 200 meg video you need to send out to local news outlets?

The best way is to toss it on a USB drive. I have two in my purse at most times (one’s a novelty R2-D2 my friend sent as a thank you, I keep all my PDFs for software on it). But wait, you say, it’s 2012. Why can’t I use something else?

The problem is that the methods by which we can transfer large files aren’t, generally, user friendly. I mean, that comic there on the left is pretty much why it sucks. Click on the picture to see it bigger. The only think Randall didn’t list was Torrent, which I love for how it handles files, but it’s really not ‘non-nerd’ friendly to set up. To use, it’s easy, but making a torrent, distributing it, and seeding it, takes time.

A friend of mine suggested HFS which stands for HTTP File Server. It lets you treat HTTP as FTP. Just as secure as FTP too. But again, it’s a pain to set up.

So what happens when two simple guys want to share a movie they’re working on? They drive over with an external hard drive and share the data. Because that’s the fastest, safest, best way to do it.

We’re missing something here, aren’t we?

I got to thinking about this when MegaUpload, a filesharing site (mentioned in the comic) was shut down on the 19th for violating copyright. See, some people were uploading material they didn’t have the copyright for to MegaUpload. Why? Because anyone could sign up and upload anything. Of course.

https://twitter.com/EricMann/status/160110405090414592

I meant MEGAUPLOAD in that tweet, but Eric’s reply got me thinking more.

How much illegal material goes through the US postal service? I mean, let’s say I download illegal software, put it on a USB drive, and mail it across state lines to my friends in Texas. How many laws did I break? A lot! The US Postal Service sends a lot of really weird mail but they do have rules. The trick is getting caught. They don’t check DVDs, books, or USB drives because there’s no need to.

Going back to MegaUpload, they were shut down because someone used them to transport illegal items. If we apply that mentality to physical mail, then we’re talking about shutting down the entire postal service because Bobby Dumbass mailed his brother a video of himself jerking off. Oh yes, that’s illegal.

This isn’t unnecessary hyperbole.

The reason MegaUpload is so popular is that it made it fairly easy for the laymen of the world to upload large files. The problem with it is that it’s filled with distractionary popups and the like. I’m using ‘is’ since I think it’ll be back. Still, MegaUpload filled a niche that is desperately needed. How do the tech-newbies upload large files? I’m capable of making and seeding a Torrent, but those aren’t easy and rely on other people seeding to speed it up, plus a level of tech-savvy from the receivingt end where someone knows how to use a torrent file and pull the data back down.

On the other hand, when I download something from Apple, say a 300meg update for my iPhone, I’m downloading … a 300meg update. Apple has a gazillion severs in the US. Why not use Torrent technology to let me pull down the file in chunks, instead of in order? Is this because of how Torrents work, or are they just scared because of what happened to other Torrent sites?

Torrents (bittorrents) are amazingly impressive to me. In regular file downloads, you pull a file down ‘in order’, essentially, like a printer. One line at a time is sent, downloaded, rendered and output. Torrents spin that around, and work by downloading small bits of files from many different web sources at the same time. It’s like watching the movie Memento. The story is told out of order, but in the end it makes sense. That means if I’m downloading one bit from Joe in Arizona and another from Dan in Nebraska, I still get the same file, and I get it faster because if I lose connection to Dan, my Torrent app finds Barbara in Iowa who’s also seeding the file and I keep downloading.

Today, if I lose connection in an FTP download, I have to start over. A torrent I can stop and start all I want. I know, that sounds totally awesome, right? So why aren’t we using it more?

I don’t know. I think because it’s seen as ‘dangerous’ by the copyright moguls. It makes it too hard to track infringement, and makes everyone culpable. Which it really doesn’t. I mean, I guess they’re just afraid and don’t understand that this power is already there, and that it’s always been there. These are the same people who wanted the VCR to die an ugly death because it would ‘hurt sales.’ Protip: It didn’t. Neither will this.

So let’s push our tech companies to come up with a better way to share large files, a way the non-tech people can use. Make it easy to set up on your computer, make it easy to understand, like email and the basics of the web. Make it fast to upload, faster to download, and easy to link to. Make it easy to keep private if we want, or public if we don’t. Make it simple to report copy infringement too, and use it as a legal way to send large files, like movies, so the Hollywood people can give us a viable, workable, alternative to theft.

We have the tools, let’s do it!

20 January, 2012
SOPA Blackout
I’m lazy and I don’t want to write a plugin, so I asked on Twitter if someone had one to black out a site for SOPA on the 18th of January. If you don’t get why this is a thing, please read WordPress.org’s post on SOPA. A lot of sites are going black from 8am to 8pm. I am, and I to didn’t want to use a plugin.

My solution for this involves two files and is all thanks to Pete!

@Ipstenu add a .maintenance file

— Pete Mall (@petemall) January 12, 2012

To do this is really simple. Go in and make a file called .maintenance in the top level of your WP install. For most people, it’s the same folder as your .htaccess and wp-config.php files.

Now edit that file and put in the following content:
```
<?php
 
// Let's make sure you're not an admin/logged in!
 
function is_user_logged_in() {
    $loggedin = false;
    foreach ( (array) $_COOKIE as $cookie => $value ) {
        if ( stristr($cookie, 'wordpress_logged_in_') )
            $loggedin = true;
    }
    return $loggedin;
}
 
if ( ! stristr($_SERVER['REQUEST_URI'], '/wp-admin') &amp;&amp; ! stristr($_SERVER['REQUEST_URI'], '/wp-login.php') &amp;&amp; ! is_user_logged_in() )
 
// If it's after 8:00:00 on the 18th, we're going to show the blackout page
 
if ( time() >= mktime(8,0,0,1,18,2012) ) {
	// When we hit 8pm (20), we're back.
	$upgrading = mktime(20,0,0,1,18,2012);
}
?>
```
What does this do? It’s pretty simple. First it checks to see if you’re logged in and, if so, lets you get where you need to go. If you’re not logged in, though, it checks the date and if it’s after 8am on the 18th, you get a maintenance page. After 8pm on the 18th, it swings back. (All this code, except for the date stuff which I wrote, is from Matt (Sivel):
WordPress Maintenance Mode Without a Plugin and WordPress Maintenance Mode Without a Plugin Part 3/ ) Pretty cool right? And the 8am to 8pm is based on your server’s time, so it’s all local. It’s also pretty easy to see how you change that for your own time. I would say pick your busiest time to go black.

But if you want it to look pretty, you need to do a little extra. (Code from WordPress Maintenance Mode Without a Plugin Part 2 and text from Blaccupy) Make a file called maintenance.php and put it in your wp-content folder. Here’s an example:
```
<?php
/* Tell search engines that the site is temporarily unavilable */
$protocol = $_SERVER&#91;"SERVER_PROTOCOL"&#93;;
if ( 'HTTP/1.1' != $protocol &amp;&amp; 'HTTP/1.0' != $protocol ) $protocol = 'HTTP/1.0';
header( "$protocol 503 Service Unavailable", true, 503 );
header( 'Content-Type: text/html; charset=utf-8' );
?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
        <title>BLACKED OUT</title>
        <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
        <style type="text/css">
        body {
                background: black;
                text-align:center;
                color: #eee;
                font-family: Helvetica;
                font-size: 2.2em;
                }
        </style>
</head>
<body>

<div style="width: 960px; margin: 0 auto;">
<h2>This website is..</h2>

<h1>BLACKED OUT!</h1>

<p>In protest of pending US legislation, which threatens the freedoms of websites like this one and the freedoms of the people who use them, this website is offline on January 18th, 2012 from 8am to 8pm EST.</p>

<p>Please <a href="http://americancensorship.org/">help protect our free speech</a> against the corporate and political interests which seek to take them away!</p>

<p>(And don't worry, we'll be back in business tomorrow!)</p>
</div>

<?php
die();
?>
```
Which means your site will look like this on January 18th. You’ll notice I made some tweaks on mine. This is a default feature of WordPress, by the way. You can design your own maintenance mode page just with this one file, so y’know, party time.

Now there’s only one catch. If you update WP via the automatic updater between now and then, you lose the .maintenance file. I don’t have a fix for that, but if you do, please comment!

And yes, my sites are going dark on the 18th.

ETA: If you have a Multisite and only want SOME sites dark, use Customize the Suspended blog page from WordPress Must-Use Tutorials. Suspend the sites and boom goes the dynamite.

ETA 2: If you’re using MediaWiki (like I am on another site) I came up with this idea to go dark for SOPA. Its just a normal extension that, between those hours, redirects to the same page I use for WordPress. You could have it point to any page, of course.
```
<?php

if ( !defined( 'MEDIAWIKI' ) ) die();

if ( time() >= mktime(8,0,0,1,18,2012)  &amp;&amp; time() <= mktime(20,0,0,1,18,2012) ) {
     
        include('/location-of/wp-content/maintenance.php');
    exit();
}
?>
```
That code, sans the Mediawiki line, will also work as an extension for ZenPhoto, so pass it on.
12 January, 2012
Yourls
For a long time I’ve wanted short URLs for one of my sites. Finally I figured out a short URL, picked up the domain, and said “It would be great if I could redirect posts with this! But how?”

As it turned out, I was making a mental mountain out of a miniature molehill. I do that sometimes, get all caught up in a non-meaningful detail. This was easy, it wasn’t super complicated, and it was fast. On the scale of things where WordPress is the easiest (1) and MediaWiki is the hardest (8), this landed next to Zenphoto (4) and was about the same (3 or 4, depending on your skills). It requires more RTFM than WordPress, and I had to do some things manually.

Setting Up Your Domain

First buy the domain. This part is obvious, I hope. Since I’m on cPanel, I added my new domain as an addon domain to the master. This let me have the short domain (do4.us let’s say) hosted off the main domain.com site, without making a separate account. If I’d wanted to map a domain, I would have parked instead of addon-ing.

To add an addon domain in cPanel:
1. Enter the domain for the new addon domain into the New Domain Name field.
2. Enter the main FTP username for the addon domain in the Subdomain/Ftp Username field. You can use the one you use for the mani account if you want.
3. In the Document Root field, enter the directory that will contain the addon domain’s files.
4. Enter the password for the addon domain into the Password field.
  - Make sure you use a secure password.
  - You can have cPanel generate a secure pasword for you using the Generate Password feature.
5. Confirm the password in the Password (Again) field.
6. Click Add Domain
7. To add files to the addon domain’s home directory, click the File Manager link, or use FTP/SSH like normal people.
Once I did that, and DNS propagated, I was ready to go.

Installing the App

I decided to use Yourls for this, since my friends use it, and I know (in that internet way) the guys behind it. Hi, Ozh.

That said, their install doc was screwed up. For 1.5, it says to edit a file that apparently isn’t included in the build. That’s okay, since I just used SVN anyway. The directions are very much geeky. This is not a simple WordPress install.

What I did was first make a database domain_yourls and added my DB user account to it (I never use my domain FTP account). Then I ran an SVN checkout from googlecode to grab the files into the root of my add-on domain: svn checkout http://yourls.googlecode.com/svn/trunk/ .

After that, it’s the manual editing of the config file (the sample of which is not included in the 1.5 zip) and then I went to myurls.com/admin/ to finish setup. I had to grab the .htaccess file sample, since mine didn’t copy down (my own fault there).

Configuring the App

Install the YOURLS: WordPress to Twitter plugin. Even if you don’t plan on using the auto-tweet function, this is the easiest way to get your URLs made. The “hard part” here is setting up a Twitter ‘app’ for the first time. If you’ve done it before, it’s not terribly hard, but with all new things, it’s scary. Ozh’s directions are painless, thankfully, and then … you’re done. And you have your own Short URLS!

What’s Missing?

Two things, and neither are YOURLS fault!

1) Twitter doesn’t know that three different URLs (domain.com/postname, domain.com/?p=2 and do4.us/2 for example) are all the same URL. That means if you use those Twitter Rewteet buttons on posts, it doesn’t show up the same way, and the ‘count’ is off.

2) There isn’t an easy way to tell Jetpack to use my short URLs instead of my site’s full one. Edited to add: By this I mean only in the ShareDaddy links. Like the ‘tweet/email/facebook’ ones. Actual shortlinks work perfectly.

I suppose a third is ‘Damn it, Twitter, stop shortening a short URL!’ but that’s a different rant.

Should you do this?

I think so, but then again, I’m weird.

Read Also…

Otto – Using YOURLS with WordPress

Rev. Voodoo – How I Set up Vudu.me URL Shortener With Yourls
9 January, 2012
Said It Once Before But It Bears Repeating
A lot of the time, we complain “Don’t people look in the forums before they ask a question?” Sometimes we kvetch that these people are ignorant or lazy, and many times they are. But while a lot of questions are repeated, it’s really not as cut and dried as it may seem.

We’ve all had conversations where it devolves into “Hey, can you get me that thing?” Usually this involves a hand gesture or two. I’m sure everyone’s been in the kitchen with family and pointed right at a cutting board and asked “Pass me that … that thing.” It’s not that you’re stupid, or ignorant, or lazy, it’s just that right now you forgot the word “cutting board” and as embarrassing as that is in the moment, we all accept that this happens to everyone.

What does this have to do with questions? It’s really a language thing, on many levels. If you ask six different people “What do you call those boxes on the admin dashboard of my CMS?” you’re going to get six different answers. (WordPress had this not too long ago, and it varies from ‘meta boxes’ to ‘widgets’ and everywhere in between.) Certainly we can attribute this to ‘different brains, different thought patterns.’ But also, if you’ve ever tried to learn a new language, you remember the brute memorization of words than you had to combine with actually using the words, otherwise you forgot them. It’s like that algebra you did in school. If you’re not using it, it’ll fall right out of your head. Unless it’s the lyrics to that song you hated.

Now that we all accept that we all forget, what’s the deal with not being able to find what we need? It comes back to naming. I often complain that looking for an image on Google would be easier if I could draw it. I’m a pretty visual person, and I like to see what it is that’s wrong. I ask people “Can you put up a screenshot of the error?” or What page are you on?” You get a lot of weird error reports in my life, like “When I upload a file I get an error.”

The problem is not that people don’t know how to explain what’s wrong. The problem is they don’t know the words to use.

Okay, maybe it’s a hair splitting, but when you say “I want my code to do THIS and instead it does THAT.” you will often see yourself using very non-technical terms. First and foremost, that’s okay. In fact, I encourage people to use the terms they’re familiar with, that will make it easier to get help. But you need to know what you’re asking for, and that’s a problem.

For example. You’re brand new to WordPress and you want to know how to upload an image. So you google “Upload image WordPress” and thankfully the very first hit is what you want. However, the more ‘specialized’ a question gets, the harder it is for the uninitiated to ask it. “I want to change those menu things on the side on my webpage” you think. Not a weird or uncommon request. Except ‘menu’ is the wrong word. You’re really asking “How do I edit my sidebar?” and that’s fairly easy.

You have to know what you’re asking for in order to get the right help, and you can’t know what it is until you ask someone who knows. And worse, you can’t know who to ask until you’re familiar with a product and it’s terminology.(Unless you know someone who speaks hand-gesture.) Basically when you’re learning a new program, you’re learning a new language. Worse, you’re learning a whole new culture. It’s like being back in college, where everything is hugely different from High School.

That’s why I try very hard not to get frustrated when I see the same question a million times. It’s rarely worded the exact same way. However, when I see people ask “How do I add images to WordPress?” I wonder if they’ve heard of searching.

The steps are easy:
1. Look it up on Google/Bing/whatever
2. Search the forums
3. Ask
When you hit step three, you have to ask it in the clearest language you can.

On my site, I have two ‘sections.’ There’s the main part where all my posts are, and there’s this list on the side that has calender, login links, and other stuff. Here’s what it looks like: .

Now you’ve asked a very clear question. Let’s compare it to the ones I saw recently:

My site has this stuff I don’t want. How do I remove it?

Which one would you answer?

It’s okay not to know what you’re asking about in detail. No one is born knowing, and you have to learn somehow. Accepting the fact that you’re new, or ignorant at something, is hard. We’re often told it’s not okay to not know things, that being ignorant is a sign of weakness. That’s just not true. We’re all ignorant and we’re all new about something. Everyone starts out ignorant. And we all start out not even knowing how to ask a question.(If you’ve ever been to a Passover dinner, the point of the Four Questions is to remind us that we all start out as the simple child who doesn’t know how to ask a question, and thus we tell a story every year to teach them, and ourselves.) The problem is that the answers you get depend entirely on how you ask the question! If you ask it wrong, you get the wrong answers, which frustrates everyone.

Should you search first and then ask? Of course. But you, as the helper, need to remember that the language barrier is going to cause a lot of the repetition. You’re going to get the same question, something basic and simple, asked a hundred times because people don’t know what they’re really asking. And yes, if there’s a good tutorial, toss them a link. But remember these people are new and scared and tossing them a link doesn’t help because they still may not speak the lingua fraca of the help docs!

Step back.

Remember what it was like to be new, and you’ll understand why the same questions are asked a hundred times over. Point them to the documentation. If the docs are lacking, fix that and make them better for the new guy. And, as hard as it is, especially right now in this holiday season, don’t get mad. Take a deep breath, watch Tron or play a round of World of Warcraft (or Mario Kart Wii) and remember that first time you did something, and how hard it was to learn all those terms and understand what they meant.

And you as the asker? You need to remember that sometimes, when the helpers ask you something that seems silly or weird, or overly simplistic, there’s a reason. We like to take apart a complicated question to its simplest iteration in order to understand what it is you want, and to be able to teach you “Okay, when you say ‘non blog index’ what you mean is a ‘static front page’ which is ….” We want you to learn our lingo so we know that we’re all speaking the same language. Otherwise we’re just doing a modern rendition of “Who’s On First.”
30 November, 2011
Community Driven Design

WordPress 3.3 is on the horizon, and already there’s a minor kerfluffle over the flyout menus. Regardless of if you agree with the change or not (I do, Otto does not, for example), it brings to mind the reality that every time there’s a new change to the Admin UI, someone demands to know ‘Who’ requested the change. One time, the answer was ‘Matt.’

While WP is open source, and that means it’s community driven, that’s only to a degree. Remember, at the end of the day the folks with commit access are the ones who decide what they want to support and have in their app. Theirs. WordPress isn’t a Democracy, it’s at best a parlimented monarchy, but really more of a benevolent dictatorship. This is neither good nor bad, when you put it in perspective, and I’m afraid that with products, especially free and/or open-source products, we as a user base consistently lack that perspective.

The company I work for recently switched to Office 2007. Yes, I want you all to take a moment to reflect on the fact that we didn’t move to Office 2007 until it was 2010 (and didn’t finish until summer 2011), it’s important. The reason we didn’t switch sooner wasn’t for anything technical. In fact, we really wanted to switch so we could upgrade SharePoint and have functional integration. No, there were no app conflicts or weird database issues preventing the upgrade. It ran on our operating systems without issues. But why didn’t we upgrade? Because some of the people in “very important positions” had trouble with it, and we were concerned that the UI change, which was rather dramatic, would overwhelm our help desk.

To put this in perspective even more, there are about 20k employees at my company (give or take, I’m not counting consultants here, or non-computer-using people). Of those, about an eighth are what I’d call techies. That is, maybe 2500 of us are really nerdy people who use foam swords or even know who Stallman is. Another 2500 of us are technically inclined, and capable of trouble shooting the basics. Another 2500 are smart enough to know how to explain their problem to the techs. That means over half the company are ‘real users,’ you know, the ones we make fun of for deleting DLLs that are taking up space, or who reboot their monitor. Every time we make a change to software used across the entire company, we have to put that 50% clear in our minds. How will this affect them? What training to we need to provide? We’ve pretty much accepted that no change will be universally accepted, and at a certain point we have to agree that this is ‘good enough’ for people, and deal with the fall out.

Coming back to Open Source, when a project like WordPress or Drupal makes a major change someone’s going to hate it. This is just the way of the world, and even if you love the change, you need to work to make sure your replies to these people aren’t ‘haters gonna hate!’ or ‘you suck!’ Neither of these are productive. Part of the problem here is that people get passionate and sulky, like a nine year old who viscerally dislikes something, but lacks the language to fully explain it. This is not to say people are incapable of explaining themselves, but that part of their problem is the ephemeral ‘feeling.’ The other major part of the problem is that no two people hold a hammer the exact same way. And of course that people who are complaining at the ‘beta’ stage of the product are in too late.

Understanding how these designs get made goes a long way into making people accept changes they don’t agree with. It doesn’t make them like the changes, but understanding how and why they happened can get you to the ‘agree to disagree’ point. John O’Nolan (who currently is living on the road by choice) wrote an amazingly informative post about how he got involved in WordPress UI back in the 3.0 days. He lays out how you can get involved more, if you’re inclined. There’s a great Make WordPress UI P2 blog, and of course WordPress Development blog that you can follow along to see what’s going on and there’s always looking at the tickets in Trac flagged for Needs User Experience/UI Feedback, but I’ve found the first way you should get involved is to start using WordPress trunk: the live latest and greatest, but not ready for prime time players, version.

That seems like a departure from theme, but it’s not. We all start out as basic WordPress users. We use the product, we know how to add/edit/remove posts, we move on to using plugins, and eventually we hit a wall. Either we start to adapt and become power users, who understand how to tweak things in wp-config.php, play with SSH/FTP, and make a quick child theme, or we resign ourselves to using WordPress as it is presented. Neither use-case is better or worse than the other. If you’re a ‘hard core’ WordPress user, though, you will find yourself wishing for small fixes, and you’ll make a plugin for yourself. Then you share it, and then you start to suggest things in the forums, or report bugs in trac. Now we’re cooking with fire, and it’s not long before you start tossing out code or css ideas for trac.

The point of this is that if you start ‘testing’ the new versions of WordPress at the beta or release candidate iteration, you are too late in the game to make a UI comment. The Beta and RC releases aren’t for making drastic changes, but for making the changes that are in there work correctly. Like how the ‘close’ button on the admin bar pointed isn’t working on IE 7 or 8. That’s a bug. But not liking the admin sidebar menu flyout and disagreeing with it entirely isn’t a bug. Did you know the head of the UI team didn’t like the Admin Bar back when it came about?

You don’t have to like everything about a product to use it, and sometimes changes mean you need to rethink how you use it. Also, WordPress has a policy similar to Apple and Amazon: Release, then iterate. That’s why in the last three releases of WordPress, we’ve had one major change and two noticeable tweaks to the whole admin UI. The 3.0 release was a huge overhaul, and in both 3.1 and 3.2 (and now 3.3) we’ve had significant variations on a theme. They feel big, but compare it to the 2.9 to 3.0 jump and it’s really pretty small.

If you want to guide WordPress’s UI, get in on it earlier than beta. If you want to iron out bugs, join at Beta, but take the time to learn the difference between ‘I don’t like…’ and ‘this is broken….’ If you want to get new features early, join at RC. If you want to wait till we’re ready to go, wait for the final release. If you just use WordPress and trust that most everything will work, use the final releases. If you’re annoyed that little bugs get missed, use RC. If you know you’re using a fringe case, or setup that uses normal WordPress but on an obscure server or configuration, RC or Beta is where we need you. Remember, not everything can be tested, but you can help test more. However. If WordPress is your life, if you live and die by WordPress and support people who use it or need to be testing it in your corporate environment, then you need to step up and start using SVN. Make a second install and set up a job to update every few hours, pay attention to release dates, and don’t treat this like ‘traditional’ software and wait for a release to be notified as to what’s going on.

But that is another post all together.

Perhaps the best thing about a cooperative design, like in an open source app, is that if you don’t like the changes, most of the time you can find someone else who doesn’t, and who wrote a plugin/extension to change it. When you compare that to, say, Microsoft Word, and remember that you, as a user, have very little say in things unless you luck into their market studies or beta tests, and even then, the locked down systems don’t always permit changes, well, you’ve actually got a lot of freedom. And if you’re not a techie, well, make friends with one or hire one. I hear a lot of them like beer.

26 October, 2011
Request: Multiple Domains, One IP SSL Certificates

This is actually a request. The server that runs Ipstenu.org hosts three other domains. I set up my self signed certificate just fine for *.ipstenu.org, but I want to add on the other domains. For some reason I seem to be failing.

I somehow managed to get it half-baked. If you go to https://otherdomain.com it kicks you to https://ipstenu.org/wp-signup.php?new=otherdomain.com which isn’t what I want at all.

I’m using WHM on CentOS 5.6 and I’m a total newbie when it comes to all this! Links to tutorials with pretty pictures, advice, or directions are all welcome!

18 October, 2011

Tag: website

Large Files Don’t Move Well

SOPA Blackout

Yourls

Said It Once Before But It Bears Repeating

Community Driven Design

Request: Multiple Domains, One IP SSL Certificates