It's the small things: If you've been bothered with #calls and #chatty seemingly starting up slowly in #phosh (while most other apps startup fast): I've posted MRs to fix this in chatty and calls (which then also prompted a small fix in phosh). Here's a quick demo of calls before and after the change:

@agx wow! How? Is it something with how Calls and Chatty are processing the long list of conversations or calls before they manage to show the list on screen?

@eliasr Both were running in the background already but the activation token to tell the compositor: hey, I'm here and should get focus (because phosh said so) was lost in the phosh -> spawns calls -> spawned calls instance notifies "calls daemon" that a window should be shown (and then quits) chain of events. By switching to DBus activation we remove the intermediate calls instance, the token gets passed and the compositor knows that calls is up (same for chatty).

@eliasr as chatty and calls run as daemon on session startup: so should it be slow for large call histories / room lists we can tweak that by preloading those. @devrtz already optimized that in calls a while back by only loading parts of the history. So basically startup was seemingly slow (although the app was already up) because calls/chatty didn't notify the rest of the system with a valid token