TagSpaces – Open-source personal data manager
tagspaces.org
tagspaces.org
So, yeah, show stopper. Also, what's so bad about a database? Yes, the file system is very good at keeping track of files, but there are databases that largely don't get in the way, like sqlite, cdb, etc. They will sync across servers reasonably well with things like dropbox, as long as you don't have lots of people trying to concurrently do stuff from multiple places. If that's what you're doing, this kind of tool isn't right for the job anyhow.
However their approach is awful. Imagine what will happen if you tag video/audio files.
* Metadata: read/write tags as file metadata (depending on the file format) most common formats like document, image, audio, video have metadata support. http://en.wikipedia.org/wiki/Metadata
* Sidecar file: http://en.wikipedia.org/wiki/Sidecar_file and http://en.wikipedia.org/wiki/Extensible_Metadata_Platform and the Apple Spoghtlight files http://apple.stackexchange.com/questions/6707/how-to-stop-os...
* Alternative file streams: http://en.wikipedia.org/wiki/Fork_(file_system) and http://en.wikipedia.org/wiki/Extended_file_attributes
(first option is preferred)
Admittedly file managers these days at least can show thumbnails and in some cases even previews of the file which is great. They also are capable of extracting some metadata of files, but that still feels bit tacked-on in most cases. Versioning is also available in various forms, but that too could certainly be better integrated to the system.
Imho it would be interesting to see a system which would forgo our current conventions of files and directories, and instead would be more strongly be based on the concept of tags, metadata and objects.
But I got sidetracked... I meant it is nice that people are trying to rethink even a little how we manage data, even if this particular project doesn't really hit the mark for me personally.
edit: Longhorn concept video: https://www.youtube.com/watch?v=b9ifQvQCO7Y
Have you seen the WinFS trailer: http://www.youtube.com/watch?v=fZ_4p5iUc88
You can try out BeOS open source successor that comes with a BeFS compatibility called HaikuOS. I suggest you to read the BeFS book written by the main developer who later developed the Spotlight search engine for MacOSX 10.4+ and later iOS. http://en.wikipedia.org/wiki/HaikuOS , http://en.wikipedia.org/wiki/BeFS , http://www.nobius.org/~dbg/practical-file-system-design.pdf , http://en.wikipedia.org/wiki/Spotlight_(software)
Both NTFS and the newer ReFS (http://en.wikipedia.org/wiki/ReFS ) offer almost equal capabilities to BeFS. And it's a real shame that Microsoft hasn't been able to come up with a decent GUI. Even Vista had a better advanced search dialog integration than the successor's Windows 7 and 8.x
However, it's nowhere being user friendly yet and the command-line based API changes all the time.
I suppose you could use them together because you can mount your files in camlistore to the file system with cammount but it would not be easy to make them sync tags and metadata.
Also since it uses the AGPL it's a no-go for me.
Even if you did write plugins for apps and license/sell them, that would stop you from using a useful app just because you couldn't do it for that app?
I'm having a hard time following how AGPL affects you as a user of the app, not someone who's selling addons for it and not as someone who provides the app over a network.
It seems you could modify the source and run your own version without releasing your modifications and without violating the (A)GPL.
2. Yes, because I don't want to spend time learning a system that I can't extend if extending systems is my livelihood.
3. I don't want to support a community that shuns people who disagree about licensing.
4. This feels against the spirit of open source to me, to avoid having people use code, and provide feedback.
I don't believe that anyone understands the GPL including its creators. Too many things in it are vague.
AGPL: Anyone using/visiting the service need to have access to the source code.
They are very simple. The only reason people can be confused by those two is FUD, and lawyers who find such statements too simplistic.
The AGPL want that anyone who uses a service also have access to the source code. If one runs a modified AGPL service that only one person have access to, then the set of people who need to have access to the source code is that one.
That "ugliness" you mention has worked really well for my career and I know more people that think the same than people that think the opposite.