Option to delay tweets in buffer if user already tweeted around that time.
If the user is already tweeting around the buffer timeslot, add an option to delay tweets (logic could be if tweets detected within 30 minutes, then delay 30 minutes, etc.). This would reduce the problem of too many tweets at once.
Hey David, thanks for the suggestion. We are definitely looking into how we are able to solve this problem right now. One thing that helped me, is to switch to simply Buffering everything, so I don’t get confused with it. I will see if we can brainstorm on this.
Simon Blackley commented
Buffer is great, but Twitter is not just a publication channel! A lot of the really great stuff happens in quick-fire real time. I think the real use case here is 'Avoid irrelevant scheduled tweet from Buffer in the middle of a conversation.'
2012 Mercedes Benz A-Class New Photos Released
DJ Paine commented
this is a BRILLIANT IDEA!!!!!!!!!!! i'd use this!!
I'd like to suggest a simple option while the more complicated issues are under consideration - a timer delay function on the "post this now" feature so that tweets care not sent out so quickly that the user risks being temporarily blocked from posting - popularly known as "Twitter jail". The Twitter limit is 100 tweets per hour. User activity is polled by Twitter every 10-15 minutes and the average/trend is checked to determine if the limit is likely to be breached. A simple rule of thumb delay that disables the "post now" button for 90 seconds after it has been clicked would act as a "buffer" for users to help them avoid accidentally triggering this form of censure. Not perfect, because it can't take into account tweets posted using other methods, but certainly a big help for anyone using Buffer as their main tool for ad-hoc posting
I send a lot of my tweets via Buffer so that would work. I won't put everything IN the Buffer-queue, soms are time-sensitive (like news) - for those I choose Post Now. Delay or skip tweets around this time would be nice.
Patrick Allmond commented
Leo - Here is what I am attempting to balance against. I use buffer to share out good content from my RSS feeeds that I watch. Wordpress is also automatically tweeting old content every 4-6 hours from my blog also. Personally I don't like to share anything with a link more than once every 60 minutes.
Agreed. This would work out wonderfully.
I'm unlceat as to how many tweets you're sedng out at (for example) 11am, that you'd have to push the scheduled tweet back. I mean, I can understand if you just sent 20 in a row, but to push back the 1 or 2 scheduled then doesn't make much of a difference. If it's just one tweet and then the scheduled one, then tI don't think two ina row (or within a few minutes of each other) will bother anyone. That's not much "congestion."
Seconded. This will avoid congestion
Here's what my ideal delay setting would look like:
[ x ] Skip schedule tweet if I've tweeted in the past (text field) minutes
[ x ] Ignore @ replys
[ x ] Ignore retweets (will also ignore any tweet beginning with "RT" or "MT")
Daniel Foster commented
this could be used to allow multiple people to contribute cool things they see without having to worry about conflicting with an important broadcast tweet
Oscar Gonzalez commented
This would be awesome. I'd vote for not taking @replies into consideration. Just regular tweets.
And take @replies into consideration (don't count that as a tweet). Option like "Skip a timeslot if this account sent a non-@reply tweet .. minutes before"?