1, 2009 12:49 PM
> To: Twitter Development Talk
> Subject: [twitter-dev] Re: Draft: Twitter Rules for API Use
>
> Dean:
>
> Can you please stop posting about your individual TWITTER ACCOUNT
> issue on a Twitter developer forum? No "app" was blacklisted in your
>
Ryan, that makes total sense. The TOS is a bit unclear in that matter.
Jesse
On Fri, Sep 11, 2009 at 10:04 AM, Ryan Sarver wrote:
>
> Hey Jesse, thanks for the question.
>
> The intention here is to stop applications that are posting on the
> user's behalf without an explicit understanding of t
-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of PJB
Sent: Friday, September 11, 2009 12:49 PM
To: Twitter Development Talk
Subject: [twitter-dev] Re: Draft: Twitter Rules for API Use
Dean:
Can you
John,
I cannot do that, because my 120,000+ current user base has not opted
in for that type of communication from me.
I will get spam complaints left right and center if I did that, and my
email deliverability on emails that I do send will be severely
impacted.
For your suggestion to work, tho
Dewald,
Perhaps your application should send periodic reminder emails to
subscribers, perhaps after each status sent, but limited to once a
week? You could take the opportunity to do marketing and detail future
scheduled tweets and provide a link back to your service for schedule
editing.
-John
Dean,
What you did most probably triggered the following churn code in
Twitter, and that was why that account was suspended.
Dewald
On Sep 11, 12:41 pm, "Dean Collins" wrote:
> Basically fired up TwitterKarma to
last seasons posts and then started following people>
chatting about th
Ryan,
Careful with that one, because I have seen users say that about tweets
they specifically scheduled, but have simply forgotten that they did
so. The application is usually the first to be blamed publicly in a
tweet. It's far easier than for the user to say, "Oops, I messed up
and forgot."
A
On Behalf Of Dewald
> Pretorius
> Sent: Friday, September 11, 2009 8:43 AM
> To: Twitter Development Talk
> Subject: [twitter-dev] Re: Draft: Twitter Rules for API Use
>
> I guess the lawyers wrote this draft as an extension of the modified
>
> Twitter TOS.
>
> Alex,
Hey Jesse, thanks for the question.
The intention here is to stop applications that are posting on the
user's behalf without an explicit understanding of the action. There
are some apps that post without the user giving permission each time,
but the app needs to specify that at some point and the
ment-talk@googlegroups.com [mailto:
> twitter-development-t...@googlegroups.com] *On Behalf Of *Marco Kaiser
> *Sent:* Friday, September 11, 2009 10:43 AM
> *To:* twitter-development-talk@googlegroups.com
> *Subject:* [twitter-dev] Re: Draft: Twitter Rules for API Use
>
>
>
>
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of Marco
Kaiser
Sent: Friday, September 11, 2009 10:43 AM
To: twitter-development-talk@googlegroups.com
Subject: [twitter-dev] Re: Draft: Twitter
vechatconcepts.com
> +1-212-203-4357 New York
> +61-2-9016-5642 (Sydney in-dial).
> +44-20-3129-6001 (London in-dial).
>
>
>
> -Original Message-
> From: twitter-development-talk@googlegroups.com [mailto:
> twitter-development-t...@googlegroups.com] On Behalf Of Dewa
My reading is that twitter can blacklist an app at any time for any
reason - "Twitter may suspend or terminate your access to the API" -
That being true, effectively it means that's the rule and the other
points are really guidelines. It provides total freedom for the
Platform team. That
009 8:43 AM
To: Twitter Development Talk
Subject: [twitter-dev] Re: Draft: Twitter Rules for API Use
I guess the lawyers wrote this draft as an extension of the modified
Twitter TOS.
Alex, you will need to jump on this draft from a dizzy height and get
all your Platform rules in there.
I guess the lawyers wrote this draft as an extension of the modified
Twitter TOS.
Alex, you will need to jump on this draft from a dizzy height and get
all your Platform rules in there.
Once the API Rules are published as "The Rules" you will have no
grounds to blacklist an application for other
This document needs further detail, specifics, and allowances.
1. "Identify the user that authored or provided the Tweet"
What do you mean by this? Presumably the author of the tweet is the
person for whom the tweet appears on Twitter.com and who therefore
actually made the tweet or authorize
Jesse,
I apologize. Then I made incorrect assumptions. I thought you saw it
as the potential Excalibur in the fight against auto-DMs.
In my case, not only does the user activate the feature, he also
provides the exact text that must be sent. Not only is that express
consent, it is express instru
Dewald, I'm not heading anywhere with it. I just want Twitter to clarify the
terms, that's all. Feel free to leave your input if you have an opinion on
what those details should be.
Jesse
On Thu, Sep 10, 2009 at 7:35 PM, Dewald Pretorius wrote:
>
> Jesse,
>
> I know where you are heading with
Jesse,
I know where you are heading with this. ;-)
If a user explicitly activates a feature in an app that sends DMs on
their behalf, they at that point explicitly grants the app permission
to do so.
Dewald
On Sep 10, 10:10 pm, Jesse Stay wrote:
> This is great news! Regarding "sending Tweet
ember 10, 2009 8:55 PM
To: Twitter Development Talk
Subject: [twitter-dev] Re: Draft: Twitter Rules for API Use
Dean,
That's basically what I meant. We know those are not the only rules,
so the other rules should also in the draft, shouldn't they?
Dewald
On Sep 10, 9:50 pm, &
This is great news! Regarding "sending Tweets on a user's behalf", does
that refer to DMs as well, and when seeking permission, must it be on a
"tweet-by-tweet" basis, or can a user give you permission beforehand to have
complete control over Tweeting on their behalf? I'd like to see that part
cl
Dean,
That's basically what I meant. We know those are not the only rules,
so the other rules should also in the draft, shouldn't they?
Dewald
On Sep 10, 9:50 pm, "Dean Collins" wrote:
> No offence but can you please post these 'draft' rules along with the
> current API rules.
>
> Sorry if I s
No offence but can you please post these 'draft' rules along with the
current API rules.
Sorry if I sound 'overtly suspicious' but as you can imagine I'm a
little wary of anything that twitter inc says at the moment and would
like to have all of the rules in a single location as it causes
confusi
I expected to see more along the lines of rules of which the violation
would cause a blacklisting of the app.
No problems with what is in the draft at present.
Dewald
24 matches
Mail list logo
