[Brandon Rosage, Ushahidi] I'd like @brianherbert to explain this, since he's provided this answer many times. But as I understand it, there are two reasons...
[Charlie Harding, Ushahidi] sorry I've not seen the discussion before
[Brandon Rosage, Ushahidi] First, and most importantly, that, historically, the sensitivity and public nature of the data on deployments has created an undesirable implication that Ushahidi (the company) is running these deployments.
[Brandon Rosage, Ushahidi] Second are the technical implications of running a pretty robust company website alongside an even more robust user-generated content website.
[Brandon Rosage, Ushahidi] So "Ushahidi.io" (a placeholder for the dedicated domain for the hosted service) is intended to say "The user is on our cloud-hosted service, website, and domain now."
[Charlie Harding, Ushahidi] I don't think that .io resolves problem #1 since our name is still there, I'd like to better understand the real challenges of #2 as we create fragmentation and #3 I'd like to see examples of other companies where this is the case so that people aren't confused
[Charlie Harding, Ushahidi] Are you suggesting we use a totally different domain than Ushahidi.io, that it is just a placeholder and that we will instead use a new brand name?
[Charlie Harding, Ushahidi] I'm honestly really confused why we won't put our name on our work
[Brandon Rosage, Ushahidi] I think there's an argument to be made that "our work" and "our users' work" are different.
[Brandon Rosage, Ushahidi] And that a domain extension is a reasonably modest way to distinguish them.
[Jess Shorland, Ushahidi]@charlie, if I'm understanding you correctly, your issue is lack of consistency in user flow from ushahidi.com to ushahidi.io?
[Brandon Rosage, Ushahidi] GitHub does this, with github.io
[Charlie Harding, Ushahidi] I don't think that .com and .io make any meaningful brand difference to users other than to create confusion on destination
[Charlie Harding, Ushahidi] but I'm also willing to concede if no one else sees it as a problem
[Brandon Rosage, Ushahidi] I would prefer it all be .com. But I don't think it's too great a cost to users to have that extension change.
[Charlie Harding, Ushahidi] if it is a major security risk, then I see. But we won't escape the brand issue of people using our platform for reasons we don't like with our name extension on their deployment
[Sophie Shepherd, Ushahidi] My concern is that someone would try to go to ushahidi.io from a deployment and get lost. But if that (when it doesnt have a subdomain) redirects to .com, i dont think it would be too confusing.
[Charlie Harding, Ushahidi] I'm just opposed to fragmentation if avoidable
[Brandon Rosage, Ushahidi] This is not a wireframe. The layout, interaction, and screen will not LOOK like this. It's intended to outline the words we use, and how each plan is "additive," and what features are added with each plan.
[Brandon Rosage, Ushahidi] If you see anything that's wrong or confusing, let us know. We'll be using this outline to design the "Plans" module.
[Jess Shorland, Ushahidi]@sophie that's a good point. ushahidi.io should absolutely redirect to .com. I don't see this as a big issue at all. I don't think it will make enough of a branding difference to justify the trade-off. My sense is that to majority of cloud audiences, it's not going to matter. Ushahidi is the brand/word that matters. I can double check this with @brianherbert and @Robbie
[Sophie Shepherd, Ushahidi] Agree 100% that "ushahidi" is the part that matters
[Charlie Harding, Ushahidi] To finish the .io discussion, the only reason I see we would do it is for security/complications, not brand
[Charlie Harding, Ushahidi]@Brandon this looks good for the time being. I would grab the support text at the top of the pricing tiers. The # of SMS alerts is something we need to actually price out. This isn't set. But not a barrier
[Charlie Harding, Ushahidi] Also # of custom forms is limited in the free and standard version
[Charlie Harding, Ushahidi] sorry it will just be a lot easier to work through this stuff in person. I've been doing an immense amount of reading on this stuff and have failed on the knowledge transfer side.
It limits what we can do with ushahidi.com .. once a user registers XYZ.ushahidi.com we can't just demand that back if we want to use it for some internal use.
We already have a bunch of sites on something.ushahidi.com .. we can add exceptions for the 50+ subdomains we already have, however maintaining those over time is just an extra complication I don't want to deal with.
[Robbie Mackay, Ushahidi] on a related note.. we seem to have started using ushahidi.org for a bunch of things.. @brianherbert any chance we can pick either .org and .com as the primary?
[Robbie Mackay, Ushahidi] or set a specific purpose for each.
[Robbie Mackay, Ushahidi] another thought: crowdmap.com is a much more memorable domain.. If I have to tell someone my URL they'll remember projectname.crowdmap.com .. but projectname.ushahidi.com relies on spelling Ushahidi correctly :)
[Robbie Mackay, Ushahidi]@Charlie@jess can we get notes on basecamp for any discussions around cloud? regardless how minor..