Very cool. Going on my list for the next time I make it to Chicago!

👀 what’s the spot???

Will do! It’s definitely disappointing when you have a dud. This was probably my worst yet, but it’s been amongst lots of other successes!

I do feel like a bit of an idiot - I for some reason thought the joule app wouldn’t have venison roast, but there it is… would have saved our meal!

Thanks, maybe I will try it again sometime - we were gifted a joule, but now I’m going to be nervous to go off the beaten path with the sous vide in terms of new cuts. Should have stuck with my standard reverse sear on the smoker and finished CI in this case! Trusty thermometer never lies and it seems like the sous vide does weird things to lean cuts

This is the current version of spec for long-form for reference. Seems like iii is the most flexible, but more work for you all of course.

“Post Approvals of replaceable events can be created in three ways: (i) by tagging the replaceable event as an e tag if moderators want to approve each individual change to the repleceable event; (ii) by tagging the replaceable event as an a tag if the moderator authorizes the replaceable event author to make changes without additional approvals and (iii) by tagging the replaceable event with both its e and a tag which empowers clients to display the original and updated versions of the event, with appropriate remarks in the UI. Since relays are instructed to delete old versions of a replaceable event, the .content of an e-approval MUST have the specific version of the event or Clients might not be able to find that version of the content anywhere.”

I do love the idea of how generally useful a wrap could be though I admittedly haven’t wrapped my head around how it might work with replaceable events.

I guess that would enable the community to keep a copy of the original event of an edited long-form, but also notify users that a new version is available but unapproved.

Bitcoin maxis are definitely prevalent (I’m not an outspoken one but I don’t mind it)

I do suggest finding people who you like and checking out their follower list. On some clients you can even do a “read only” log in with their npub

This horrendous recipe was the first result on google.

Suggests 12-14 hours (at 135 for med rare) for a 2 lb roast. Rest of the internet makes it seem like it should be more like 3-5 depending on preference and probably fat content. Just a good reminder to not blindly follow any online recipe

https://www.themeateater.com/cook/recipes/sous-vide-venison-roast-recipe

Fantastic. Thanks! I made some comments on the moderated communities PR regarding long-form moderation since I expect those will be preferred by some communities (cause of widespread markdown support and edibility).

There are multiple approval options listed in the nip, but it would be great to get your insights since you are leading the way in terms of the actual implementation!

https://github.com/nostr-protocol/nips/pull/602

If that’s the norm on your feed you need to curate your feed better. Nostr is what you chose to see and I don’t see any of that bullshit.

It was so soft it was hard to cut. If you look close you can even see the marks the knife left on the cut surface. Learn from my mistakes 😂 nostr:note1yhm9sfg95wny57z8vcdxj3veh04h773um5792aa3w4gzrh704agqmvugkk

It was a venison roast. Texture almost looked like a tongue and it almost felt like it had been pre-chewed it was so soft. I’m sure all of the connective tissue was just completely obliterated.

This was a lean venison roast which was new to me. Made the mistake of following the first set of directions I found online and should have realized it was 2-3x too long. The recipe for some reason said 12-14 for a 2 ln roast which is very obviously incorrect in retrospect. Embarrassing, but now I know what the consequences can be when you really overdo it. Had always wondered

Have you ever had meat that’s been in the sous vide too long? I won’t make that mistake again.

I love this addition! A couple questions so far…

- will there be an approval flow for articles? I’ve noticed habla.news generally ignores the approval event for now as well.

- would it be possible to get a url to show the note on a fully featured long-form client or at least a way to copy the ID? I’ve noticed some embedded content doesn’t render in kiwi.

Thanks for the awesome work on this!

Yeah hopefully most clients will get that fixed. Then again there is something about knowing it will repost that makes me not want to edit as much - maybe that’s feature in its own right 🤔

Love that these long-forms are showing up in more and more feeds!

That meal that looks oh so good, but tastes oh so bad. Thank god tomorrow is Friday

Back in the good ol’ invoice days 😂

Someone should make this a long-form doc… Great opportunity to show off habla and others and ditch google!