Sometimes I check the logs and notice HAL, Jarvis and other bots disconnecting then when they return, they do not get opped automatically. Other times I notice Eeems for example trying to !op, to no avail. I think there should definitively be a few extra ops for such stuff, in case the channel became op-less, so you guys don't have to call an Efnet oper everytime, while still being careful before opping someone to make sure it's not an imposter

Yeah I've not been able to get ops back in #omnimaga-de even though I'm pretty sure I was one of the first there to open it up, netham just never set me as an op. I've also had to op HAL/Netbot45 a few times in -ops

Also OmnomIRC definitively needs banning, because when you ban a forum member he still can post in Omnom if he kept an old tab open, until his session times out. In that case you are forced to ban everyone from using OmnomIRC, so no text sends to #omnimaga, but it will still show up on the site side.

OmnomIRC banning existed in OmnomIRC v1, but for some reasons it was never re-implemented in OmnomIRC v2.

Yeah that would be really helpful. I wonder how hard it would be for netham to also implement an admin panel for Omnom so it's easier for us to manage it without having to remember all the commands or something.

I think Ephan/Jim could definitively be good choices as european channel ops. Maybe Lionel too, but he is not active enough I think.

I think they are good choices too.

EDIT: Erm I just realized that was quite a necropost

Lol, meh it's still relevant

I wonder if there is enough space left for Axe to add some sort of signing process that can be enabled ( disabled by default ).

[sarcasm]
Rule #1: Never update the first post!
People LOOVE to dig through your thread in order to find the latest update. When I find myself looking at the first post in a project topic, I always enjoy seeing no progress updates, the oldest screenshots, and thinking it has gotten nowhere. The first post is for just announcing the project, and it is the end user's responsibility to dig through page after page of posts to find news.

Rule #2: Put the most important things last!!
Everybody loves to read your rants, old screenshots, musings, and plans for future features before seeing the overview of the info and the download link.

Rule #3: Make the first post really long!!!
Never put change logs in spoilers! Everybody LOOVES to read about every single change you made in the program before seeing the most recent updates. Always put screenshots line by line and outside of spoilers, and the most important screens (i.e.) animated ones at the bottom. I always love to see all of the old screenshots of crappy beta versions before I see a nice animated current screenshots. In fact, NEVER put new screenshots in the first post! Note: lots of unnecessary info and rants make for good first post fluff.

[/sarcasm]

Who am I kidding? Those are the things NOBODY should do!!! First posts are for updating info and having a quick overview of the topic, the rest is for discussion, people.
Feel free to add more anti-rules.

Umm....Actually some people don't mind that stuff. It's a matter of personal preference. I myself seldom update my first post because I'd rather spend my time working on my project instead of going back to the first page and adding a little more information to a different post as well as posting a new one. I'd rather just put it in the first post. If people really want to know more about the project they can read back a little.

I think I'm in love with this game

You could have the script dynamically parse what $max should be, and you could create a form for yourself to upload the file as well as update the title/text ( just make sure to make it secure ).
There should be, at the least, you could just do a substr() but I'm pretty sure there are more advanced methods.
I'd say stick with the dynamic design and just try to make it more streamlined.

Merged.
Sorry if that makes people double posters

Why not using MySQL?

Lets start him off slow ok Adding MySQL to the mix when he barely knows PHP isn't a good idea yet.

You could use xml, I'm just not sure if you can access it that way, feel free to try it out though. You could also use flat text files if you did some nice formatting, like grabbing the title from the first line, the alt text from the second line and the rest of the content from whatever is leftover.