Jacob Davis

@evgenyneu Thanks for the quick reply! You have a great library here. I'll take a look at the other libraries or may just fork this one and the support I...

@ricmoo Just curious, but did you ever release your project for secp256k1 curve? My current requirements are expected to handle secp256k1 and secp256r1 curves. [](https://github.com/kmackay/micro-ecc)

By the way for anyone else looking, I actually pulled in the mirco-ecc c library and am using in swift. Its working great so far :) https://github.com/kmackay/micro-ecc

Similar here. Cannot get any of the examples to run. Im on Fedora 38 with latest v and ui ``` ❯ ../v/v -cg examples/users.v /tmp/v_1000/users.10102165615358526159.tmp.c:44833: warning: assignment discards qualifiers from...

Design looks great! However, Im more of a fan of using standard platform design especially in an open-sourced project as it makes it easier to maintain. That said, it's a...

> if we're going this route, then IMO this array should maybe be better in kind-0 as `content.relays:[]`. having what relays you post to is pretty integral part of identity,...

> I guess we can all agree on using kind 0 then. > > I like having relays as tags. I think it unlocks some nice features like being able...

> I only found one profile with "relay" in metadata, however this kind 0 is really nonstandard, has a content key within the content field. note1q7w36puvtxukgflu2kvugyral4tvk938lj9mmq7djvxugftazdlq2sf65g > > @ismyhc are...

> > I just found my conversation with @jb55 and he puts them in kind3 > > That's what most clients are doing, it's a crappy legacy from branle. >...

I guess I could be missing something, but the content is AES encrypted with shared secret of sender/receiver. So there are only 2 keys that can read the content. Sender,...