I'll be happy when I can close this PR. It is now in app review π¬
Get nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m to setup a lightning address for you! π€
π

It's not necessary safe if the app is on the App Store. Apple don't check if the app is misusing the nsec. You are assuming trust of the app, the best way to check it is safe is if the app is open source so it can be verified.
I see. I just wonder if you truly run the whole "thing" (Websocket + Strom + LN node (presumably LDK/Greenlight/BreezSDK)
Strom is Typescript (I guess), and can run in AWS Serverless
https://aws.amazon.com/de/blogs/compute/building-typescript-projects-with-aws-sam-cli/
Websocket can natively be run via API Gateways
And I guess(!) also the Lightning part of the code can be run by one of the AWS services. Presumably also AWS Serverless, if just using Greenlight/BreezSDK (bit i might be wrong)
That would mean you can deploy the whole Strom-as-a-Service stack serverless, and when a new CP/CP operator comes along, you presumably just edit some config somewhere to register it, and provision its own Websocket
I want to offer different lightning backends for Strom in general: LND (for umbrel or voltage), LDK, CLN, LNbits, Breez/Greenlight. Kinda plug and play. For Strom-as-a-Service different backends options would require different fee models, hosted LND/CLN nodes being the most expensive.
But Strom itself is being written in Go, which I think also works with AWS serverless. It could work, though I plan to integrate nostr also, which would mean it's a websocket client listening for events...
Have to think about it more.
I'm just thinking about if I could offer a hostable version of Strom. Like Strom-as-a-service π Strom + lightning node. Its would need incoming websockets for the charge points to connect to.
I'm probably thinking waaay too far ahead π
This gives me hope, but I need to test it
Normally you'd deploy an AWS API Gateway service which exposes a websocket for external use. And you have you service (Lambda, ECS etc) behind that API Gateway.
https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-websocket-api-overview.html
So there is no way of using the ALB, it has to go through an API gateway?
Normally you'd deploy an AWS API Gateway service which exposes a websocket for external use. And you have you service (Lambda, ECS etc) behind that API Gateway.
https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-websocket-api-overview.html
Nice, thanks!
Can anyone definitively tell me if websockets work through AWS ECS or not?
Do any of the #nostr clients with built in image uploaders offer to strip out EXIF location data?
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
GM #coffeechain
Weekends are for stepping back, playing with your kids and thinking of #nostr π

The nostr:npub1us9uc0sjjg0vyvh7vefgu2a96hx5up5gujl6pqays65hlk4de6hsnwq4g0 announcement bot was broken today. It's been fixed, sorry! Announcements are back to normal.
For some reason it's blocked for me. Don't remember mashing a Block button

Wen cash beer tap?
Wen zap beer tap?
Your LN address is not resolving #[1]

