April Town Hall 2026

I don’t even speak about collaboration and chat etc.
What I really don’t like is the fact, that importing an exported Space overwrites some date Properties!
That leads to the very real problem that filters in Views don’t work anymore – and there is absolutely no way to fix that!
The user can’t filter or sort his View for these dates anymore! NEVER again!
– These meta data are lost forever!

I’ve mentioned and explained it already multiple times, in different threads.
And I understand that one could have the point of view, that Properties like “Creation date” and “Added date” etc. better get the actual timestamp of the import.
– That’s may be a valid point of view in some cases. But this is definitely not what the user wants in case of a disaster, when he doesn’t want to add some new data, but simply wants to restore all his data to the point it was before the disaster.

A possible (and very simple) solution would be, that the user becomes asked when he starts an import:

  1. If he wants to use the original dates from the imported file.
  2. Or, if he wants that the original dates become overwriten with the timestamp of the import.

This would be an easy to implement solution against the mentioned data loss.
Chat and collaboration etc. are a different story that may need a different solution.

Hey hey!
The recording is now up here, and you can find the Q&A recap here.

Thanks for sharing the recording, very useful.

Re “notifications without relying on Google or Apple” - would the modern, “open” way, not be to do this through UnifiedPush?

Or allow us the users to self-host the notification via the self-hosted server