🍴PPPs: Week 4 - ForkableRecipe.com

Plans 📆

Do 2 or 3 of these 4 things. I don't think I'll get all of it done, and some are risky.

• Get stats about payments on a per-recipe basis exposed in UI

  • Question 1: Are there unique failure modes surrounding lightning address payments? Docs somewhere on this?

• Figure out withdrawals, maybe implement

  • Question 2: How should I think about fees for this?

  • Question 3: Are attack vectors documented somewhere?

• Figure out if I have flaws with my thinking on UX-Directed Temporary Custody.

• Swap out [email protected] for user's submitted lightning address on the profile page.

Progress ✅

• ✅ As planned - Got a lightning node w/ 2 channels set up! Check it out on Amboss.

• ✅ As planned - Got a way to send sats to a recipe set up!

  • Used a fork of ligess for lots of inspiration (I owe Dolu89 a PR, or at least a write-up, about my experience. Major shout-out warranted! No way would I have got this working without that repo!)

  • The design uses a [email protected] lightning address concept.

  • Example is in upper left hand corner of the only recipe page on the site right now:

• ✅ Bonus Progress - Got [email protected] added to profile pages too!

Problems ✋

• It's hitting me like a ton of bricks, that I have to build features that automatically send sats, and that comes with major security/attack-vector considerations.

• I definitely wish an app could detect a lightning wallet's existence. The pre-coiner experience is hurt by this. They just get a button that does nothing. Idea: javascript that pops up once for everybody that explains what it is...kindof shitty UX.

Links 🔗

Direct links that show stuff working (notice the various lightning addresses underneath the buttons with the lightning emoji)

• https://forkablerecipe.com/juan or https://forkablerecipe.com/bumi

• https://forkablerecipe.com/jeffrey/berry-smoothie

• https://forkablerecipe.com/explore/repos