kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it does

😂 WEBSOCK

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually fsjlfsfjslfsjlfds


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it does

😂 WEBSOCK

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually fsjlfsfjslfsj


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it does

😂 WEBSOCK

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually fsjlfsfjslfsjl


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it does

😂 WEBSOCK

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually fsjlfsfjslf


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it does

😂 WEBSOCK

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually fsjlfsfjs


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it does

😂 WEBSOCK

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually fsjlfsfjsl


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it does

😂 WEBSOCK

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually fsjl


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it does

😂 WEBSOCK

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually fsjlfs


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it does

😂 WEBSOCK

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually fsjlf


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it does

😂 WEBSOCK

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually fsj


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it does

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it do

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as i

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as it

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as wel

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as well as

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works as

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this works

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this wo

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this work

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this wor

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away tha

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away th

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that this

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown away that th

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown a

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown awa

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so bloc

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blo

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so blown

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so b

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so bl

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm so

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay super simple.

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I'm

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stuck there and now it's in

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay super simple.

yeah, but the other thing is that, for example, for create_account you might want to pass arbitrary data, which the bunker might or might not support, like "image" or "avatar" or "name" or something; I don't even like "email" I put it there as a POC and it just stu

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay super simple.

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay super

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay super simpl

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay super sim

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay sup

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay super simp

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay super simple

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay super si

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay s

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to sta

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to s

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to stay su

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure to

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structure

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data struct

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data structu

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data struc

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data str

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data stru

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data strut

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the data strutu

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force th

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the dat

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they force the da

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they fo

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they for

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that they are

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that the

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things i

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is th

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is tha

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good things is that th

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good thi

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good th

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only go

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good thing

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only goo

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the only good thin

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the onl

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the o

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

th

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

the

Yeah, I guess

but for this stuff they're really annoying; for tags they're fine and I like them better actually


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

Yeah, I guess

but for this stuff they're really annoying; for tags they


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure that objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure tha objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure th objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am sure objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am s objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I am su objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I  objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them?

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr? FJ likes them

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr? FJ likes th

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr? FJ likes the

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr? FJ li

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr? FJ lik

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr? FJ like

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr? FJ likes

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr? FH

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr? F

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr? FJ

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around nostr?

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays around no

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays arou

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays ar

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays aroun

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arr

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional arrays

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional array

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positionall

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional ar

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positional

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many position

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many pos

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many po

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positiona

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many p

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many posi

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so many positio

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so man

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are the

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so ma

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are there so

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are th

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, wh

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why are

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier, why ar

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easi

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit eas

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit ea

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bit easier,

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a bi

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are a b

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are bit

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are bi

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects are b

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess ob

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objects

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess objec

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess obj

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess o

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I gues

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I gu

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah I guess

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. y

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool. yeah

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok co

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok cool

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok coo

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

ok

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updating you still typing?

no


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updating you still typing?

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updating you still typ

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updating you still typi

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updating you still typing

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updating you still t

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updating you still

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updating you still y

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updating you stil

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updating you

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updating you sti

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updat

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped updating

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped upda

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stoppe

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stopped up

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it stop

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it sto

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it s

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

it

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

i

yeah

that way we get rid o

👍


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@bar.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo@ba
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "fooa
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "foo
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "fo
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email: "
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email:
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  email
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  ema
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  e
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  secret
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  se
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  secre
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com",
  sec
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "examp
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "exampl
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example.com
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "example
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "ex
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "e
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain:
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain: "
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  domain"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  doma
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  dom
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",
  do
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal",

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal"
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "bal
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "ba
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "b
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username: "
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    usernam
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    user
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    usern
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    u
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({
    username:
  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?

yeah

that way we get rid o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array?


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional arra


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional array


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the position


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positi


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the posi


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positional ar


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the positiona


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the p


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the pos


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instead of the


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there instea


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there ins


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there inste


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object there


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an objec


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object the


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object th


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an object ther


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an obj


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an ob


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use a


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use an o


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to use


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're going to us


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're go


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you'


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you're


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok, you'r


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

O


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

OIjk


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

Ok


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

OI


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂

OIj


kind: `create_account`
params:

{
 "kind": <create-account>
  content: nip44_encrypt({

  })
}

I love it!  😂


kind: `create_account`

I love it


kind: `create_account`

I love


kind: `create_account`

I l


kind: `create_account`

I love it!


kind: `create_account`

I lo


kind: `create_account`


kind: `create_account`

I


Definitely all fixable, but I'd take some time to really think through the user journey here. It's a completely new paradigm so it's going to be hard to grok.


I'm decidedly short on humans reflecting on their entrenched positions and admitting their errors in public. Kenneth is simply the exception that proves the rule.

😆


I'm floored that we've already managed to raise over 1M sats for Bitcoin Chiavenna on nostr:npub1kmwdmhuxvafg05dyap3qmy42jpwztrv9p0uvey3a8803ahlwtmnsnhxqk9. 🤩 Let's keep this momentum going!

A huge thank you to everyone who has contributed already and, for those that haven't yet, there are still limited edition t-shirts available. 😉

https://geyser.fund/project/bitcoinchiavenna

nostr:note13a6mqks0r87fllxvz5cw538envchqs66v9g5msavw8f29ychwquspj3n59


Ok – I've watched the demo and I played with nsec.app. So nsec.app isn't talking to any backend unless you explicitly tell it to do the cloud sync?

I created an account there and then was able (after a few false starts) to get signed into nostrudel using that key.

When I tried to use the same nip-05 on my phone, it seemed like it was connecting but never finished the connection and I couldn't log in. So I'm not sure, do I need to logged into nsec.app on my phone too? And in the same browser on my phone?

I also didn't set a password when I created the nsec (wasn't asked) but then when I go to sign into nsec.app on my phone, i am asked for a password so I'm not sure what to do there.

I think the idea sounds like a cool one. E.g. not having a custodial nsecbunker could be a good thing, but the UX here is extremely confusing at the moment.


😂🤣🤣 the 80IQ version works surprisingly well!!

Let me never doubt the speed of relays and websockets again.


I have briefly had a look but I'm not sure I totally get it. Is it remote signing (bunker style) or is it an extension. Storing your keys in the browser makes it sounds like an extension....


I've just bumped Nostr Ignition to v0.0.6.

Big thanks to nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 who pulled (a version of) my code out into nostr-tools for me and refactored the library.

Release notes here 👇
https://github.com/erskingardner/nostr-ignition/releases/tag/v0.0.6


😭

nostr:note1xm6zc4a7x5g8ggkzv5pv5flwzm9qwkkfhgw6rwxhaw4lwdv8tqyqr5llr6


💯 Coming in early to hang with SovEng so definitely!


I think they might have one while I’m away in Madeira but we’re planning one a month or so


It’s actually pretty cheap by EU standards. Especially if you’re looking at larger cities. You can go out for a very good, multi-course meal with drinks and spend less than 30 a person.


💯 Spot on.


Oh yeah – definitely a roaring success.


See you here soon! 😄


This note was brought to you by this article.

https://www.rollingstone.com/culture/culture-features/taylor-swift-ai-generated-nudes-swifties-1234954487/


I find the the idea that you can stop something you don't like by simply making it illegal so amusing. I mean, it's clearly worked really well for the war on drugs and the war on terror, right?!

Perhaps instead of legislating and then spending billions on enforcement (and/or wars), we should spend that time and money on educating people and equipping them with the mindset, tools, and social skills to manage what they see and do on the internet and in the real world in a productive way.

Meh, you're right. Let's just keep yelling at each other about what we DON'T want instead of working together to get more of what we DO want in the world.


It is! :)


