Now since this concerns perhaps my biggest personal failure of 2025, the topic is a bit of an open wound for me, and I do understand your position as ''zapcooking'' in all of this....but ( 😅 ):

The fact clients were sort of forced to include special behaviors on an existing kind, like primal actively filtering, is the crux here. A recipe kind could/would be a nice first example of ''partial kind rendering'', something i don't think we really have thus far. i.e. a ''general'' client like primal could half-ass the recipe implementation, only showing the bare minimum and pointing their users in the direction of zapcooking for a better/more complete experience. It would be a win-win where Primal only spends minimal time on implementing the kind such that their users don't experience broken references in their feed while browsing primal irt something Primal generally have no interest in putting much effort in anyway, whilst it would give zapcooking (and other potential recipe apps) room to shine in terms of features. Because as it stands, Primal spend that time anyway, in a way that sets a bad precedent (not their fault) for the ecosystem as a whole. Anyway, this whole notion should, in theory atleast, ease the whole implementation lobby process.

Hope you had a good talk with nostr:npub1ehhfg09mr8z34wz85ek46a6rww4f7c7jsujxhdvmpqnl5hnrwsqq2szjqv about it?

Il retreat from the discussion now, ive kind of spend my credits to weigh in anyway, so il just wish everyone a happy new year :)