The idea behind this AP-like system I'm working on is that it is _multitenanted_ (technically multi-single tenant, but multitenanted for all external purposes). The idea is that you can have multiple groups operating on a single server. The server _may_ have an address of its own, but the individual tenants could have their own entirely separate domains. so: `social.example.com` could be a different tenant from `example.social` but both hosted on the same backend **server** and have their own moderation, their own everything as far as the app goes. In order to do this, I'm implementing what essentially amounts to **row level security**: so if you send a message to social.example.com and you are on example.social this will end up with two distinct database entries for the message, etc. This has several advantages, the least of which is that it makes removing a tenant and shipping them elsewhere comparatively easy since we only have to lock your rows and you are the only one accessing your rows. Now the question is: do I want two copies of the _data_ and the answer is… probably I do, but it needs deeper consideration because data is more expensive. The answer may be "yes for local data, yes for remote text, no for remote non-text data that is really being cached anyways." But I need to think about it more.