Optimally, parts of this repo should become an LNbits extension:

• Most of what is currently in settings.json could be set via UI
• API endpoint that serves as redirect for Streamlabs access_token (essentially wait_for_token.py)
• webhook.py as background service

The extension should also allow modification of the donation format that is sent here.

The extension's front end would ideally be a simple tipping form that asks for "Name," "Message," and "Amount" in either sats or any of the supported currencies, converting the amount to sats to create an invoice.
Another option that would be great to have available is a Twitch login button that auto-fills the "Name" field, and sets the identifier to a unique ID value, like the Twitch User ID (see here).

I've created a branch to work on this: https://github.com/Fittiboy/lnbits/tree/TwitchAlerts Will be closed by lnbits/lnbits#227

Hi,

I tried to send tip from the BLW wallet (@btcontract - author of the LNURL) but I got the error:

"requirement failed: Action domain mismatch"

From the Blixt wallet - there is everything OK.

I think your chain URLs from LNURL communication has different domains but the LNURL protocol requires to have the same domains (#6 point - "url domain must be the same as callback domain at step 3" in example comment)

Is it your the bug or the BLW?

It appears that StreamElements is currently working on providing a nice API. They have a WIP API reference which includes an endpoint to post tips, exactly what is needed to integrate this.

Would be great to have this!

This PR adds a guide on how to cut out all middlemen and run this in self-sovereign mode.
The Bitcoin way.
Closes #5

• [ ] How to set up your own node (Just link to Raspiblitz)
• [ ] How to change the funding source of LNbits

The original purpose of this project was to cut out all middlemen.
To this end, the only change that has to be made is the LNbits funding source.
Two short guides are required for this:

• [ ] How to set up your own node (Just link to Raspiblitz)
• [ ] How to change the funding source of LNbits

It should also be considered to potentially use Raspiblitz' LNbits

A lot of the setup required for Bitclouds.sh hosting can be automated.

• [ ] Purchasing a Bitclouds VPS instance
• [ ] Checking remaining balance
  • [ ] Low balance alerts
    • [ ] Discord webhook?
    • [ ] Telegram bot?
    • [ ] Email?
• [ ] Getting a top-up invoice
• [ ] Installing git and python3-venv
• [ ] Caddy
  • [ ] Adding the repo
  • [ ] Installing caddy
  • [ ] Creating the Caddyfile

This PR adds guides on how to actually host this publicly.
Closes #2

• [ ] Purchasing a Bitclouds VPS instance
• [ ] Checking remaining balance
  • [ ] Low balance alerts
    • [ ] Discord webhook?
    • [ ] Telegram bot?
    • [ ] Email?
• [ ] Getting a top-up invoice
• [ ] Installing git and python3-venv
• [ ] Caddy
  • [ ] Adding the repo
  • [ ] Installing caddy
  • [ ] Creating the Caddyfile

Currently, the system is fully functional, but does not yet include a guide on how to publicly deploy.

• [ ] Acquiring a domain
  • [ ] Full domain name
  • [ ] Duck DNS
• [ ] Guide on how to self-host
  • [ ] Setting up nginx
    • [ ] SSL cert via certbot
    • [ ] Enabling reverse-proxy
    • [ ] Opening the necessary port (443)
  • [ ] Setting up Cloudflare
    • [ ] Creating an account
    • [ ] Adding domain to Cloudflare
    • [ ] Hiding behind Cloudflare
    • [ ] Whitelisting Cloudflare IP range
• [ ] Guide on how to host via Bitclouds
  • [ ] Basic Bitclouds setup guide
  • [ ] Keeping Bitclouds instance up (keep funding it!)
  • [ ] Installing git, python3-venv, and Caddy
  • [ ] Creating a Caddyfile