@megascatterbomb This will need to be tested, as I have not been able to test it.

I'd think the TOS text (and checking accepted date vs most current) should be retrieved from the masterbase instance by the client-backend, and sent to the webui. That way, custom UIs can have proper support for TOS, and the TOS is properly based on the masterbase instance in use. How does that compare to the current ideas?

I'd think the TOS text (and checking accepted date vs most current) should be retrieved from the masterbase instance by the client-backend, and sent to the webui. That way, custom UIs can have proper support for TOS, and the TOS is properly based on the masterbase instance in use. How does that compare to the current ideas?

To quote a message from Mega:

tos changes would only happen when the user updates the client (as that's the only time our data collection practices would change)

So combined with the fact that plans are only to support a central Masterbase, I don't think it matters too much at the moment. In an ideal implementation I would agree with you but there's probably no need.

LGTM. Will hold approval until the matching functionality of the UI is complete and has been tested.