Event JSON
{
"id": "f9af975ce04aa430807e8de8c940c3b7e1f64dda51c0f9e1e99fa74e78239a58",
"pubkey": "5112eee8668d8342659e08fab1513cadb2c875b0405aa6db458baedfd30b5006",
"created_at": 1709282042,
"kind": 1,
"tags": [
[
"p",
"3cdad0b7a807df385f54f64d6979e3d511f72c2472e22f8715679a55341bbadb",
"wss://relay.mostr.pub"
],
[
"p",
"a8f309f993f6d202dd41519ac072e14eea0c67c8c2628a1881fbd015a8947485",
"wss://relay.mostr.pub"
],
[
"e",
"28993f7544a1bdd88b5c9ad335798758745a7c2dbe3d358966f8ebc987a1a10f",
"wss://relay.mostr.pub",
"reply"
],
[
"emoji",
"heart_cyber",
"https://media.infosec.exchange/infosec.exchange/custom_emojis/images/000/028/822/original/5dd764ee4416c25e.png"
],
[
"proxy",
"https://infosec.exchange/users/m4iler/statuses/112019507961576013",
"activitypub"
]
],
"content": "nostr:npub18nddpdagql0nsh657exkj70r65glwtpywt3zlpc4v7d92dqmhtds93ax9z There will never be a Babelfish, because latency. What we were promised in tHGttG was instant interpretation, but you need at least a sentence to be able to translate properly. Even simultaneous interpretation gets a few seconds of lag. It may be doable that way, but your audio would be skewed a second behind the speaker.\n\nAlso, dubbing != dabbing, but the mental image of an AI dabbing on haters made my day :heart_cyber:",
"sig": "990b6a05a99d1850acf9e3a0b1c6cc25b7832e137c722bd4b2e45273036b6d3877224c16fc297f3501a0c3c6c93092675b0fbf6d4bb5145a7df573de3b78a2d8"
}
