daniele

I forgot the user's own profile! An "Edit" button replace Follows/Message, and the top-right dropdown actions are hidden. 

I'm pondering that it might give the idea that it doesn't make sense to pass the author's pubkey in creating an event, since it can be obtained at signing time;...

Another structural point is whether, in classes to interact directly with a specific event, e.g., Nostr::Reaction, it is preferable to pass data in a raw manner (as now, e.g., event...

> The way that you're starting here will mean that we'll have LOTS of potentially deeply namespaced modules or modules that have somewhat arbitrary names. For example, creating a new...

@anthony-robin > we should ensure users could create a manual event payload This is already possible to with the `Event` class. > An initializer with the private nsec/npub config The...

I just pushed some commits in master that update the API to the new structure. Now I'm going to think how to organize the classes and their relationship. /cc @anthony-robin...

Damn, we need a test suite. I will look at this asap.

Initializing more clients with the same signer should _not_ waste too many resource, but a better approach would actually be preferable. I'm evaluating how to procede.

> It can be set to mono layout (type 1), which includes a default left_side, or to duo layout (type 2), which features both left_side and right_side. Has responsiveness (e.g....

> but we came up with the current structure as it keeps the smart widgets follow specific guidelines when it comes to each element positioning and space taken This is...