Event JSON
{
"id": "de955640171c191f7adc5652f7908bc697f07667469feeed1ec3e4354df6d55e",
"pubkey": "1bab79497d21d691bc1a610c8efc29348ec84016e274f7bbd8132d3ea70795f5",
"created_at": 1704408550,
"kind": 1,
"tags": [
[
"p",
"7f253317431495bf5be5202e40fc1737134a67f58a1a071cc60efc16da21be90",
"wss://relay.mostr.pub"
],
[
"p",
"31cde7286bc8d04c80531a9c5b42b9a00a705ac122f9c790ba629270554b9565",
"wss://relay.mostr.pub"
],
[
"e",
"c6df933ad18214c2333a20ed43e48ce61619c7e512e673a46051b202bda6cb16",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://nondeterministic.computer/users/martin/statuses/111700118784310847",
"activitypub"
]
],
"content": "nostr:npub10ujnx96rzj2m7kl9yqhyplqhxuf55el43gdqw8xxpm7pdk3ph6gqyqsth0 Thanks! We’ve not prioritised interop with ActivityPub since it would be difficult to provide a good user experience – eg. it’s not obvious how to ensure that users see the same reply threads across both Bluesky and ActivityPub, since the underlying protocols are very different. Maybe it can be done, but right now we think our time is better spent proving out the Bluesky model.",
"sig": "c40d7b2888c210532e9ac261bd654d889b9cd1f688083c85b623ce8e8a1a27eca4222d876a0609b224e812e0d235e2e6b16558ae62549d9dcdcf9aba9b7962f0"
}
