getAlby / getAlby/hub

Plugins (Ideas tracking issue)

Open
#402 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
280
Forks
132
Avg merge
5d 18h
Merged PRs (30d)
8

Description

Plugins as an idea sounds cool, but what would it actually mean in the context of Alby Hub? list your ideas here!

Currently we have internal apps which are the simplest implementation of plugins, but require user interaction.

The benefit of proper plugins is they can execute without user interaction. They could execute on certain conditions (such as a payment received) or on a schedule (like cron jobs)

What are we trying to solve?
- Easily run custom apps without requiring a separate web server? (online 24/7)
- ?

What would the plugins be able to access / modify in Alby Hub?
- a NWC connection?
- the internal hub API (e.g. channel management, apps, ...)
- custom frontend pages?
- some isolated DB data?

Plugin ideas:
- ~~Uncle Jim (generate subaccounts)~~
- ZapSplitter (receive a payment and forward it to N addresses)
- Subscriptions?
- Cashu Mint
- ?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.