CypherGraph: Difference between revisions

From Traxel Wiki
Jump to navigation Jump to search
Line 25: Line 25:


= GPT Thoughts on Reactions =
= GPT Thoughts on Reactions =
{| class="wikitable"
|+
!Catalog
!Format
!Dataset
!Classification
!Notes
|-
|Harvest
|JSON
|link_list
|create, delete
|
|-
|Harvest
|JSON
|archive_link_list
|create
|revise sync calls - do not use delete switch
|-
|Harvest
|JSON
|discussion
|create, (delete - only affects 2 most recent months)
|Restructure the storage, move date to year=2023/month=09
|-
|Pipeline
|Parquet
|raw/link_list
|create, delete (2x daily)
|
|-
|Pipeline
|Parquet
|dedupe/link_list
|create, delete (2x daily)
|
|-
|Pipeline
|Parquet
|compacted_raw/link_list
|create, delete (~weekly)
|
|}
== Positive Tags ==
== Positive Tags ==



Revision as of 16:01, 19 October 2023

Discussion Graph Traversal

The primary mission for this project is to make it possible for people to share information science actions. To make it easy for them to publicly describe, demonstrate, and encode mechanisms for curating information to resist disinformation and toxic infectious memes.

Graph traversal becomes a super-important element in those mechanisms.

Consider a message m, which is a node in a discussion graph D. There are various cases where I would want to incorporate or avoid that message.

Incorporate

  • Root Nodes m, a vector of all the nodes m that make up the first level of discussion. To be included they would need to satisfy an inclusion criteria.
    • The node itself is desirable.
    • A descendant node is sufficiently interesting that it merits inclusion of this node to anchor the branch.
  • Child Nodes c, a collection of nodes that have a parent, but are not root nodes.
    • Node Itself: The node itself is desirable.
    • Descendant Node: A descendant node is sufficiently interesting that it merits inclusion of this node to anchor the branch.
    • Ancestor Node: An ancestor node becomes worth of inclusion only with this added context.

Traversing:

If I start from a node m and want to decide whether to include its parent branch, under the "ancestor node" rule above, I might consider the following:

If node m is coded with the "supporting data" tag, and the parent node is mildly interesting but a citation is needed, m might justify inclusion of both nodes.

If node m is coded with the "counterpoint" tag, and the parent node is compelling but in need of challenge, m might justify the inclusion of both nodes (and perhaps suggests the inclusion of sibling and niece/nephew nodes).

GPT Thoughts on Reactions

Catalog Format Dataset Classification Notes
Harvest JSON link_list create, delete
Harvest JSON archive_link_list create revise sync calls - do not use delete switch
Harvest JSON discussion create, (delete - only affects 2 most recent months) Restructure the storage, move date to year=2023/month=09
Pipeline Parquet raw/link_list create, delete (2x daily)
Pipeline Parquet dedupe/link_list create, delete (2x daily)
Pipeline Parquet compacted_raw/link_list create, delete (~weekly)

Positive Tags

  1. Insightful: For comments that offer a fresh perspective or deep insight.
    1. light bulb, 1257, U+1F4A1, 💡
    2. 69, U+1F92F, 🤯, exploding head
  2. Cited Source: For comments that provide reputable sources to back their statements.
    1. graduation cap, 1188, U+1F393, 🎓
    2. 962, U+2693, ⚓, anchor
    3. 1536, U+2714, ✔, check mark
  3. Well-Structured: For arguments that are logically structured and easy to follow.
    1. 865, U+1F9F1, 🧱, brick
    2. 864, U+1F3D7, 🏗, building construction
  4. Open-Ended: For comments that invite further discussion or pose thought-provoking questions.
    1. 544, U+1F5E3, 🗣, speaking head
  5. Empathetic: Recognizing comments that show a deep understanding or empathy towards another viewpoint, even if they don't agree.
    1. 547, U+1FAC2, 🫂, people hugging
  6. Balanced View: For comments that consider multiple perspectives before drawing a conclusion.
    1. 1354, U+2696, ⚖, balance scale
  7. Fact-Based: Comments that stick strictly to factual information.
    1. 339, U+1F575, 🕵, detective
    2. 220, U+1F9E0, 🧠, brain
  8. Constructive Feedback: Positive suggestions or feedback on a particular idea or argument.
    1. 346, U+1F477, 👷, construction worker
    2. 961. U+1F6A7, 🚧, construction

Negative Tags

  1. Fallacy Used: For comments that employ logical fallacies in their arguments.
    1. 162, U+1F573, 🕳, hole
  2. Ad Hominem: For comments that attack a person's character instead of their argument.
    1. 345, U+1F977, 🥷, ninja
  3. Unsubstantiated Claim: Claims made without any credible source or evidence.
    1. 1123, U+1F52E, 🔮, crystal ball
  4. Over-Generalization: Making a broad statement without sufficient evidence.
  5. Anecdotal Evidence: Relying heavily on personal experiences instead of broader evidence.
    1. 581, U+1F984, 🦄, unicorn
  6. Emotionally Charged: Comments that seem to be driven more by emotion than reasoned analysis.
    1. 103, U+1F621, 😡, enraged face
  7. Off-Topic: Drifting from the main topic of discussion.
    1. 76, U+1F615, 😕, confused face
  8. Oversimplification: Analysis or solution that ignores complexity of the situation.
    1. 815, U+1F36C, 🍬, candy
  9. Shill:
    1. 72, U+1F978, 🥸, disguised face

Neutral/Informative Tags

  1. Seeking Clarification: When a user asks for more information or clarity on a point.
    1. 1520, U+2753, ❓, red question mark
  2. Background Info: Providing context or background information relevant to the discussion.
    1. 1267, U+1F4DA, 📚, books
  3. Experience-Based: Provides substantial and relevant real-world evidence.
    1. 255, U+1F9D3, 🧓, older person
  4. Hypothesis: Proposing a theory or idea that hasn't been substantiated yet but adds to the discussion.
    1. thought balloon, 167, U+1F4AD, 💭
    2. 35, U+1F914, 🤔, thinking face
  5. Bot: This looks like a bot account / post.
    1. 117, U+1F916, 🤖, robot

Considerations

  • Guidelines: Provide users with guidelines on how to use the tags appropriately. This can prevent misuse or over-tagging.
  • Feedback Loop: Allow users to see how their comments are tagged by others. This can be a learning tool for them to understand how they can improve their contribution to the discussions.
  • Avoid Gaming: Just like with upvotes/downvotes, there's a potential for users to "game" the system. Implementing a system where only a limited number of tags can be applied per user or per comment might help.