bisq on Nostr:

{ "id": "51e6b509587f09d8f4825d8c80252a6da435c35a8094d680f33a35e1da3d7833", "pubkey": "8027a1877f39e603dafc63279e004b4ed9df861d18ce81d9c43c7d7135da8f65", "created_at": 1781614267, "kind": 1, "tags": [ [ "r", "wss://nostr.oxtr.dev/" ], [ "r", "wss://relay.primal.net/" ], [ "r", "wss://relay.nostr.info/" ], [ "r", "wss://nos.lol/" ], [ "r", "wss://relay.damus.io/" ], [ "r", "wss://nostr.wine/" ], [ "r", "wss://relay.mostr.pub/" ], [ "r", "wss://nostr.land/" ], [ "r", "wss://offchain.pub/" ], [ "r", "wss://eden.nostr.land/" ], [ "imeta", "url https://blossom.primal.net/71ae7f8be9a816d4a35cc2d6ec1029283524e1bbfb17a2772a60421130788ac5.png", "m image/png", "dim 1416x1247", "service nip96" ], [ "client", "Primal Web" ] ], "content": "https://bisq.network/blog/where-bisq-stands-after-security-incident/ https://blossom.primal.net/71ae7f8be9a816d4a35cc2d6ec1029283524e1bbfb17a2772a60421130788ac5.png ", "sig": "f97a02cb778488662d9e6916f03f8781da1a49953b4e47d710995d298e2325e6e651dcdbbbcbc388c7118b7ac65aa9dba5a6ece52f7e5b50f137290266ff2cf1" }