Half-Elf on Tech

Thoughts From a Professional Lesbian

Author: Ipstenu (Mika Epstein)

  • Pilot Fish Woes

    This is a true story. (more…)

  • Surfin’ Safari

    Safari 3 beta came out for Mac and Windows. Naturally I download Safari 3 for Mac last night and test it out, planning to pick it up on Windows when at work.

    On a Macintosh, things are like a pleasing mix of Firefox and Safari. There are a couple bugs I dislike (like Firefox’s ‘Allow Popups from…’), but I adore that it now alerts me ‘Dude! You’re closing multiple tabs!’ if I quit, and ‘Hey, you’re entering text in this window, you sure you want to close it?’ if I close this tab. So on that note, yay.

    On Windows it sucks balls. Oh, it’s fine on my XP home edition, but as soon as you add in Windows wackiness of Roaming Profiles, and proxies, and it dies.

    Mac makes two critical errors:

    1) Not letting you manually adjust proxies. Picking it up from IE seems sensible, but having used IE and multiple other browsers, I can tell you it’s a bad idea. IE settings work for IE. Firefox has to be different, slightly, and so does Safari. So instead, they should default to IE, but allow you edit access.

    2) Preferences don’t grok roaming profiles. There’s no way around how huge this is. If you want Safari to be used in corporate America, you must allow for roaming profiles. This means either you let relative pathing do it’s job, or you allow the users to manually set profile locations. The latter plan isn’t really going to work, since Mac lives by the ‘Do everything simply and have the user do nothing.’

    My solutions are simple sounding, and they won’t fix everything, but it’ll get them started.

    Hey, Mac, I used to build MSIs!

  • Why not homogenize?

    For another site I maintain, I use a total of six different coded products. Not one of the lot is actually integrated with the other, and no, I don’t use the same password between them. I’ve been having thoughts about merging the various tools into one vended support option, but as I look into the options, not one meets all the goals I have.

    Most of the time, when people look at a One Ring solution to keep all their products in line, they think of two aspects: usability and style.

    Usability means that, on the back end, you only have to learn one style of tools. We all know that no two product vendors produce the same style of code. Microsoft’s suite of word processing tools are, by far, the best out there, but Photoshop’s the place people go for photo editing. The interfaces between the two software tools is nothing alike. They’re so far un-alike it’s laughable. Hell, even Word on Windows is dissimilar to Word on a Mac.

    So for usability, people like things to look the same, or at least similar, so they don’t have to think hard when wanting to make a change. That makes sense.

    Style is more complicated. They want things to look the same. This makes more sense when you’re talking about a webpage, were you might have multiple background tools, but you want the whole site to look the same. This is called seemless integration. I call it style, since it’s a look and feel situation for the end use. Style points are useful. Style points keep people coming back to your site.

    In web software, which is as far as we’re going today, seamless integration is the thing. is content, a point most sites I’ve seen tend to miss. You have to have something worth reading, or people won’t read. Second? They have to enjoy the visit.

    A pox on all the sites with dark backgrounds and light fonts! That is not enjoyable! Most of us grow up with black text on white/light paper! We’re used to it, we like it, and our eyes have adjusted. Pander to us!

    There, was that too hard?

    Once you get a design, folding your multitude of tools into a seamless integrated design is fucking hell. Period. The majority of my sites are hand-coded, which means any integration was done manually. Over the years I got wise and used PHP includes, and then a PHP/SQL pastiche. But I attacked each part of the website problem as a separate entity.

    I needed polls, so I found good software. I needed an RSS feed, so I found one I liked. I needed a better gallery, so I picked on and so on and so forth. Doing things that way made extra work for me, this is true, but it also allowed me to tackle each new component as an individual. Would it have taken less time if I’d found an all in one solution? Yes, but it falls back on the problem that what I need doesn’t fall under usability and style.

    When I look for a new addition, I look for it as it’s own thing. A gallery needs to stand alone, without the rest of the site, and meet my organizational goals, my pretty URL goals, and my bandwidth goals. I’m confident enough in my l33t skilz to hack a system and make it look like how I want.

    So for me, a hacked up mishmosh system suite is what I need. Each tool is tailored specifically to my goals, and while it makes more work for me, the end user never has to deal with most of it.

    And if they’re happy, I’m happy.

  • Caveman Tech Support

    The tech support problem dates back to long before the industrial revolution, when primitive tribesmen beat out a rhythm on drums to communicate: (more…)

  • Stop repeating yourself!

    Almost a year ago, I blogged (and sent to a mailing list) a little ditty on how people know who you are on the net.

    One of the readers replied:

    : Admittedly, there a many legitimate reasons to have two IDs on one bulletin board.

    This might make an interesting follow-up article.

    Does it? Let’s find out!

    Some background information for the neophyte: Bulletin boards/forums have an ‘Admin’ who is the lord of all they survey. They run the code, generally the design, and have access to all things. Below the Admin are the Moderators, who have a varying degree of power. Some can only close nasty topics and some can do everything but blow the board’s code up. In other words, there are a lot of possibilities when we get into how much ‘power’ a moderator can have, so your millage will vary from board to board. Take this post with a grain of salt.

    Reason One: You’re The Admin

    In this instance, what you see logged on as the admin is not what you see as a user. For those of you at my office (and hi, I know you’ve found this page, I won’t tell anyone you read it from work, but I can see your IP address!), this is the same reason we have some people as admins and some as users. I’ll step it back.

    A user can log in, read posts, post a message, maybe send someone a private message. Just the simple stuff. That’s all they need to do, after all. Read and communicate. That’s all a user needs to do.

    An admin, however, can see the code, gets different error messages, and has control over not just the code, but the database with all the personal information.

    Now, as an admin, you also get a very different layout for the board, and when you’re designing things, it can be a problem. You know that what you see as an admin doesn’t match Joe User, so you make a second ID that’s just a user, and use that to test things from a user’s perspective.

    Reason Two: You’re The Admin

    No, I’m not repeating myself.

    If you’re the admin, sometimes you want to just be you. Having a second ID with which you can catfight with the best of them sometimes takes a load off people’s minds. It makes you normal and people have normal conversations.

    Reason Three: It’s a gaming board and you have multiple characters

    Some bulletin boards have roleplaying adventures and you can interact as different characters. Hence, different IDs.

    …

    Crap. I ran out of reasons.

    Okay, so there aren’t a whole lot, but there are some.

  • Why Wiki?

    I like the site I have for my RPG a lot, but it’s very big and often unwieldy.

    So I started to think about the ways I could simplify it, make it easier to use and easier to navigate. The first idea I had was a Wiki. I want to point out that when I started with a CMS (which I still love for what it is), I spent a lot of days going ‘Oh, my head! I’ll never get this.’ So I expected the same here.

    What ended up happening, over the course of a month, was the realization that while the CMS is a little pain in the ass to navigate, it works better for what it needs to be. Everyone who uses it has a blog, and I’ve put so much effort into customizing it that really, the only part that would be helpful is if the ‘encyclopedia’ for the site was a Wiki. At that point, however, it wouldn’t be ‘linked’ with the CMS I have so I’m fucked. Not in a bad way, just in the ‘this works, it works 90% of the way I want, and there’s no reason to screw with it.’ If Slayer ‘reboots’ and we start a new game, I may try something different. CMS was an experiment, and it was successful.

    But … I do have another site that might benefit from an encyclopedia. About 150 individual pages of information, contextual and informational. Okay that was a little redundant, I’ve had a long week. But still 150 pages. And maybe, just maybe, updating it all, by hand, alone, is a bad idea. After all, there’s stuff I’ve never finished because I don’t have gobs of free time. And as proved by the forums on that page, people want to talk and help. So how can I combine that with an ‘easy’ to use back end, and a not-terrifying to use front end?

    Wiki.

    Okay, so it’s got a crappy admin side and if you’re not a coder you’re going to cry setting up MediaWiki, which I did and I am one. And some users are skeptical about how to create pages and … it’s been 2.5 months and of my 32 users (yes! 32!) four people (besides me) have added information. Hell, having one person add information is helpful to me, so I call it a success.

    There are 1314 total pages in the database. This includes pages about the Wiki, minimal “stub” pages, redirects, and others that probably don’t qualify as content pages. Excluding those, there are 291 pages that are probably legitimate content pages. Of the 291 pages, 150 or so came over as a direct copy/paste import (and some clean up), and 140 or so were added special to the wiki because I had more ‘flexible’ room.

    That flexibility is what drove me to Wiki. You know, when you make a new website, it’s a pain in the ass to link everything up the way you want it, and you have to come up with some sort of structure that will make sense to everyone and you hope they can follow it?

    Wikis piss that out the window and laugh at your ancestors.

    That’s a joke, son.

    Wikis aren’t linear. Wikis are fluid and organic. They grow in the direction they grow because there is information to grow in that path. Not to say there’s isn’t a rhyme and reason to the site, but a Wiki accepts the fact that things criss-cross and double back and take weirdo curves and twists when you’re not looking. Of my 291 pages, only 61 don’t link back to something else, and even so, I’m taking the time to go through those pages and cross-reference. Yes! That pain in the ass, time consuming project of ‘Doesn’t X refer to something over on Z?’ A Wiki links all those up with a simple, easy code [[Page Name]]. Thats it.

    Okay, if you’re an HTML coder (guilty), your brain has a moment of pain looking at this. Another fsking pseudo code language to learn? First HTML, then BB code and now Wiki Code? 90% of the HTML I’d want to use work on a Wiki. The only ‘argh!’ moment I have is with headers, and even then it was easy to fall into that code mind-frame.

    So what did I learn?

    To run a Wiki you have to let go of control. And that’s really hard. If you have a ‘normal’, let’s say traditional, website, you have a small number of people who can update the site. You have a set design the site maintains. You have templates and standards and such. For a Wiki, you have to step back and say ‘This is the site, this is how it looks. Please add more information, but we’d like to keep the feel we have.’ Yeah, you can follow along behind people and clean up what they do (some people use wacky grammar, others use l33t speak), but essentially you’re giving room for their voice.

    You can’t take that away once given.

    Well, you can, but you’d be an asshole.

    Running the Wiki has made me a ‘kinder’ person, sort of. I’m more laid back with people who post in perplexing grammar on the forums. I’m not going to be a firm rule-mistress. Okay, maybe on the Wiki I’ll be a little more the enforcer, but there’s no reason not to give people chances.

    Of course, I still can’t figure out what the hell “I love to but deberia to allow him grissom sara to love it also” means!

    By the way, why did I choose MediaWiki, over something more use friendly like TikiWiki or something ‘prettier’ or something easier to hack? Well, I actually tried out a handful of Wiki’s before I settled on this one. I’d load them, make a couple pages, toggle around and see what I thought. The one I picked was the one that felt right to me. You might think differently.