Yeah; the way WordPress handles archives automatically for us makes it a bit strange to figure out at first. Once you get it, it makes perfect sense though.
Any suggestions on how to better label the fields that would have made it easier to understand?
Can’t speak for the others; if scalability into the billions of posts is really your concern: at volume, the platform matters significantly less than the operators and system administrators keeping up with the growth. Most of your static content will be served directly from the cache, and there’s not much you can do about database writes; they have to happen anyways.
If what you’re looking for is for someone to tell you that bbPress will out-perform some other platform is some specific way, I think you’re on your own. What I can tell you is that bbPress very much is in active development, and is optimized to use all of WordPress’s cacheing API’s, with constant efforts specifically going into further optimization in future versions.
Do not modify the core files that are included with bbPress.
Easiest way is to use the shortcode, and use CSS to hide the bits you don’t want.
If this isn’t satisfactory, you’ll need to make custom template parts to override the output.
You figuring it out doesn’t usually involve others handing you an answer. 
I think you might be over-thinking things. Rather than trying to overload the WordPress template loader with a new archive-forum.php and trying to run something through a shortcode, why not just use a WordPress page, set the slug to /forums, and put the shortcodes and div’s in there instead?
Topic views are specific ways to group topics together based on any criteria. bbPress comes with 1 view: Topics with no replies. Developers are free to extend the views in bbPress, much like we have here at bbPress.org with the support plugin.
Looks like she doesn’t have the proper capabilities.
* Is she marked as a spammer?
* Is this a multisite installation of WordPress?
* If so, is she a user of that site, or do you have those forums set to be global?
When you start storing that much data, it becomes less about volume and more about server setup and performance. MySQL databases can hold billions or records efficiently, WordPress can read and write to that database easily, too. What will matter is how you spread the pain of your traffic and volume around.
Don’t sob quietly if something is broken! If you find a bug, proclaim from the hilltops so it gets fixed!
I need more specific information to be helpful. Also, the visual editor isn’t built into the template files, so they should not directly be the cause.
I run bbPress 2.1 at testbp.org with the visual editor on; so something else must be up.
Sounds like you’re only overwriting files, and not deleting the directory. Delete the entire /bbpress folder and replace it with the one from Beta 1. Should be good to go from there.
The .pot file needs to be updated. I’ll make sure it’s done in 2.1 by the time it’s released.
Don’t delete anything from the bbPress plugin folder.
Chances are you have a /css/bbpress.css file in your theme. It will now act as the full bbPress theme stylesheet, rather than pulling in two separate files.
endearndrew – can you drop a note in the 2.1 topic that this is resolved, and anywhere else you brought it up? Thanks.
Search for bbp_show_lead_topic. This has been answered here several times before.
Marco – thanks for the feedback. No reason to double post this. Trac is plenty fine.
Not the same issue at all. Also looks like you fixed it.
Not the same issue at all. Also looks like you fixed it.
It’s a bug. Will look into it.
Look harder. Plenty of examples in the forums here and the codex.
What your site looks like is not the intention. Your theme is not compatible with bbPress, since it’s doing something o override the WordPress template loader.
Way is suggested above deletes all revisions, even for your blog posts. Easier to modify the theme to not include them.
I see no pagination on your links above.
Not experiencing any of these issues on several installations. Can you please try your updates again? If you have anymore feedback other than ‘it broke’ would also be great.
Update to bbPress 2.0.3; should work just fine.
