yar's revenge. the story so far exceeded the ability of the Atari 2600 it needed a comic book and record. https://youtu.be/weaboJeOyf4?si=BtG2fPPbXrG8hiTv

I know the guys at Alby are working on this issue. they suggested adding this to my PeerTube plugin's package.json for future funding.

"funding": { "type": "lightning", "url": "lightning:donkimberlin@getalby.com" },

A zap is a direct payment from one user to a lightning wallet. A boost is direct payment from one one user to a split block. A boost will have as many zaps as entries in the split. Zaps are to people, boosts are to a collective enterprise with an open contract for distributing zaps.

Zap's mostly use lnurl, Boosts mostly use keysend. Boosts have significantly more metadata about the content being boosted.

I use it for PeerTube RSS feeds in the Lightening plugin. it's not a perfect fit but works. The main issue I see with using it for SN is that its current implementation is keysend payment focussed with the type 'node', SN Lightening addresses were lnurl only last I checked , so you might need to extend it a bit by using a different type. Still better to work within an existing framework rather than starting from scratch.

What is it written in?

Login with lightning is on the roadmap for the plug-in.

Got it sorted out

even more curious, it does show up if i search for it when not logged in to this account, but the comment doesn't.

Curious, when not logged into my account I can't even see this post. guess spending SATs on boosting the post was negatively effective.