I’ve decided to create a new topic on my blog called Saturday Shorts.
I won’t have something every Saturday, but when I have something . . . a short review, review of short stories, a cover reveal, a discussion topic . . . something short, in other words!
This Saturday Shorts is about Twitter. Now that I’ve used Twitter for two or three months I have a few questions which I hope others can help me with.
I’m asking these questions mostly of people who have book review blogs, but anyone else with an opinion is welcome to comment! I don’t think these have a hard and fast answer, but I would like to have other people’s opinions who have twittered longer than I have!
- I’ve read that is something we should do–but is it necessary?
Do you send out more than one twitter about a book review? If you do, how many times do you repeat your tweet? All in the same day?
- Again, I’ve read about sending out several tweets about our posts during the day of your post.
- If you do re-tweet does it help you get more people coming to your blog?
Some of the people who become my twitter followers are people I’ve never heard of! What do you do when someone you’ve never heard of becomes a follower? Do you follow them?
- I don’t follow the people I don’t know–either by their blog or as an author or as a publisher.
- I don’t expect everyone I follow to follow me, but I don’t know the etiquette!
Do you include the author’s twitter name (if they have one) in a tweet about your book review?
- I have done this a few times when I really like the book and their twitter name comes up as I’m tweeting. I’ve had a few authors respond to my tweet and it’s been fun to talk with them, but if I don’t like a book I don’t want to add the author’s name! Also I don’t want to act too much like a fan girl…LOL! And I want to feel my reviews aren’t influenced by past encounters with an author.
- Do others worry about these things?!!
Feel free to discuss one or more of these questions and help me out . . . . Or if you have other questions or comments about Twitter . . .