It's really hard to stomach tr.im's gushing benevolence in creating a new,
community owned and operated URL shortener being that they only arrived at
this model by failing to secure venture capital (and by freaking out their
massive user-base with such PR blunders as last week's "tr.im R.I.P." and "
tr.im to December 31, 2009" blog posts!). Eric, please stop soap-boxing
poetic about the "walled garden" and relinquish control so those still using
tr.im can all get on with their business.

There, my hat is in the political arena.

Art Thompson, Jr.
Logical Things - Design + Technology
917-609-1158 [m]
512-692-9865 [w]
www.logicalthings.com
linkedin.com/in/logicalthings
twitter.com/logicalthings


On Mon, Aug 17, 2009 at 3:26 PM, Warren <[email protected]> wrote:

> http://blog.tr.im/post/165049236/tr-im-to-be-community-owned
>
> for those that want to read all the drama straight for the source.
>
> It's definitely shaping up to be something interesting, but I'm doubting it
> will change the relationship that bit.ly has with Twitter considering what
> they share in investors and relationships.
>  On Mon, Aug 17, 2009 at 3:14 PM, Alex <[email protected]> wrote:
>
>>
>> This has turned out far better than I ever expected - Tr.im has
>> announced that it's going to go open source and be community owned:
>>
>> http://www.readwriteweb.com/archives/trim_to_go_open_source_community_owned.php
>>
>>
>>
>
>
> --
> Warren
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
Our Web site: http://www.RefreshAustin.org/

You received this message because you are subscribed to the Google Groups 
"Refresh Austin" group.

[ Posting ]
To post to this group, send email to [email protected]
Job-related postings should follow http://tr.im/refreshaustinjobspolicy
We do not accept job posts from recruiters.

[ Unsubscribe ]
To unsubscribe from this group, send email to 
[email protected]

[ More Info ]
For more options, visit this group at 
http://groups.google.com/group/Refresh-Austin
-~----------~----~----~----~------~----~------~--~---

Reply via email to