<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -85,6 +85,19 @@ ActsAsFollower Methods
 
 		book.followed_by?(current_user) # Returns true or false depending on if current_user is following book
 
+- To block a follower call the following
+        
+        book.block(current_user)  
+  
+    # Blocks the current user from appearing in the followers list, and blocks the book from appearing in the current_user.all_follows or current_user.all_following lists
+
+- To unblock is just as simple
+        
+        book.unblock(current_user)
+    
+    # Unblocking deletes all records of that follow, instead of just the :blocked attribute =&gt; false the follow is deleted.  So, current_user would need to try and follow the book again
+    # I would like to hear thoughts on this, I may change this to make the follow as :blocked =&gt; false instead of deleting the record
+
 
 Comments
 =======
@@ -98,19 +111,24 @@ Props
 Thank you to Dougal and JDG for their interest and time in commiting to making this plugin better.
 Also, make sure to check out Dougal's blog about the plugin here: http://douglasfshearer.com/blog/rails-plugin-acts-as-follower
 
-ALso, props go out to Pete Jackson on his VoteFu plugin which is what I took the majority of the design pattern for this plugin from:
+Also, props go out to Pete Jackson on his VoteFu plugin which is what I took the majority of the design pattern for this plugin from:
 See Pete's plugin here: http://github.com/peteonrails/vote_fu/tree/master
 
 Pete based his plugin off of acts_as_voteable and acts_as_commentable so I should give props there as well.
 
 Thank you Pete!
 
+Thank you to  jhchabran (Jean Hadrien Chabran) - http://github.com/jhchabran and TomK32 (Thomas R. Koll) http://github.com/TomK32
+for their commits to the block/unblock problem, I took a sampling of their strategies and combined them.  Thanks guys.
+
 
 TODO
 =======
 
 * Add Example Usage code to the plugin
-* Possibly add hooks for model observer code or after_save or after_update code
-	- Any ideas on this are more than welcome, just email me.
+* Instead of adding hooks for observers and AR callbacks, I am going to convert the plugin to create the Follow model in the 
+    RAILS_ROOT/app/models folder with the generator.  No use having a ton of code when a simple generator does the trick.
+
+* Let me know if there is something else you would like to see.
 
 Copyright (c) 2008 Tom Cocca ( tom dot cocca at gmail dot com ), released under the MIT license</diff>
      <filename>README</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>112230742b1c8cea6e2f42496be5d95f7931fb3d</id>
    </parent>
  </parents>
  <author>
    <name>Tom Cocca</name>
    <email>tom.cocca@gmail.com</email>
  </author>
  <url>http://github.com/tcocca/acts_as_follower/commit/7a259646b971dfe657c33487d59f8225bf9b28cd</url>
  <id>7a259646b971dfe657c33487d59f8225bf9b28cd</id>
  <committed-date>2009-11-08T16:53:22-08:00</committed-date>
  <authored-date>2009-11-08T16:53:22-08:00</authored-date>
  <message>Updated README, thanks to jhchabran and TomK32 for their block/unblock patches</message>
  <tree>cf09748aa31837ee15344dfb89e7317fe166572d</tree>
  <committer>
    <name>Tom Cocca</name>
    <email>tom.cocca@gmail.com</email>
  </committer>
</commit>
