Why not simply store only a cryptographically secure (signed) random unique value on the tag itself, and keep all the other data somewhere else that all the legitimate readers are connected to?
With a simple database, this is not a problem, since it is computationally infeasable to forge a signature like that.
Is there anything that a true database filesystem offers that something like a realtime updatedb index and maybe a background updated glimpse index of/home cant offer?
I have about 18GB of files in my main home dir, and I can search it in seconds with slocate and if I need a content search, with glimpse.
I know that this kind of database FS provides a lot of cool opportunities in terms of meta-data, but how useful is it for non-techies, who usually dont name their files coherently, let alone correct ID3 tags or other other meta-data.
I think you will find that linux can be real time.
:)
For that matter, it can also be a dog, or a salad.
Why not simply store only a cryptographically secure (signed) random unique value on the tag itself, and keep all the other data somewhere else that all the legitimate readers are connected to?
With a simple database, this is not a problem, since it is computationally infeasable to forge a signature like that.
Is there anything that a true database filesystem offers that something like a realtime updatedb index and maybe a background updated glimpse index of /home cant offer?
I have about 18GB of files in my main home dir, and I can search it in seconds with slocate and if I need a content search, with glimpse.
I know that this kind of database FS provides a lot of cool opportunities in terms of meta-data, but how useful is it for non-techies, who usually dont name their files coherently, let alone correct ID3 tags or other other meta-data.
just invite more english speaking people?
Slashdot has more redundancy than that any day of the week.
If curling is a sport, anything is possible.