thanks for helping … but I knew that one .. did that : hacked the BB PHP, which is of course far from ideal. Less about being able to, but I dont want to, since I need to maintain my hacks if I upgrade.
So you say there is nothing to “configure away” that misfeature without hacking?  Does bb.org have business relations with gravatar.com?
		
	 
	
	
	
 
		
			
	
	
		
		This isn’t hard at all.
Apply a filter to:
bp_gravatar_url
Return a url to a default image.
[EDIT]
Just noticed that bp_gravatar_url only changes the domain… the params are still added at the end of the URL.
Might try applying a filter to:
bp_core_fetch_avatar
Write a function to see if “gravatar.com” exists in the image URL, if so, return a default image.
		
	 
	
	
	
 
		
			
	
	
		
		bbPress and Gravatar are Automattic projects, as is WordPress, BuddyPress and many others. Check the full list at http://automattic.com/.
		
	 
	
	
	
 
		
			
	
	
		
		Thinkimg about your Gravatar https issue – I thought that was fixed in a recent version of BP.
		
	 
	
	
	
 
		
			
	
	
		
		thanks for helping.
 @r-a-y
i’ve already hacked bp_core_fetch_avatar() as described in https://buddypress.org/forums/topic/how-to-disable-gravatar-completely
however, a quick grep for gravatar.com over all wp/bb reveals more places. i am a total wwp/bb/php idiot and have no aspirations to become even mildy involved with the codebase. i was looking for a on-place “checkbox solution”.
 @DJPaul
ah, ok;) it’s ok to have such commerically motivated “defaults” … in the end its a pretty impressing piece of tool and its nice to share anyway. on the other hand, it would be nice to have a big “this is a private site” switch which turns off this, and other things (like the dashboard fetching stuff from outside … i “disabled” that one using a firewall rule;)
		
	 
	
	
	
 
		
			
	
	
		
		 @jivany
i’m running latest rel. of today .. the issue is there. also: the browser prob. would go away if the inserted stuff would be to https://gravatar.com, but the privacy issue would remain.
		
	 
	
	
	
 
		
			
	
	
		
		What if you removed the existing bp_core_fetch_avatar_filter from get_avatar and then created your own copy that passed ‘no_grav’=>true into the bp_core_fetch_avatar function?
I think this should kill the attempt to use Gravatar to fetch an avatar. I’m assuming that bp_core_fetch_avatar isn’t being called directly anywhere.  If you do find anywhere that does, it should probably have a ticket raised against it.