Skip to content

Calls

Jump to bottom Edit New page
Moritz Kaminski edited this page Sep 28, 2022 · 19 revisions

Going forward

Community calls happen every Thursday at 1pm UTC.

2021-12-27

2021-12-20

2021-12-13

2021-12-06

2021-11-29

2021-11-22

2021-11-15

2021-11-07

2021-11-01

2021-10-25

2021-10-18

2021-10-11

2021-10-04

2021-09-27

2021-09-20

2021-09-13

2021-09-06

2021-08-30

2021-08-23

2021-08-16

2021-04-26

General

  • Tiny PRs that are easy to review
    • Cosmetics always in a seperate PR, otherwise it is hard to see if something changed or if it is unrelated costmetic changes
    • If possible: commit messages and PR descriptions describe WHY doing the change?
  • Design: we need mockups for functionality before implementation and agree on the features and processes
  • Discussion about the Core Design Goals
    • Who is it for (short-term? mid-term?)
    • What should it do? / What's the pitch?

Roadmap

  • UI implementation in order to show functionality and make it easier for people and developers to use
    • Welcome/Onboarding screens as proposed by Johns
    • Popup
    • Prompts (payment/enable)
    • Options for configurations
  • Allowances
  • LNURL-pay
  • LNURL-auth
  • Testsuite

Experiments

  • Donation metatag (with LNURL-pay)

WebLN

  • Updating the current spec and doing a RFC

Native Companion Apps For Extensions

  • What are they?
  • How do they work?
  • Why could they be helpful for us?

PR #54

Messaging

  • I find the messaging pretty confusing and we quickly spread functionality accross the app
  • Messaging has limitations:
    • Every message handler receives EVERY message always
    • Added message handlers will stay around and will receive all future messages
    • Security considerations when communicating with the inpage/content script
Current Setup
Communication between the website and the Content Script
Communication between Content Script and Background Script
Questions?
Should we use Redux?
  • seems to provide a standardized way?
  • we don't need custom messaging
  • clear architecture, used by others
  • joule uses it, too.
  • learning curve is quite steep it seems

Encryption

  • What should be encrypted?
  • What should not be encrypted?
  • Having everything encrypted limits the functionality of the the extension because the user will always have to unlock the extension first.
  • Shuld the extension get locked after a certrain period of time automatically? (=> problem that functionality does not work if everything is encrypted)

https://github.com/getAlby/lightning-browser-extension.wiki.git``

Clone this wiki locally