You're replying to a comment by Kent Fredric.

December 10, 2009, 14:39

1. 301 Redirect:
Just don't do this in text. Its very pesky. Having seen text files with a thousand hand-coded apache rewrite rules for redirects, this is a bad idea. Use a database or something if you must. You're probably better off discerning the intent of what the user was linking to heuristically as a fallback mechanism, and then sending them there. You have 3 options what you can do here, 410 Gone, 300 Multiple Choices ( With a list of alternative places to go ) , or if your heuristic is good enough to *know* where they want to go, send a 301 / 302. Its a hard call, because you want to stop people accessing the old urls, but you really don't want the headache of a legacy-url and a new url having to share the same addressing space and having to maintain a secondary set of legacy data ( which will only get worse over time ), and you can't even guarantee every past URL has a fixed guaranteed location in the new URL system.

2. 404: You can do one better, log 404's and tokenise the url as to what they are looking for, use path tracking to see where they went ( and try to gauge where they were trying to go ) and tweak the heuristics/data to make them automatically get sent to the right place.

3. A great 404 page would do, as above, and try to use heuristics to work out where they are trying to go as best as possible, I think a good thing to do with 404 is treat them like search queries. ( It may also help to see url's as very highly specific search queries that only return one result most of the time ;) )

4. Yeah, pingback-- , so messy. You could at very least do something to trackbacks so they're folded and minimise screen utilisation.

      [  Comment  ] 
      [ __________]
Or even 
   [Comments   [ show trackbacks ] ] 

So anyone who wants to see them can make them turn up with a bit of JS.

6. Caveat, giving people points for activity can encourage spamming-style activity just to gain rep. Be careful. You may want to have a peer-reviewed good-comment-bad-comment rating system like reddit/stackoverflow to control how it applies. Comments that are replied to by other people might want to automatically gain a rep point. Not sure.

7. Even better, highlight their search terms on the page when they arrive =) [ If you're not already doing this ofc ]

8. Produce raw data feeds for all your statsy stuff, then people can graph it how they want and send it back to you. ( it will also make your stats graph code cleaner =) )

10. Images-- # sorry. too many images that are not relevant to context frankly just piss me off. they consume screen space, and I just have to scroll past them. DO NOT WANT. Screen space is expensive and frequently poorly utilised. If you're going to waste screen realestate, you might as well do something productive with it, ie: advertising. People zone out and ignore that stuff anyway.

14. Threaded comments are somewhat good, but there are dangers with them diverging too heavily. As well as tracking recent comments becomes much harder with threading. Its a tradeoff I havent found a real solution to yet asides letting people switch between the 2 modes of operation as they see fit.

16. Lightweight syntax for comments-- # everyone tries to use a shitty markdown crap, or some other pseudo-language, and all it ever does is cut the balls off the people who understand html, and produce a crappy inconsistent other-language which backs to html, but you have headaches trying to work out how the fuck you're going to do it. I have spent too many hours of my life trying to get Markdown to do what I want it do when I could have just done it with simple html. If you support this other language, make it optionable, because I for one *really* hate $otherlanguages.

18. There are privacy concerns arising from use of gravatar ( essentially, gravatar can track everything you do ). Look into Pavatar support.

22. Tiny URLS: you can implement this as the heuristics system above. If a short url is just a search token for some arbitrary content, then all you have to do is associate that token with the data. ie: I could take a stab at , and it would search for content with an associated short-tag of git, and possibly redirect me there, or find pages which have the term 'git' used frequently, and return a list of them for me to visit. If there's anything PHP have done right its this feature on their website;

24. Also maybe standalone Tar.gz's of the page.

30. Have Pages Open In A New Window By Default. ?!? Shit no. Way to annoy people.
If people want a new window, they'll do it. Thats what middle click is for. Extra annoying is people with crap like <a href="#" onlick=.... > rubbish which only calls , or some other javascripting thing, and that sort of stuff makes me want to hurt you. Middle click opens in a new empty page .... with nothing in it. Yuck.

34. You're better off having a link/menu that just redirects them to google translate, ie: not doing it via some api-proxy. That way they know they're relying on a translation service and it might be a bit nasty, instead of thinking you have crap language skills.

39. Just make sure you have either a) one rss for everything, or b)seperate rss feeds, but still a unified one for those that want it.

41. You could do it with a bit of javascript magic, and make <code class="latex"> get parsed by javascript, and replaced with an image =)
This is additionally beneficial becuse it keeps the source of the code available =)

42. <3 justify.

47. Egad, not *another* job board. Stop it people. There are too many to choose from, they all suck.

Reply To This Comment

(why do I need your e-mail?)

(Your twitter name, if you have one. (I'm @pkrumins, btw.))

Type the first letter of your name: (just to make sure you're a human)

Please preview the comment before submitting to make sure it's OK.