i'll keep the points from this blogpost inside this thread, to avoid a spam explosion of one-message threads. if any of these points lead to discussion, we can fork them out.
we already had two data points about App.Net:
from the blogpost, i think we can extract the following extra ones:
2 - simple and easy to follow (i agree)
3 - pseudonyms allowed, good! i agree! this is an online identity provider, so keeping your personal life separate from your online life is important, and it's good that (unlike e.g. Facebook and Google+), App.Net allows this.
4 - you are responsible for what you upload, and some types of content are not allowed. specifically (the blog post mentions this further down under 'Copyright'), if you post copyrighted material to which you have no license, they will take it down and close your account
5 - the copyright license you give them is "limited" - good! the terms also state: "Aside from our limited right to your content, you retain all of your rights to the content"
6 - if you delete content, it is hidden from view immediately, and deleted entirely from their servers in max. 2 weeks. "It is then gone forever." - good!
7 - "breach of any of the rules outlined in the terms of service — including those above — may result in you losing your App.net account, and access to the service." - that's good because it's conditional on there being a reason to terminate your account. a lot of other services claim the right to terminate your account for any reason and/or at their sole discretion.
8 - their technology is proprietary, as is their logo and name, and you may not extract the content from their website. They state this under the "App.Net's Content" section, but it seems to also cover the content that other users upload. The blogpost doesn't explicitly pick on that last part, and i think that although this last part is unfair if you view them as a hosting provider, it is probably fair if you view them as a closed platform. that is, if a person publishes through App.Net, that content is not considered to have been published to the web in general, it is considered to have been published specifically to App.Net, and so App.Net mark their territory around that user content. A competing service may not scrape and republish it, regardless of whether the user who wrote and owns the content would allow that competing service to do so.
9 - App.net does not take responsibility for what its users post, whether on App.Net, or on website that have an inbound or outbound hyperlink with out.
10 - the review of the legal stuff is interesting, i would like to know also what Hugo and others think of this. I have read the all-caps part twice, and the second time it seemed to state that as a user you cannot sue them, except for the 50 dollars (or whatever 12 month fee) you paid. It does not mention class action lawsuits, but i'm not entirely sure where the line is and how we should judge this. Given my own limited understanding of this topic, we need to discuss it further to reach a clear conclusion, i think.
I'll ask Andrew to comment whether he feels this is an accurate selection of data points extracted from his blog post.