The core issue is brand affinity. Is it important that identi.ca the *service* is connected to laconi.ca the *product*?
IMHO the affinity is confusing and separating the two would be the best in the long run. The "McChicken" sandwhich has an affinity with the McDonalds brand. That's helpful to McDonalds to connect the sandwich and the restaurant. I don't see the same benefit here. The .ca is also confusing to the internet plebs. Rebranding the user service identi.ca would be more problematic than laconi.ca the product, so I would suggest rebranding the product. Only developers and those running a laconi.ca server will care and that's a much smaller population. Maybe identishare.com, identibridge.com, identimeld.com? Ahoy, Jason ----- "Evan Prodromou" wrote: | On Wed, 2008-11-05 at 10:56 +0800, Bo Fussing wrote: About a month ago there was some discussion about changing the project name from Laconi.ca to Identi.ca to avoid confusion between the server and the service. Was there any definitive decision on this? There was some resistance, so I backed off, but I think we've agreed to disagree on the matter. | | Q: is there a way we could get the best of both worlds? What if we called the software "Identi.ca Open Source" and the site "The Identi.ca Service"? | | -Evan | | | _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev |
_______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
