purge some more isRoom related stuff from the main query class

address self-updates to delete / remove modal dialogue vestiges

Updated to what's probably a reasonably stopping point. Will update description, etc after this.

I think these docs are great. :D

These first two basically prove this works if you have no rooms yet:

I think Diviner is meant for these scenarios. Basically because

I dunno, this was pretty exciting... :D

A few inline ideas that you are welcome to take or leave in my opinion.

Thanks for the demo. :D

I am demoing making an audit on the fly. Don't worry. :D

If you visit one of the commit pages, do you see the 'somebody accept a commit' message duplicated / other duplicated activity?

I think fixing this is basically removing the unique constraint on the "slugs" table in Phriction, and then using application logic to make sure that there can be only one active page with a given slug at any time.

I can't seem to reproduce this. See this test page here...

Hmmm, with the sum of UI changes lately, it feels like a lot of scrolling to get down to the code.

Hey @tiguchi - thanks for the report. I think it should be fixed if you update to HEAD. If things still don't work for you please let me know and I'll take another look. Thanks again for the report!

Is there any actual review happening in this workflow or is it just about getting the 100+ audits to an accepted state as quickly as possible?

How come the user shouldn't comment? What is the business value of letting someone read this information, but not interact with it further?

...we're really looking for as much information as you can possibly provide about what you're trying to do here. As a simply stated feature, the answer is "wontfix".

Please do re-open this if / when you have time to answer @epriestley's questions. Also, check out

Let us know if you weren't able to resolve this following @epriestley's instructions. Assuming things worked out for now... Thanks!

See T3105#31820 for the reasoning for the "wontfix" status, which remains true today.

Let us know if restarting didn't resolve this. Thanks!

Can you provide more examples of feed stories that you'd like to delete? Generally, I think the goal we want to solve is to make feed useful such that you don't feel the need to X out stories, so more context on what you want to remove is very helpful. In the example given, I would think we might want to aggregate those stories and just show a single one.

I think this problem is with Azure, your configuration with Azure, etc, since if it was a generic issue serving files we'd be hearing more about it.