That doesn’t matter all that much as each NC has its own shard and a long as any shard is aware of the other shards it can act as a controller in a distributed search.
Problem is the shard indexes are being stored in the system partition, but really should reside on any added storage.
@Cult I am a noob with NC but so far I don’t see anywhere security ACLs are being provided to the shard.
So when you do a full text search there is no way to limit the result set to those are who authorised and the current highlighting context is breaking current security mechanism?
I really like the idea of federated p2p storage and p2p indexing as hugely important knowledge bases can be created in ad hoc networks. From a distributed wikileaks to advocacy or legal a secure p2p storage and indexing system could be hugely beneficial and of much use to many.
Storing entities as integers is fubar though and they should be UUIDs and looking at the database the same is true of the ACLs.
UUIDs should be used for all entities that are visible and fast integer indexes should be purely an internal process.
You could have thousands of users on thousands of NC’s with thousands of GB with no break in user privacy apart from what has been granted.
NCs could have public, trust relationships and private data and both the share and index would be representative of this.
With the current database using integers and my noob status where I haven’t seen any form of UUID entity reference or ACL scheme then really you can not federate at all as you are always taking the risk of a duplicate entity ID.
I think Nexant is extremely important to Nextcloud but currently struggling to see how it is not going to cause problems with system storage and security. Thing is its the manner of the core and operation and my concerns are a bit chicken and egg as Nexant (Solr) can work in that manner, or could.
As I say don’t take my word for it though as I am still struggling to get my head round the individual file encryption methods where the database is hold a hash for each file rather than and encrypted file system.
I think the answer to a secure index is just to bung it on a encrypted file system and hold a file system hash, but probably displaying in all glory tremendous noobness.
https://wiki.archlinux.org/index.php/Dm-crypt/Encrypting_an_entire_system
You could have an extremely small embedded system running huge volumes and indexes with full text but as storage is added via LVM and maybe the files would have individual encryption and the corresponding index could just be an LVM encrypted partition holding the index.
But currently I am wondering why NC is encrypting files rather than volumes?