Thought about going to a php platform instead of a cgi flat file?
Just glancing over the code I see some hard links, you should soften those up a bit, ...
You may be seeing hard links in the code but thats how they are built. There are very few pages on this site that aren't built on the fly from php or cgi scripts.. most of the links come from variables therefore they look "hardcoded" when you just view the source. The flat files you see are not flat at all.. almost all scripting is server side to keep the load time down. We know what our servers can handle.. let us do the work for you puter .
I only looked at the first few lines of the code, and I found the CSS and Body BG tags both hard coded instead of soft.
LINK REL=stylesheet HREF=' TYPE='text/css'
body bgcolor='#5D5C61' background='
This is as far as I went and what I was referring to. What happens when you use hard links like that is the GET request has to be sent again and again, slowing the parse engine down. Obviously all the session variables, etc are dynamic... but those dont actually pull information in. They are whats called a post parse link, so they require user input to process. The CSS Link and Your Body tags are PRE parse tags and require processing prior to viewing and hence why they shoudnt be used. You should use hard links on POST parse links for Search Engine purposes though. I just got a report from Yahoo about a client's site today, and they wanted hard coded post parse links *shake head*.
ImageMagick: Why would you want to create an entirely new application for something so simple? That just seems like alot of work. Gallery already calls Imagemagick on command, has secure uploading, has storage, has unique naming, and most importantly has an album view with admin functions. It already has everything you need. I would just create a new album, then If size is a concern I would just adjust the 'resize' option in Gallery admin, setting it for a maximum of say 800x600. Then when users upload into the album.. the photos are resized and automatically displayed at the best resolution possible. Solving all the size problems. If you create an entirely new application you would have so many variables to contend with: sizing, uploading, storing, naming, viewing, etc.
Flat File: Do you know what I mean when I say that? What I am asking is... is this bulletin board storing the messages in a file on the server, or is it pulling from a database? You said "not flat at all" does that mean you are using a database? I perused the Ikonboard requirements and it hinted at MySql support for heavy end users. Noticeably here,
If you are running a flat file system, I would suggest getting it over to MySql. That would be a very noticeable difference. If it is on a flat file... you might want to bounce around the idea of going to phpbb or something... go totally into php and MySql,
OH, and as for the purpose of the thread.... a Babe Board.. so people can post pics of babes on bikes,