On Sat, May 9, 2009 at 10:54 PM, Yuri Takhteyev <[email protected]> wrote: > >> I can't. At least not until I wade through the new terms of service. >> And if I disagree with that terms, I'm locked out of the data I've >> stored there. Locking out users without any warning is not nice. > > +1 > > And there are things to disagree with. > > "the Content is not spam, is not machine- or randomly-generated" > > I guess code that includes base64-encoded images is no longer allowed...
I see you point and agree, at least in your example. What the paragraph is referring to, in spirit, is things like spam-scripts hammering comment fields and so forth. Machine generated code in the terms of code-generation and so forth is fine. I'll talk to the people who know the legal aspects of these matters and find a way to reword it to what it's intended to convey. > The indemnification clause is also a little aggressive, especially > when combined with the lack of promise to remove the content on > request. I think you've misread it, we cannot reasonable remove cached or otherwise referenced (backups come to mind) content right away, but within reasonable time. > Another issue: all the links are now broken. Can you do something > about this? (I actually liked the old URL organization better, but I > suppose it wouldn't matter so much if proper redirects were in place.) I'll admit I still got a few redirects to do, could you send me the urls to the things that break? thanks > > - yuri > JS --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Gitorious" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gitorious?hl=en -~----------~----~----~----~------~----~------~--~---
