I guess I'll get the ball rolling. We're building (and close to releasing) an app that's focused on Twitter users. It has FluidDB objects that each correspond to a Twitter user. Because the FluidDB objects aren't owned, other apps can put their tags onto the objects too. The query language lets you search on objects based on any tags (that you have read permission for), so we're hoping we'll soon see a wide variety of tags on these objects, which will give us a bunch of new ways to identify users on Twitter, to tag them arbitrarily, etc. The are obvious things like ratings, or people you've met, but there are also lists (a tagged set of users is just a list, more or less) including queries that cross lists, and things like http://tunkrank.com scores about Twitter users. FluidDB gives a place to put all that stuff - without requiring you to ask permission or for your needs to be anticipated - and it gives you a way to query on it too.

That's just a first app. We'll open source it. I can think of many more, as you might hope :-)

Terry Jones (disclaimer: I work for Fluidinfo, makers of FluidDB)

Mobile carriers store subscriber information, and this causes all sorts of problems with mobile device characteristics, roaming and other special attributes that only the carriers control.

It would be great if each subscriber could own their own profile and have it synched with their own mobile device. This would require carriers to inter-operate with FluidDB, but since many of them use LDAP, it wouldn't take much to have this type of interface made available via a FluidDB client library.

This is framework of a simple application that I've been kicking around.

I plan to build a visual FluidDB query editor with DSLs on top. One may call it "language workbench". Here is http://fluidmix.org/ the site. Will be doing the query tree interface next. I believe FluidDB is a great platform for search and I intend to take advantage of it.

Hi Orlin

I hadn't been to fluidmix since you first mentioned it. the site looks really nice.

So, the lack of response is a bit surprising. Am I wrong that FluidDB is novel? Or are people just having a hard time with the idea because it is novel?

Hi Jeremy

The information model takes some time to sink in - at least for most people (including me). Examples will help people to "get" it better. We have one coming out soon (next couple of weeks). I can give you an early look if you're ineterested.