Avatar
ThyLobster
c65d0b75a84bbfc046b9cedc0cf098a0816b83ad24004ec8bb9314baa178758c
Coder by day. Libertarian (it seems).

As things get increasingly harder in the UK, so do the On/Off ramps.

What are our options beyond the obvious?

No, Neo. Work is a word. What matters is the connection the word implies. 😉

Thanks!

No, I mean, I get the response :) What I don't get is, whats wrong with the payload that looks like this?

```

const payload = {

"ids": null,

"authors":null,

"kinds": [0],

"#e": null,

"#p": null,

"#a": null,

"since": null,

"until": null,

"limit": 10

}

```

Are you saying the payload needs to be

```

[

'REQ',

"npub....",

{}

]

```?

Sorry to bother you.

Sorry, dont want to insist, it's just that I think that for a few weeks now, some people can't see my messages. I think I may have the wrong relays or something, but something is not quite right and I dont know if you can see my note at all. Can you nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft ?

I'm intrigued. I need to learn more about this.

But can you please explain a little more on how does trading multiple times with the same person, even if this person is on your social circle, reduce the risk of banks assuming you are incurring into fraud? The bank doesn't know they are your friends. If I send them 3 payments, that can still be illicit. I have no idea how the banks make that decisions, do you?

Genuine question - Do you know or have an idea of what their algoritms are?

I'm looking at vexl, but I dont think it solves the issue of on/off ramps.

The problem remains on how to make payments in fiat that dont raise red flags or cause the accounts to be frozen.

I reckon the solution IS to trust a third-party that disguises as a legit element.

Replying to Avatar ThyLobster

Sorry nostr:npub1ng0gxxuxwldpt8n98mgsthnxaahcd5t45343gsymmpwfmaz4m3gqhqkpmf, but can you give me a hand?

I'm not a JS developer by any means but I would like to understand how nostr works from a fundamental level. Literally from the pure ws connection side.

I wrote this simple client and I got this response and I dont know what i'm doing wrong.

I have tried using your higher-level ndk, but that would somewhat abstract away the very thing I would like to understand.

Sorry nostr:npub1ng0gxxuxwldpt8n98mgsthnxaahcd5t45343gsymmpwfmaz4m3gqhqkpmf, but can you give me a hand?

I'm not a JS developer by any means but I would like to understand how nostr works from a fundamental level. Literally from the pure ws connection side.

I wrote this simple client and I got this response and I dont know what i'm doing wrong.

I sometimes take a little time but eventually I get there :) Thanks for showing me this.

But I wonder if I can achieve the same thing by printing a QR code on paper, laminating it and storing it inside a fire and waterproof container?

Its probably cheaper....

I'm struggling to buy bitcoin. I would like to buy but I know the banks will freeze my account if I make a payment to anyone of for more than 1000 or 2000.

I'm not sure why did we got convinced that the on/off ramps would not be shutdown.

Bisq is useful but the ramps will be completely shut very soon.

I'm sorry. In in London. But I would love to see what you mean. The descriptor is like 4 lines long and not really human readable, so the best way to store it should be a digital file. Are you saying we should write it down in steel?

Can you post an photo of what seedhammer looks like?

So I have done my "experiment" and you are right, I need to store the descriptor.

So I guess that my only option would be a digital key for a multisig, but it basically breaks the whole point of the multisig security and makes it a single point of failure :(

I was just so hoping this could be a simple solution, but its not :(

So what was the solution you came up with for the descriptor?

"I don't remember asking you a gawd damn thang"

"Oh, I'm sorry. Did I break your concentration?. Oh you were finished? Well allow me to retort..."

"WHAT DOES MARCELLUS WALLACE LOOK LIKE?"