@sshannin is sending me screenshots where this is occurring in the durable column view with asynchronous updates via other users sending messages so I'll take a poke around today in case there's something one off in that code path.

Can you please re-open with reproduction instructions? Algorithmically speaking, this is impossible AFAIK because we now use the unique transaction ids to guarantee we only render each transaction once.

What are you finding confusing about Conpherence? (I saw your task about creating rooms - anything else?)

This is by design; we don't want new users creating new rooms as they test out the product, and instead think rooms should be created rarely and with some thought. Also, searching first seems like the right call.

I could see (maybe) adding custom fields support to events some day and otherwise sounds like T8032 is going to solve this for us for now. :D

If I read all this correctly, this was asking for the status of two existing bugs and reporting a third. I updated the task description to include links to the actual pertinent tasks here. Note I may have erroneously created the third task but I couldn't quite find it.

On the TODO user stuff, I had always assumed we'd do some sort of grey accounts. So something like a contact form could require users to log in, require them to enter an email address (grey account time), or be anonymous (no requestor object associated / created). I had figured a given Item would still have a Source associated with it ("the anonymous user complaint box") but not necessarily a requestor object.

I like shifted and I thought of "translocated" which is fancy for "moved" more or less.

Given all these constraints, I think while configuring a space it might be cleanest to have the user think about

How do you see the Security case playing out? My idea is that users don't put things in the space; the security guys do so the space is very private and not visible. I do like making people get a notification when they lose visibility, similarly to the task I can't find right now about getting a final notification when you are removed from subscribers

I think spaces being stronger than automatic capabilities is the right call from a product perspective. Mainly, I think losing access to a space should really make you lose access to everything in the space.

Hey SheerIce -

Oh i just re-read your description and it sounds buggy regardless of what you have the conpherence setting set to.

Since Conpherence can override per thread, this is broken out as its own setting:

The "start in Billing" workflow for me is

I think the usability issue here is that from the admin.phacility.com home page you have Instances, Billing, Documentation, Support.

Oh, okay, cool. Thanks!

UI seems a little strange for the "self actions" thing -- mailing list users can't take actions, right? -- but probably whatevs.

Thanks!

This won't update Herald rules or saved search queries, but they're presumably rare and infeasibly complex to migrate.

Sounds like a plan boss.

Yoinking this. If you've made any progress on this, feel free to post a diff, otherwise I'm on it.

Seems like the right first step to me and hopefully it holds up and the split into a Publisher class won't be necessary.

Cool. I don't think T8307 impacts too many people, and its nice to see a tracking task. :D

Copy changes, etc are coming; just taking off my queue.

while v2 is done, it kind of got busted up a bit and v3 is the new thing to watch still under active development. Check out the Conpherence workboard to follow along.

This has outlived its utility as a grouping task.