Avatar
jb55
32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245
I made damus, npubs, and zaps ⚡️ Independent bitcoin core and lightning dev.

Downside is that clients have to know a about every type and every future type for it to render properly. Think of a world where there are hundreds of different app-specific kinds. Fallbacks are super important if we are going to start doing nip27 embeds everywhere.

This is my brain immediately after waking. Its part of the boot process or something. Some kind of power-on-self-test

90% convinced accounting should be a programming role. Accumulating data from multiple sources into your chart of accounts almost always requires code of some kind. I’m guessing this is never done properly and accounts are just inaccurate because of this.

With ledger-cli + sql and parsing zap data I can have very accurate balance sheet of zap donations, total zaps broken down by posts, merch sales, even cln routing fees earned, sats lost due to channel close fees, etc. couldn’t have done it without code.

also gm nostr

yeah its a known bug where extra data is only fetched on the post that you first click into on a thread. There are lots of thread issues which i hope to fix soon.

I still haven’t seen this bug… resuming the app should ping and reconnect :/

I haven’t released it.

I don’t know I’ve never run an LND node

Definitely thinking about it! I might add a nostr transport instead of commando so that it will work through firewalls.

All donations and merch sales go directly through my lightning node. a #CLN node makes it easy to run a business on bitcoin:

1. https://jb55.com/btcmerchant payment links ( https://damus.io/merch ) for serverless CLN PoS (I used this in miami for all merch sales).

2. CLN sql queries to build reports from LN invoices, feeding them into https://ledger-cli.org for accounting.

3. Completely self sovereign with no counterparty risk.

Catch up fiat businesses 💅

How is it so far? Trying to avoid so I don’t get sucked in.

I havent listened to a word from these people since years ago. What’s their latest grift?

Ah you can click the number to change it. It could be more obvious

#damus booth was like #plebchain IRL the entire conference. What an incredible experience, nice meeting y’all!

I learned a lot! My biggest takeaway:

We need better onboarding in-app. 90% of people I talked to who created an account never set up a lightning address, never experience getting paid for posts, never follow people, etc. will fix this by including a “finish setting up damus” with red notification dot breadcrumbs for pfps, wallet attach, first post, follow, etc.

Learning this on the ground was invaluable. Overall people just seemed excited for the future of nostr. Talking to #plebchain irl was a nice contrast for the otherwise influensoor-heavy flavour of the conference. #nostr is starting to feel like a serious pleb renaissance: Just real people stacking sats and shitposting, no influencer algos, drama or popularity contests. Fucking grateful to be a part of this. Let’s keep growing nostr to show how powerful this community really is.

Back to building!

Yeah just a long way home. 24hr no sleep. Home now, passing out 😴

busy conferencing. No algos to fill the void. back to scheduled programming soon I’m sure.

You can’t do seamless client side zap splits without it. You would have to open N invoices externally and pay each one. Noone would do this.

Not sure it anyone has noticed the orange pending zap indicator yet. This means it got a payment confirmation from the NWC relay (payment was sent) but it hasn’t seen a zap yet. This can happen with slow or buggy zappers. But rest assured the payment was sent, damus tracks this in the UI so you don’t accidentally zap again.

Yellow means it didn’t receive a payment confirmation yet (nwc relay connectivity issue?)

The zap will disappear when NWC payment fails, which may happen if you ran out of sats or liquidity issues.

The indicator will go away when it sees a zap.

Sending rusty clightning patches over signal. Very cypherpunk. Who needs github.

Fiat revenue is dirty. Damus will avoid at all costs.

most non-nostr apps shouldn’t need to care about NWC, I don’t really see a problem. If another app needs NWC like functionality then they should propose a spec for their use case. nostr just happens to be popular atm and it makes sense to use relays for rpc in this context.

nostr:note1ewpmpv4946zqk2gz407g95xm8pdg0rzuzwt8endjh848nek4w87q0vuudc

An average of 2 cents collected from 1200 zaps in ~6 hours totalling $30. The legacy system has no chance of pulling something like this off nostr:note1h80ajcxn75kr6xqksrqyx5nqh6yw7nncn7el5ntdwmd5vmc4hvcqnkr65g

This by #[3]​ seemed interesting nostr:note1r4ts6nszuvf3j40wd53g3qddhs47svhayet4crehtcllvg0d7gqsr3sry4

I think theres a small bug where it will fail to zap the first time you attach your wallet. I hear that if you force restart your app it should fix itself. Still working out the quirks, this is the first alpha release.

Not correct… that sounds like a bug

They are also blurred so the OP must be referring to another client

Replying to Avatar Sjors Provoost

nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk this video doesn't play on my self hosted instance. Though it very briefly flashes a preview when the page loads.

Weird I did encode it for maximum compatibility 🤔 maybe I screwed up

Should have made them backwards compatible imo. Didn’t need to hardfork like this. Could have just referenced urls in tags.

Go to the universe tab (magnifying glass icon) and paste the npub in search

because it’s easier for spammers to PoW than normal users

Yup its there. It will be in the next version

"have you been zapping girls on nostr again"

I'm up late pondering what kinds of domestic dilemmas I have unleashed.