Birdwatch Note
2024-07-21 23:25:02 UTC - NOT_MISLEADING
The community note currently being displayed states it’s not a null pointer issue, while continuing to describe a null pointer issue in detail, exactly as it was described in the OP. Why are so many people agreeing with something that contradicts itself?
Written by 23491AC0AF7334B9FA19F1E26973B13F7887B117D015A649E44622759B2E9966
Participant Details
Original Tweet
Tweet embedding is no longer reliably available, due to the platform's instability (in terms of both technology and policy). If the Tweet still exists, you can view it here: https://twitter.com/foo_bar/status/1814376668095754753
Please note, though, that you may need to have your own Twitter account to access that page. I am currently exploring options for archiving Tweet data in a post-API context.
All Information
- ID - 1815166122582512058
- noteId - 1815166122582512058
- participantId -
- noteAuthorParticipantId - 23491AC0AF7334B9FA19F1E26973B13F7887B117D015A649E44622759B2E9966 Participant Details
- createdAtMillis - 1721604302435
- tweetId - 1814376668095754753
- classification - NOT_MISLEADING
- believable -
- harmful -
- validationDifficulty -
- misleadingOther - 0
- misleadingFactualError - 0
- misleadingManipulatedMedia - 0
- misleadingOutdatedInformation - 0
- misleadingMissingImportantContext - 0
- misleadingUnverifiedClaimAsFact - 0
- misleadingSatire - 0
- notMisleadingOther - 0
- notMisleadingFactuallyCorrect - 1
- notMisleadingOutdatedButNotWhenWritten - 0
- notMisleadingClearlySatire - 0
- notMisleadingPersonalOpinion - 0
- trustworthySources - 0
- summary
- The community note currently being displayed states it’s not a null pointer issue, while continuing to describe a null pointer issue in detail, exactly as it was described in the OP. Why are so many people agreeing with something that contradicts itself?