Record🤔

uri:

"at://did:plc:v2cwzcqbfb7qvkspmpege6y7/app.bsky.feed.post/3lcgdxkqags2h"

cid:

"bafyreicnarjsbouhxxv4onsdiu7padcyklb6ihvrafqjs4v6tyoe4r42jq"

value:

text:

"Believe @pfrazee.com has said, re this bit, that if NYT wants to unverify, they just remove the relevant bit from their DNS and then the account listing joereporter.nyt would show “invalid handle” until the account holder changes handle to another domain in settings"

$type:

"app.bsky.feed.post"

embed:

$type:

"app.bsky.embed.images"

images:

• alt:

  "Screenshot of text:
  
  But this new method does bring back some of the old debates over who "owns" a reporter's social media account. For instance: Bluesky's verification only requires a one-time check of DNS records. But if a @joereporter.nytimes.com gets fired in six months, I doubt the Times would be thrilled for him to keep "nytimes" in his social media identity forever. It's not clear how, exactly, a publisher would go about "unverifying" an ex-employee without having to create a new dummy account and verify it with the old identity. But that's an edge case, and it's a potential problem for publishers more than for journalists."

  image:

  

  View blob content

  $type:

  "blob"

  ref:

  $link:

  bafkreihn6ndonnmeqprnxor4z64srl5d2ykj7pcua3zlxlaujcd3oea2hu

  mimeType:

  "image/jpeg"

  size:

  550367

  aspectRatio:

  width:

  1320

  height:

  1346

langs:

• "en"

reply:

root:

cid:

"bafyreib4qbafcqdphbbkbkrmmn7vr6qgqooop5lgup7bad2jrhgtqci34e"

uri:

"at://did:plc:ybo4pxheeu5wcdas3ahvmogu/app.bsky.feed.post/3lcgdanrmlk26"

parent:

cid:

"bafyreib4qbafcqdphbbkbkrmmn7vr6qgqooop5lgup7bad2jrhgtqci34e"

uri:

"at://did:plc:ybo4pxheeu5wcdas3ahvmogu/app.bsky.feed.post/3lcgdanrmlk26"

facets:

• $type:

  "app.bsky.richtext.facet"

  index:

  byteEnd:

  20

  byteStart:

  8

  features:

  • did:

    "did:plc:ragtjsm2j2vknwkz3zp4oxrd"

    $type:

    "app.bsky.richtext.facet#mention"

createdAt:

"2024-12-03T19:14:56.494Z"