Recent content by ooo

wp have all versions like 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, etc (and 1.2.x minor updates) I think it is good idea to use similar versioning. If next release after 1.1 is big update, it is not necesarry to bump version to 1.5... If next release after 1.8 is big...

does xenforo support permission to allow guests to post messages without registration?

I don't know about other forum systems, but in vbulletin each skin/style and language combination requires separate record in postparsed table, this tables are big, and to work fast this tables must be cached... that means with more skins it will eat more ram or your forum will work slower

  What you mean by 'best'? Is it only way, or you know alternatives? Because this is not what I need.

where to put my email address to get notification about final release?

may be it make direct urls (without rewrite) nicer if main files will be short /u.php?id=522 instead of /user.php?id=522 /u.php?522 instead of /user.php?522 /t.php?t=463 instead of /thread.php?t=463 /t.php?463 instead of /thread.php?463 etc.

Mark Sullivan developer from Vanilla Forums is he relative to Mike Sullivan from XenForo?

is there any plans to start selling product during pre-final RC (or Beta) release? or first available version will be 1.0, with following 1.1 which covers found bugs?

fact that you didn't notice means it is NOT good

google wave was exactly facebook replacement, i.e. email with more interaction, which covers most of facebook functions btw, google just open sourced standalone version of google wave http://googlewavedev.blogspot.com/2010/09/wave-open-source-next-steps-wave-in-box.html

this is very like google wave why they just didn't fork google wave?

will we have any hints or official rc version before final release? or we will not know rough release date before it happens?