Hi,
The version of AEM you're using makes a difference. Regardless, the basic reply is that this has nothing to do with reverse replication.
Up through AEM 6.0, the blog feature was based on a page template and content was only entered in the author environment and published (forward replication).
Starting in AEM 6.1, the blog feature was migrated to the Communities social component framework (SCF), and became a feature that allowed content to be entered by community members in the publish environment.
SCF does not use replication to copy UGC, as there are no copies. Instead, there is a common UGC store that all author and publish instances reference, commonly called SRP. Except there is one implementation of SRP, the JCR SRP (JSRP), where the one store is only shared among publish instances configured as a publish cluster. And is not shared with author at all. Since JSRP is the default, if you entered a blog article on publish, you would never 'see' it on author.
One quick clue to know if a node is an SCF component is whether the sling:resourceType property has a value that follows the pattern "social/foo/components/hbs/baz", where hbs refers to Handlebars scripting language.
To learn how the AEM Communities capability does use replication, see Deploying Communities : Configurations : Replication Agents on Author
Hope this helps.
- JK