zlacker

I've been using the alpha for the past days and it's really refreshing. Interesting discussions, and the API that is shaping up, looks really good. Congratulations and thanks Dalton.

>>terhec+(OP)
How many characters does it allow per message? From the screenshots, it looks like 256. Is this correct?

Thanks.

>>Leynos+11
Yes, it's 256 chars.

>>Leynos+11
There've actually been discussion about that. Some even think it's too much, but I guess people will get accustomed to it quickly. The upside, as I found, is that it's possible to write slightly better arguments while still keeping brevity. On Twitter I almost always hit the limit (or very close) on app.net, so far not really.

>>anu_gu+f1
This is quite the subtle design decision: It makes it more difficult to write an elegant version of the obvious App.net -> Twitter bridge.

(Such a thing might be difficult anyway - my casual reading suggests that anything beyond the most basic one-way bridge would be a Twitter TOS violation:

https://dev.twitter.com/terms/api-terms

1. All use of the Twitter API and content, [emphasis mine - ed.] documentation, code, and related materials made available to you on or through Twitter ("Twitter Content") is subject to and must comply with these Rules

5A. Your Client must use the Twitter API as the sole source for features that are substantially similar to functionality offered by Twitter. Some examples include trending topics, who to follow, and suggested user lists.

5E. You may not use Twitter Content or other data collected from end users of your Client to create or maintain a separate status update or social network database or service.

6. You do not have a license to Twitter Content submitted through your Service other than the rights granted in the Rules.

What a legal minefield. So it's probably a good idea to have an obvious guardrail to prevent people from straying too close to the minefield, and this 256-character limit is a cute way to implement the guardrail.)