pull down to refresh
@ek
5,413,473 sats stacked
stacking since: #57444longest cowboy streak: 233 verified stacker.news contributornpub16x07c...2j2s96s89dekzyis
21 sats \ 0 replies \ @ek 30m \ on: Are big financial institutions more bullish than the plebs? bitcoin
My prediction for this year was $250k
I still think it makes sense
If you’re having bugs with their software, they should appreciate you reaching out
Edit: oh, you’re talking to Start9 and DATUM isn’t really their software, they are just including it so might not know everything about it
But they should at least tell you who you could talk to in that case
the lazy path would be to just use the hosted pwa and add your pubs base nprofile as the backing node.
Yeah that's what I'm doing currently but I assume that will pollute it with dev stuff if I ever want to use it seriously on mainnet
The docker image for pub isn't regularly maintained [...]
is this the reason for the error in the lnpub logs in #1214579?
The CLINK SDK has "manage" [...]
not sure why you're telling me this, is this related to my problem in #1214579?
I'm in the pleblab slack
oh, right, DM'ed you there
hey @Fabs, I see you, do I need to pull you in again?
hey @hodlpleb how is your wife doing?
Btw, any idea why the SDK would return
Invalid Amount
for sdk.Noffer
with amount_sats: 1
or any other number afaict? See code here.I also occasionally see
2025-09-09 17:50:49 >> ERROR GetUserOperationsRequest::root..latestIncomingInvoice: is not a number
in my lnpub logs but it seems unrelated to my error because it shows up randomly, not when I am requesting an invoice
@justin_shocknet is there a docker image for shockwallet?
Or something else that I can include in our local dev environment to create
noffer
and ndebit
from the lightning.pub nprofile
?it's from @justin_shocknet
I am implementing CLINK and I definitely like the distinction between
noffer
and ndebit
. It tells me immediately if what I have is for receiving (not very sensitive) or sending (extremely sensitive).Unfortunately, a NWC url does not. This leads to bad UX because we need to tell them that this NWC url that looks like any other NWC url is too permissive if they give us one for sending when we expect one for receiving.
In general, NWC urls are opaque where we want transparency (permissions), and transparent where being opaque might be better (exposing "implementation details" like pubkey, relay, secret etc. to the user).
This could be fixed if NWC urls also were encoded with a prefix like
noffer
or ndebit
.But since they can support both in one ... not sure if this actually makes sense
I was tryna say 'We pissed on the bouncer...', like, for real! *ucking wild! Ahahah
wait what, how do you piss on a bouncer? like from a roof? haha
my friend goes full throttle, trying to spin the car around – you know, like a donut
I wonder if that was his first attempt ever to spin the car around like that
the driver stayed behind to deal with getting the car towed
lol, the one who smacked his head right into the windshield. Does he now wear seatbelts?
phone was never found?
Really don't like their new name, Honeypot was so much better
But I assume their documentaries are still awesome! Will watch later hopefully, thanks
Makes sense!
I'm just still confused because the cause doesn't seem to match the amount of confusion. How this can happen (incomplete lock file) doesn't seem to match how often it seems to happen (the internet is full with people complaining about it).
Did all of them also had someone who forget to check in changes to package-lock.json? How else could it happen to have an incomplete lock file? Who modifies their package-lock.json manually or undoes the changes to it (
git checkout package-lock.json
) and then wonders why npm install
changes it again or ...?But maybe I'm contributing to the confusion around it right now haha
I wish the documentation was more clear when
npm install
changes package-lock.json. I don't see it mentioning what happens if the lock file is incomplete.Doesn't that imply that everyone who ran
npm install
and downloaded the malicious version were using an incomplete lock file?There's so much conflicting information regarding this, online and my own (fuzzy) experience
I also think how @k00b described it is how it should work (it would actually make sense), but I also know that
npm install
did modify package-lock.json in the past for me.But maybe that was indeed only when I was working with others and someone forgot to check in package-lock.json after they added it, which would then lead to an incomplete lock file for the next person that pulls.
At this point I guess I have to read the source code of npm to trust what's going on
That's exactly why I've been telling you that exchanges are a bad way to onboard people [...]
Okay, so you told us why we shouldn't use exchanges and some ideological stuff
But you didn't tell us why you used an exchange anyway
I was aware but there was no ticket. Now there is, now some contributor could also pick it up. Thanks!