Two hours later three Belzer's knocked on my door. Really friendly fellows. I played Rav Reuven' recording. "That is exactly our policy at Hidabroot. We never go after goyim or intermarried couples. They are always referred to us by Rabbis after they have come one their own accord." I said well what about your ads and I displayed it on my computer. It clearly is proselytizing and mentions nothing about rabbis or kiruv organization providing recommendations. Their answer was that this was an old ad that had long ago been changed. I said but this has run for the last two years. "On no that is an old ad - we don't proselytize. In fact there has never been any seminar that we are associated with here in Israel that tries to attract goyim or had attendees that have not been associated with a kiruv program for 1 or 2 years.
In short we had a great session where we all agreed that proselytization was wrong and that only when dealing with a tinok shebisha who didn't know intermarriage was bad would they allow him to participate - after he came willingly. (Of interest they brought a laptop which they asked to connect to my WiFi which I did).
Then out of left field they asked me why a blog named Daas Torah was full of shmutz and Tropper's sexual scandal. I explained that it was important that people know what had happened and that this would motivate people to take it seriously and do something about it. "But how can you have a blog called Daas Torah" - they said in Hebrew since they didn't know English. We have people who are seriously involved in Torah and they go to your blog to see Daas Torah and they get shmutz. They said they have received a lot of complaints about my blog from Belzer chasidim. This was really surprising. Non English speakers being corrupted by my blog because they thoroughly read through every posting and all the comments and they discover to their horror that it wasn't Hamodiah. After I tried explaining several times I said lets go ask Rav Sternbuch - whom they had never met. I called his home and was told he was leaving for the 2 minute walk to shul for mincha. We piled into their car and found Rav Sternbuch climbing the stairs leading from his apartment to the street. I introduced them and told them to ask their question - which they did. Rav Sternbuch explained that of course there was no need to discuss shmutz in regards to Tropper.They looked at me with smug grins and said we told you so. I tried explained to Rav Sternbuch what and why I was doing because he had never expressed such concerns before - but he just said , "Why mention disgusting things "and went in for Mincha. They talked for few mintues with Rav Sternbuch's gabbai and they left with a condscending, "Don't forget to take off all that shmutz - it is Daas Torah right after mincha because you follow Daas Torah." I went in to daven confused.
After Mincha, I went to ask Rav Sternbuch for clarification. He said, "I thought they were asking whether they needed to read about the shmutz. I didn't realize they were talking about the articles that you are mefarsem. You can use your own judgment about what you write. Just don't be explicit about the nature of the disgusting activities. But there is no problem to say that Tropper is a menuval or a sheigitz (Megila 25) and in fact it should be publicized that he is a menuval."
So now we have a situation where they will claim that I don't listen to Daas Torah when they go to read my blog and see all the postings about Tropper are still there - which was clearly the actual reason they came to see me. In fact, however, Rav Sternbuch thought he was answering a question about what they should do - not what I should be doing. He felt it was irrelevant and bitul Torah for these chasidim to be reading about the depravity of Tropper when it was enough they knew about it. On the other hand he felt that there was a to'eles for me to be mefarsum the nature of the scandal. The lesson is clear - don't ask a posek an important question when he is rushing to daven mincha - unless you can ask him to clarify it afterwards.



