🍴PPPs: #1

Next ~10h over 2 weeks

Get HTTPS setup in prod
- Maybe get help with configuring ingress/networking smarter that it is.
- Will I need to break LNauth login?
Implement an early prototype of user being able to receive lightning payments, somehow, ideally based on feedback
- Get 1 or 2 people to give feedback, hopefully async (I have zero time Monday-to-Friday), about where/how payments/tips should land in the UI
Get a draft spec for recipes published into a data-model
- YAML? TOML?
- What is mandatory, what is optional?
- How smart/naive should it be?
- Are there other standards out there?

Trailing ~20h over 4 weeks

Over the last 4 Saturday nights I (that is really the only time I have):
- Forked Gitea, made a bunch of hacks (ctrl-f, replace...lots of it)
- Hand-rolled my own LNAUTH implementation (first thing I ever did in go-lang, kindof proud of myself!)
- Setup a dozen-line githook that starts to enforce a (suuuuuper early, straw-man, in-my-head-only) spec.

I had a material amount of struggles getting the LN-auth wired up, prevailed by asking for help and finding examples. Most of the issue was on my side.

Is the name good? It's not too late to change it. Any better ideas?
Can you help me try other wallets, preferably in dev, but up to you. Don't worry, I have zero code that touches anything to do with user funds yet.
What schemes might be interesting for inspiring cooks?
1. Single-tips?
2. Are the tips per recipe? Or just the user in general?
3. Should a recipe be blocked/locked until somebody tips enough to that user?
4. Should the earnings of a recipe be public?
5. Do I set up custody? Or just expect all users to have their own wallet?
6. What about users who don't have lightning hooked up yet, do I store their sats, let them build up, then expect them to collect?
Do I force e-mail registration?
Do I disable non-lightning-method registration?
Any other feedback?