knowledge crowdsourcing

[synctext]

Idea brainstorming issue

With Gigachannels and our contributing crowdsourcing community we're taking the first step of evolving beyond Bittorrent and Tor. We want to evolve further in coming decade and make "hive mind" fantasies a scientific reality. (see #4475)

TUDelft faculty member Prof. @ChristophLo has published several works on scientific crowdsourcing, Large Scale Cooperation Scenarios – Crowdsourcing and its Societal Implications (2016). He is willing to help us. Other publications on this topic are:

• KATARA: A Data Cleaning System Powered by Knowledge Bases and Crowdsourcing
• DOCS: a domain-aware crowdsourcing system using knowledge bases

The Tribler platforms requires a trust function and anti-spam measures to facilitate further crowdsourcing. Most of the effort will be hard-core engineering and numerous improvement cycles. Knowledge crowdsourcing requires intense platform engineering, not a dramatic enabling scientific breakthrough. It is essential that the crowsourcing community grows steadily and instantly starts using new features. We envision two primary use-cases: science and entertainment. Using the same platform any artist or scientist should be able to upload and share their creativity with the world. We aim that our generic editing mechanism support both music metadata and musical score (crowdsourcing cultural heritage) as well as scientific articles and citation culture.

Possible evolution steps:

• links Every channel owner can provide a portion of a page of text about the channel with inclusion of magnet links.
• markup and pictures Pictures are somehow supported in the "channel page" and markdown editor gets integrated into Tribler, like this one
  
• science channels Scientific articles in .pdf format get explicit channels support with title and author metadata. Support for cloning, commenting and enhancing scientific publications. For instance, a living survey channel with the state-of-the-art in a scientific field and markdown-based overview.
• scientific reputations Somehow we show the karma and citations of scientific authors and their work.
• Usage of reputations and richer editing practices, as shown on Wikipedia.

[synctext]

Focus: alternative scientific publication method

• IdeaDAO
• open market of ideas
• strong IDs
  • trustchain
  • Github
  • BTC
• secure code contributions by strangers
• secure online voting
• Both core platforms PRs and plugin contributions.

[synctext]

Markdown embedding - Web3 exploration

Tribler is torrent download client, it is completely "web-free". We do not use HTTP or Javascript technology (well, except for our own integrated webserver to expose the Tribler with a REST API). Explore for 2 weeks how easy it is to embed rich text browsing, hypertext and picture embedding into Tribler. Focus is the GUI part and library linkage. Download engine is out of scope, just bundle the content locally as a shortcut. This is a exploratory step for broader "knowledge crowdsourcing" in the 2022 or 2021 timeframe. Possibly we will put a master student on this topic.

Desired outcome, Markdown viewer embedded into Tribler to view markdown, images and can follow 1 hard-coded link:

• Goal: explore how difficult or easy it will be to take Tribler beyond torrents
  • establish the difficulty of markdown integration
  • suitable for usage of channels descriptions in 7.7 or beyond release
  • complete re-use of our existing QT interface (years of work to debug)
  • streaming, credit mining, and tokens took us years and we never got it operational
• Time boxed effort: strict 2 weeks exploratory prototype
• Library code:
  • https://pypi.org/project/markdown-viewer/ (non-QT)
  • https://pypi.org/project/Markdown-Editor/
  • https://github.com/Python-Markdown/markdown
  • https://pypi.org/project/pywebview/ (non-markdown; if this does not turn Tribler into Flask, Bottle, or DOM Bloatware)
  • https://github.com/Jermolene/TiddlyWiki5 (non-markdown; if this does not turn Tribler into Node.JS Bloatware)
• Demo content: wiki page, out-of-copyright sheet, Portugeese scientific article, and libretext entry.
  • focus on markdown please, store demo content locally in source code repo
  • demonstrate embedding principle: magnet link to a swarm (.mdblob) and filename
  • metadata and storage are not not the focus of this sprint
  • not about the editor, just the content viewer for now
• Deliverable after 2 weeks
  • running code with limited usability (Ubuntu, Windows,Mac)
  • single animated .GIF file suitable for .PPT presentations of max. 2 MByte
    
• Next step would be to do a release with "Rich Metadata Channels"
  • channel get a description in markdown (limited length of 20 lines, 800 Bytes)
  • swarms get a description and/or thumbnails (limited length)

[synctext]

#6214 is a great first step in our "knowledge crowdsourcing" journey. We now have Markdown integrated and are experimenting with tagging in QT-based interface. Update as of 2021:

• goal-driven challenges. Any institute or entity can set a bounty. (towards an open market for innovations)
• Python notebooks in Jupyter are highly effective form of knowledge expression.
• Reproducible science and executable paper
• alter the unit of science: from paper to paper-contribution, evolution of "hyper-specialists"
• enhance the discoverability of knowledge

• "Single Human Hive Mind"
• automated enrichment by agents which parse papers and provide metadata
• Support code: Jupyter QTconsole https://qtconsole.readthedocs.io (estimated Tribler integration time: 2-3 months)

• We could also exclusively focus on Youtube Creative Commons content. Deep dive: "How to Make Money on YouTube WITHOUT Making Videos Yourself From Scratch" 😿

[drew2a]

Related:

• Tag based content discovery and crowdsourcing #6214

[qstokkink]

Since the inception of this issue, we have done away with channels entirely, obsoleting the idea of markdown embedding. Furthermore, the similar approach of Jupyter was also rejected and abandoned.

The successor to these ideas is linked in the post above and, with that, this issue can now be closed.