Wedge

Now I'm not tablet constrained, I'll explain a bit further.

1. You're pretty much the only person that's complained about it in the 10 months we've been using a sidebar on this site. It is somewhat rude to barge in and demand we change it just for you. If you were part of a majority that demanded it, we might reconsider, but I doubt it.

2. There is such a thing as optimum reading width - note that most books are of a fairly standard size, and even when they're not, the text is still set to roughly the same number of words per line and per page, just with bigger writing. I wonder why that is... could it be that they understand people best respond to a certain number of words on a page at a time? Having very wide screens is more tiring on the eyes and the brain than having shorter lines.

3. I respect that you have a list of requirements that you have to be seen to follow. Barging in here and expecting that we follow your to-do list is not going to happen.

More importantly though, there's actually very little fundamentally wrong with SMF - if it's working for you, stick with it, you don't have to upgrade past 2.0.x if you're happy with it. There are plenty of people still using SMF 1.1.x which debuted 7 years ago. (And what about all the people who still use Windows XP which debuted just over 11 years ago?) You don't have to have the latest and greatest, and it seems to me that you're looking to move on from SMF because you think you're missing out, rather than because it doesn't do the things you need.

Depends upon the width, I have 24" monitors and it gets ridiculous.

Hey, nice to see another programmer here!

Quote

I'd love for you to dish, but I guess you want to keep it close to the chest.

It's not my story to tell. But the public information is enough to figure out the general story even if not the specifics.

Quote

Hey, regarding the quoting, is there a way to get rid of nesting quotes?

Yes, the same as in SMF - in the admin panel there is an option to remove nested quotes. We have removed some SMF 'features', but not that.

The majority of the good ones get assimilated into the team, screwed over and leave. The slow release structure is related.

None whatsoever, except learning how to design mindfucked UI (Drupal)

Understanding the internals of PHP is no real benefit to writing stuff higher up, just as writing assembler probably won't help you write good stuff in higher level languages. I have a passing awareness of how the guts of the language work, but really, that's no substitute for decent programming style in general.

Caching, yes, pretty clued up on that.

Thing is, this is a FORK. It has a lot of SMF code still in it, a lot of SMF mentality and mindset and it's going to take a long time to phase that out, short of a complete rewrite.

Even much of the recent code still doesn't look particularly out of place from SMF, though we're finally moving stuff to using classes and exceptions, stuff that SMF never used because until recently it was supporting ridiculously old versions of PHP (SMF 2.0 will still largely work on PHP 4.1 and 4.2 and should be fully functional on 4.3+, even taking into account the magic loader that rewrites PHP 5.0 style classes with scoping to make them largely work with PHP 4.x)

There already is, written by the guy who used to write converters for SMF ;)

It's just been two guys (well, one guy the whole time, one guy sort of part time) the whole way through. But between the two of us we've worked on the biggest plugins for SMF; Nao did Aeva, I did SimpleDesk (that little helpdesk that even SMF themselves use)

Hard question to answer, since there's no security 'certification' per se for web design. What I can tell you is that in a couple of weeks I'm taking the Zend certification for PHP and in previous mock exams I've done, my security knowledge always came out as excellent. I try and design things for security first. For example the plugin system I've been doing is being engineered to allow people to upload plugins through a web interface but it jumps through a lot of hoops to avoid writing things as owned by the webserver, to prevent them being attacked on a shared server.

But the fact I've been known to report security issues to SMF (one of mine prompted SMF 2.0 RC5), I've also been known to review all the vulns I could find for SMF 2.0 and verify whether they are genuine or not. So, I guess you could say that there's a decent amount of security experience around here.

Nao was Aeva's developer/maintainer, I just came along and wrote a bunch of mods for SMF as well as being a reviewer on their Customiser team, writing their helpdesk and so on. In the scheme of things, Nao's the star here.

I would note that this isn't just a demo forum, it is the *primary* forum for the site, where we discuss features and so on. Sometimes we discuss them with an awful lot of passion, because we've put a lot of time into this and it frustrates us when that time doesn't work out so well.

That is pretty much where SMF is right now. I don't want to explain more, but they're not in a good place right now, and anyone watching their Github repo would probably understand where the problems are right now.