My problem with bounties is say for example it's a project where multiple people want to do it (like the git on nostr thing).  The amount of work that would take and the high bounty means someone would get burned real bad if they worked on it and didn't get it.  So they have incentive to work on it without collaborating.  And it also probably requires NIPs, which are hard enough to get a consensus, even without a competition in the background muddling the situation.  So that's why we don't have git on nostr yet imho.

For strfry tho, there are so few that could do it you're probably right that a bounty wouldn't be bad for this one.. 🤔 

 100% agree that the bigger the problem scope, the harder it is, but then a big problem scope is itself a problem. I think bounties for github issues are a much better way to do these incentives, as the scope is usually much smaller. And if the issue is of a big scope then you can just create another smaller-scope issue and attach bounty to that one. 

 It was a little disappointing, the person that was trying to do this already, had hired someone to do it.. but they couldn't do it.  From what I could tell, they got hung up on the implementation details and it got more and more complicated .. similar to what mazin was saying.. there is a branch somewhere with where they left off.