Nope. Mostly because I don't have a clue how to use it, and that's my only "legitimate" critique, I suppose. Lots of "cool, whizbang nostr stuff" requires way more time and effort to put in to getting working. This comes down to two things:

1. Horrifically bad coding, leading to very inconsistent performance or just not working, then the dev getting bored with it and squirreling off to another idea letting their bad code flop in the breeze.

2. Personally not having the understanding of WTF is going on and it not being simple enough in concept or execution for an idiot like me to utilize on my own hardware in, like, 15 minutes.

So, for blossom:

I don't understand what it is, how it is supposed to work, or if it is even worth bothering with since I don't trust the devs who are currently working on it to actually follow through to get a stable, simple to set up, easy to use, and most importantly, reliable thing.

I'll use hazard as an example:

Nostrudel is horrifically broken. No effort is being put into fixing it while hazard is off in Blossom-Land, and, to me, this is not the character of a person that I respect to be to build anything lasting. I can see how a person acts and reacts to situations. I don't like what I see, no matter how smart or capable someone is, I much prefer boring competence at basics.

I just don't like supplanting NIPs for shiny toys. I also don't like how opaque much of the NIP repo has become. Mind you, I'm not and never, ever want to be part of that directly, as I have way more important stuff to be concerned with and spend my precious little time on.

Very few people are addressing the current flaws in the Foundation of the nostr protocol. Building on a broken foundation is stupid. All the reasons given for it are immature and/or driven by greed, since, I'll yet again mention the market distortion pushed by the VCBRO mentality jerkwads.