Event JSON
{
"id": "c152e8b155bb41fa1479b2813c48dea6bb8664c652068c7144f001d283861d07",
"pubkey": "ff6da577d3997d02bb34c1568266ca9c5922be57b20d48f5cd2f2eabec394b9a",
"created_at": 1717232764,
"kind": 1,
"tags": [
[
"p",
"88f809c5cbf12367420d4b5c942ca9e10e1aa3355a620e1907bb993f9258a79c",
"wss://relay.mostr.pub"
],
[
"p",
"390c934899155ad1361f83c6d1cbb0cfd2a9f1d85b0525fbf359ca9725e397e7",
"wss://relay.mostr.pub"
],
[
"e",
"e73c55d6c3dbac99be3aa2f51a761a8bb9a742162582d574940269ad99ec86bd",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://chaos.social/users/GCHQNET/statuses/112540566439636519",
"activitypub"
]
],
"content": "nostr:npub13ruqn3wt7y3kwssdfdwfgt9fuy8p4ge4tf3quxg8hwvnlyjc57wq0t67kn Yeah it’s a detection issue in the underlying badge firmware. Possibly a hardware issue, the badge team are still investigating it I think.",
"sig": "30a682b706b97085dbc1d5004ddd07c4190176c1c39157ba63157a9550ad969117db434466eee46c526a2db552a679be1a5df43508b54e78d789b60d051b0055"
}
