FluidDB domain names available early (and free) for Twitter users
Sometime in the next few months, Fluidinfo will launch an alpha version of FluidDB, the database with the heart of a wiki. It’s a big engineering task, and there will still be a lot to do when we go into alpha, so we’ll initially only have a small number of applications being built on FluidDB.
But that doesn’t mean you can’t get into the action early.
Starting today, we’re pleased to offer FluidDB domains for free to Twitter users. This is perhaps the simplest way you’ll ever sign up for a new web service – if you’re a Twitter user:
Simply follow FluidDB on Twitter.
Yes, that’s it. You’re done.
Later, when we create your FluidDB domain, we’ll send you your FluidDB password via a direct message in Twitter. Note that we haven’t asked for your real name, your email, a password, sent you a cookie, or asked you to fill out a pesky sign-up form. The point here is simply to give you an early opportunity to trivially claim your preferred name.
Feel free to tweet the URL of this posting (http://bit.ly/bezc). You can follow me too for extra credit. If you’re not already a Twitter user and you want a free FluidDB domain name, sign up for Twitter, and then follow FluidDB.
Mini FAQ:
Why would I do this? By following FluidDB you will reserve your (Twitter) user name as your domain name in FluidDB.
Is there any charge? No.
What is a FluidDB domain? Sorry, but you’ll have to wait to find out the answer to this. We can tell you though that FluidDB domains will have many uses, and that they wont all be free.
What if I change my mind? Just unfollow FluidDB on Twitter.
Why Twitter? Because we like Twitter. We may do a similar thing for other services, allowing users to later claim their domain via OpenID, but that introduces the potential of naming conflicts.
Finally, please note that we can’t give an iron-clad guarantee that you’ll get your Twitter user name as your FluidDB domain name, but we’ll do our best. At this early stage of the game, we reserve the right to do whatever we want :-)
You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.
January 25th, 2009 at 12:58 am
This is sooo intriguing! Thanks for the opportunity to be a “lab rat,” its an honor.
January 25th, 2009 at 1:58 am
This is sooo intriguing! Thanks for the opportunity to be a “lab rat,” its an honor.
January 25th, 2009 at 1:34 am
Hi Leslie – thanks :-)
You can find out a bit more here http://www.fluidinfo.com/terry/2008/12/04/twittendipity-a-chance-interview-with-robert-scoble/ in case you’re curious.
Terry
January 25th, 2009 at 2:34 am
Hi Leslie – thanks :-)
You can find out a bit more here http://www.fluidinfo.com/terry/2008/12/04/twittendipity-a-chance-interview-with-robert-scoble/ in case you’re curious.
Terry
January 25th, 2009 at 12:50 pm
Great to see things are marching on!
the twitter sign up is a wonderful idea! only a follow button away!
kudos to you, can’t wait to try fluiddb out
January 25th, 2009 at 1:50 pm
Great to see things are marching on!
the twitter sign up is a wonderful idea! only a follow button away!
kudos to you, can’t wait to try fluiddb out
January 25th, 2009 at 7:34 pm
Hi Emanuel! Thanks for dropping by. Did you read the article on Chinese by David Moser I sent?
Terry
January 25th, 2009 at 8:34 pm
Hi Emanuel! Thanks for dropping by. Did you read the article on Chinese by David Moser I sent?
Terry
January 26th, 2009 at 8:40 pm
Hi! Would you do the same for http://identi.ca users?
January 26th, 2009 at 9:40 pm
Hi! Would you do the same for http://identi.ca users?
January 27th, 2009 at 11:03 am
> allowing users to later claim their domain via OpenID, but that introduces the potential of naming conflicts.
A URI is unique, that’s the right way to deal with that on the Web.
January 27th, 2009 at 10:03 am
> allowing users to later claim their domain via OpenID, but that introduces the potential of naming conflicts.
A URI is unique, that’s the right way to deal with that on the Web.
February 2nd, 2009 at 10:04 pm
Hi @Elliot
Sorry for the very slow reply. Right now I’d rather not think about naming conflicts, though I guess there’s an easy solution (FCFS). If you want a domain, you could create a Twitter account & follow FluidDB. Or if you don’t have the name you’d like (taken on Twitter), send me a mail and we’ll se tit aside for you (if it’s not taken). If you’re wondering about identi.ca as a class of users, I agree it’d be nice to do. There’s no real reason why not, but I probably wont do it anytime soon.
Thanks, and feel free to ask again! :-)
Terry
February 2nd, 2009 at 11:04 pm
Hi @Elliot
Sorry for the very slow reply. Right now I’d rather not think about naming conflicts, though I guess there’s an easy solution (FCFS). If you want a domain, you could create a Twitter account & follow FluidDB. Or if you don’t have the name you’d like (taken on Twitter), send me a mail and we’ll se tit aside for you (if it’s not taken). If you’re wondering about identi.ca as a class of users, I agree it’d be nice to do. There’s no real reason why not, but I probably wont do it anytime soon.
Thanks, and feel free to ask again! :-)
Terry
February 6th, 2009 at 6:17 pm
ready!!!
February 6th, 2009 at 7:17 pm
ready!!!
March 16th, 2009 at 2:18 pm
For some reason (and I realise this is irrational) it seems strange to me to write apps that are forced to claim parts of yet another new namespace. It has kind of an AOL keywordy feel to it. Yet I realise that sites like del.icio.us, myspace etc al all have write-once-and-that’s-it namespaces.
Twitter at least provides some flexibility – I was able to rename from “goldsounds” to “danwalmsley” easily and instantly.
Ultimately, I think the primary namespace for all online transactions will be DNS. Any service that doesn’t respect the primacy of DNS as a means of pinpointing my identity in the online space doesn’t sit right.
But now I’m straying into my own company’s yet-to-be-released products, and that would violate all sorts of agreements… blech. Stupid IP.
March 16th, 2009 at 3:18 pm
For some reason (and I realise this is irrational) it seems strange to me to write apps that are forced to claim parts of yet another new namespace. It has kind of an AOL keywordy feel to it. Yet I realise that sites like del.icio.us, myspace etc al all have write-once-and-that’s-it namespaces.
Twitter at least provides some flexibility – I was able to rename from “goldsounds” to “danwalmsley” easily and instantly.
Ultimately, I think the primary namespace for all online transactions will be DNS. Any service that doesn’t respect the primacy of DNS as a means of pinpointing my identity in the online space doesn’t sit right.
But now I’m straying into my own company’s yet-to-be-released products, and that would violate all sorts of agreements… blech. Stupid IP.
March 20th, 2009 at 2:00 am
Hi Dan
I’ve not really said what a FluidDB domain is, and as a result I’ve created a confusing impression.
Apps wont be forced to claim a domain. Like many other online services, you’ll have some form of identity within FluidDB (call it a username if that’s more comfortable). You’ll use that to connect, and that name will be associated with your data. It can be flexible, just like Twitter.
We’re not trying to challenge or replace or add to DNS.
I’ll make all this clearer a bit later. For now I apologize for the confusion, and hope I can reassure you that the things you’re uneasy about are a result of me being deliberately vague at this point. I want to get a bit further along before we say too much more. That’s mainly due to my own uneasiness at letting the talk/hype get too far ahead of the product – and due much less to stealth, etc.
Terry
March 20th, 2009 at 3:00 am
Hi Dan
I’ve not really said what a FluidDB domain is, and as a result I’ve created a confusing impression.
Apps wont be forced to claim a domain. Like many other online services, you’ll have some form of identity within FluidDB (call it a username if that’s more comfortable). You’ll use that to connect, and that name will be associated with your data. It can be flexible, just like Twitter.
We’re not trying to challenge or replace or add to DNS.
I’ll make all this clearer a bit later. For now I apologize for the confusion, and hope I can reassure you that the things you’re uneasy about are a result of me being deliberately vague at this point. I want to get a bit further along before we say too much more. That’s mainly due to my own uneasiness at letting the talk/hype get too far ahead of the product – and due much less to stealth, etc.
Terry
September 22nd, 2009 at 2:52 am
fashion shop|fashion in shop|fashionable|fashionable shop|online shop|fashionable products|clothing|bags|shoes|rayban|pumps|sandals|sunglass|Anna Sui|Chanel|Coach|Gucci|LV|mongram|tous|Balenciaga|AF|Abercrombie & Fitch|Man's Beach Shorts|Man's Jean|Man's Overalls|Man's T-shirts|Women's Sun-top|Women's T-shirts|jimmy choo|Manolo Blahnik|christian louboutin|Yves saint Laurent|MUMIU|Vanies|Ray-Ban|Jewelry|fashionable sale
October 5th, 2009 at 4:15 pm
Thank you my dear brother
On this post
It's a very useful and wonderful
Best wishes you success
November 11th, 2009 at 2:28 pm
You can register free domains at 3ld.biz!
November 24th, 2009 at 8:07 am
3ld.biz and fdomains.net have become seperate entities. fdomains.net now offers Free domain names! No catches, no advertisements!
January 18th, 2010 at 7:47 am
I still don't know what FluidDB domains are and it's been an year. Is there any chance you can come back to this post and give us some explanations?
_______
Frank C. Tannehill
Domain name
January 18th, 2010 at 8:07 am
Hi Frank
Yes, it has been a long time! :-)
A simple way to think of a FluidDB domain is that it's just a FluidDB user name. But it has some characteristics of a domain too, the main one being that it is included in the identifier you use to label tags on FluidDB objects. For example, you might put a frank/rating onto an object, with a value of 6. That piece of data (the 6) has a name associated with it (frank/rating) that can carry trust and reputation, just as when you see a label like http://www.amazon.com/….. you immediately know the data associated with it (a web page) is reliable. Domain names are mainly used to label email addresses and web addresses, and FluidDB extends this to smaller pieces of data, like strings, integers, etc. So you can imagine that if Amazon had the amazon.com domain (username) inside FluidDB, they could put amazon.com/price tags onto objects and people seeing that tag name would know the associated data was reliable. FluidDB has a permissions system which ensures that only Amazon can put amazon.com tags onto objects.
Does that make sense?
Further, all FluidDB domains are reserved for the corresponding owner of the real internet domain. So only Amazon can get hold of amazon.com inside FluidDB.
Sorry for the long delay! FluidDB is now launched, as a private alpha. If you'd like to play with the API, please let me know.
May 17th, 2010 at 12:49 am
I appreciate the concern which is been rose. The things need to be sorted out because it is about the individual but it can be with everyone.
==============
Domain Names
December 25th, 2010 at 6:51 am
FluidDB domains we are having a website on Domain sale but we never heard of this TLD.
January 15th, 2011 at 8:32 am
Thanks for your information:)
February 10th, 2011 at 3:25 am
I want to have a unique domain name. How can I do this using FluidDB? I like twitter and the convenience that just by following FluidDB, I can have my own domain.
http://blungr.com/?p=myka