Cavolo! Sembra molto bello lì.


Thanks!


Let me know when!


nice!!! can't wait to show you around.


Thank you! 🙌


Make it happen!!


Thanks man! 🙏


Do it!! 🏔🏔🍷🍷🍝🍝


Thanks 🙏


They have it on desktop. Just not quite mobile yet.


About 90 minutes away. Would be closer except for all those damn mountains in the way 😂


🤙 thanks!!


Do it!!


Thank you!! 🙏


🙌 thanks Vanessa!


Thanks man 🤙


Thanks! 🙏


Probably late Oct, the weekend before Plan B in Lugano (which is just over an hour away from us).


Will do!


Can wait to show you around! 🤙


As a child of the 80s, I approve of this comparison. 😅


Done! 🤙


Done! I'll be adding more businesses in the next few weeks. 😉


Thank you!


🫂 Thanks brother! Can't wait to have you over!


Haven't pulled off much yet! Still just getting started. 😉


📣 Announcement time! 📣

As you might have guessed (from the photos I keep posting, mostly), I really love the place where I'm fortunate enough to live. It's a small town in northern Italy. We're surrounded by 3000m peaks, Lake Como is a short drive away, and the people are warm, welcoming, and hard-working.

My wife and I moved here 14 years ago with no more expectation than trying to figure out how we could live in the alps to climb and ski right outside our backdoor. Over those 14 years, Valchiavenna has become our home.

For a long time, I've been plotting and scheming about how I could give more back to this community that has given me so much and over the last few months, with the help of many local friends, all the pieces have started to come together.

Bitcoin Chiavenna is aimed at building a stronger Chiavenna using Bitcoin but; more broadly, it's a project focused on exploring how small, often marginalized, rural communities can benefit from adopting Bitcoin.

Chiavenna is the perfect petri dish for experimentation. We have local hydro power generation (run by a local coop). We are a stone's throw from Switzerland, which brings both tourism and shows local government how sane (and very minimal) regulation of digital assets can be beneficial. And, unlike many small towns in Italy, we have a large population of young entrepreneurs who haven't bailed for the big city and have started dozens of local businesses.

My hope is that our education and our learnings will be beneficial for other towns across Europe and North America. Many of whom, facing the death of their traditional industries, are having to find new ways to thrive, and do so without becoming wholly dependent on the central government for handouts.

I grew up in a small town. I live in a small town. I want to see tens of thousands of vibrant, wealthy, interesting, weird small towns across the planet. And I want them all to run on Bitcoin.

If you're with me, I'd love your support. We've just launched a Geyser project to raise funds for the first phase of several projects. We've got some cool rewards listed there, with more coming in the future.

And if anyone is coming through the area, let me know. I'd be happy to show you around and help you leave a few sats behind at local businesses!

Onwards and upwards! 🏔🚀

https://geyser.fund/project/bitcoinchiavenna


I’ll give you 2 weeks. No more. 😅


This is maybe the coolest thing I’ve heard in a long while.


Awarded to supporters of Bitcoin Chiavenna


GM Nostr! 🌞

I have a big announcement queued up for today. 😉


It’s iOS.


iOS widget called Bitcoin Widgets.


nostr:npub1clk6vc9xhjp8q5cws262wuf2eh4zuvwupft03hy4ttqqnm7e0jrq3upup9 nailed it. nostr:npub12hcytyr8fumy3axde8wgeced523gyp6v6zczqktwuqeaztfc2xzsz3rdp4 ✅