Skip to content

Develop and implement a standard for web client extendability #267

Open
@Giszmo

Description

@Giszmo

Recently window.noStrudel was added but it's "noStrudel" and opt-in and might expose dangerous stuff. I would love to see an open standard that would by default expose data that is public anyway to plugin devs. For example:

window.nostr.events = [
  {
    "id": id,
    "pubkey": pubkey,
    "kind": 1,
    ...,
    "loaded": true,
    "onScreen": false,
    "link": "https://next.nostrudel.ninja/#/n/nevent1qvzqqqqqqypzqp4hsxwh78rl23eprqnxa4au4pu9mn4wp83kagay4an9cmgasvnuqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqfdu9shjd8pagurmf5gcaku6zm4wcxxkdfxy7utdmwh4suw7rvn2qvc4zkr",
    "divId": "zk-asdflkj321"
  },
  ...
]

This would allow to easily process these events and link and decorate them in the client.

I would argue, such an object should also contain decrypted messages and everything else a plugin could grab from the screen anyway.

The goal is that developing a plugin for one client works for other clients, too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions