js:tools

[traumschule]

possible improvements to the current ecosystem. take ideas if you like, may add references later.

• joystream-lib enables any script to connect to a known jscache uplink and fast sync needed data (via their REST API)

bots

• Important design consideration for bots (summarizing) #649
• What are the most essential notifications? #564
• Discord Bots #109 Discord changes (simplified) #648
• jsbot, merge existing bots Giza Bot Updates #601 extending the FM bot and putting it on Discord #543
• announce event types / targets
  • proposal updates
  • forum posts
    • post edits, moderations
    • proposal discussions
  • wg actions WG status bot #549 Opening/hiring bot #548
  • election periods
  • media updates (videos, channels, series, playlists, nfts)
  • validator payments
  • balance transfers

commands

• status - bot status and short chain stats
• /lookup commands to query jscache
• storage - show stats
• proposals - to vote on
• proposal X
• member handle/ID - from leaderboard bot
• group [name] - show workers and openings
• election - current stage, candidates, votes
• account subscribe/unsubscribe ADDRESS/ memberId
• transfers subscribe/unsubscribe
• events [method|section] subscribe/unsubscribe
• validators
• nominators
• openings [group]
• channel Id/keyword
• bags - sorted by size
• forum [thread|catgory] assign channelName/ID *- assign thread or category to discord channel Bounty Idea - Flexible Discord Forum Bot #152

bridges

announce chain events to

• telegram
• discord
• matrix
• keybase
• irc
• mail
• xmpp
• signal
• twitter Idea: forum twitter bot - WIP #654 Idea: key network metrics Twitter bot (WIP) #655
• mastodon/ActivityPub
• diaspora
• other social networks or protocols (on user request)
• OPTION bridge channels

other ideas

• personalized notifications
• discord survey bot
• fact base: search for term and receive relevant links
• Other DAO/crypto bots - for comparison purposes #569

minutes

• jsreport, obsoletes report-generator and minting-burning-report
  • generates markdown reports based on templates
  • currently syncs needed data from chain (takes time / requires local node)
  • OPTION load data from jscache exported json
  • OPTION fetche all relevant info (except status endpoint data) from jscache / REST API
• jsmonitor (diskless)
• commit daily log analysis to cache: collected hits per asset from access logs, signed with operator key
• lazy (random sleep interval) head requests to all assets in assigned bags for each provider (no bandwith, just latency and availability test), to learn latency of each node to all SP and DP, also fills their cache of tested DPs
• commits own speed results hourly to jscache

cache

see #690

jsstats

merge with #518 and related issues

• jsstats (light front end without API ability, only caches data received from jscache socket to browser store
• cache list of all proposals, posts, threads, openings, applications, reward relationships
• Storage / Distribution component with map
• block explorer: fast block lookup, select block range, filter by event type, bookmark specific events (depends on jscache socket)
• tokenimics component with stats related to token balances with tabs for transactions, salaries, spending proposals, burns and fiat movements)
• validators component with current and historic (browse to era) validator/nominator relations and rewards, stakes graph over time
• governance component with proosals, posts, council snapshot (browse to term) with full text-search
• councils component with historic graphs for voter participation, council stakes, votes per council member
• member modal: activity graph over testnets for selected member (requires jsmulti-cache)

discussion

still necessary? add components to pioneer?

options / ideas

• (a) add selected jsstats components to pioneer (tokenomics, salaries, validator points, leaderboards), ...
• (b) log-less on-site chat to ask questions (moderated by community members)
• (c) plan WG budgets based on on-chain values
• (d) ask for chain data via discord bot (proposal links, posts, openings etc.), notifications for mentions, transfers, ..
• (e) js faq: create a JSON with [ { question: string, answer: string } ]

priorities

• app: complete redesign of all components
• fix low performance (high cpu/ram usage)
• no/less cache option: fetch more on demand, select period, scope
• modals instead of overlays, onFocus: showOverlay
• pre defined views per user type: content consumer, publisher, consul, validators / nominators (hide/star components and save settings)
• each wrapped: grid of icons, click enables detailed view, preview overlay on hover
• add info like https://git.joystreamstats.live/Operations/process/issues/16)

media interface

Page 1: basic settings

• show fill status of store, reset cache button, disable caching
• theme
• key

Page 2: Browse

• Main tabs: trending, latest, channels
• trending: grid of thumbs
• latest: ListView with thumb, descripton, channel name, creator name,
• channels: list view with thumb of last video, creation, video count, views, tags
• right sidebar:
• categories: tag cloud, click limits visible videos
• length:
• lower bar with tabs:
• posts
• votes
• expandable chat
• footer:
• left floating + button: opens new tab with atlas
• about, dcma, suggest feature,
• right floating chat button: expands chat line

Page 3: Video details

• player with controls, playback settings, mpv key bindings
• right sidebar
  • top: products / vendors (expandable)
  • tabs: description, transscript, stats, channel info with latest comments (expandable), uploader info, editor to take notes
• chat bar: chat/comments per video

Page 4: Social - share video

• what
• motivation
• categories

other ideas

• light cli: access jscache/QN

[mochet]

(a) add selected jsstats components to pioneer (tokenomics, salaries, validator points, leaderboards)

WRT this, it may be feasible post-mainnet, but before then as it has its own development/design team I fear it would be extremely difficult. Additionally, it may heavily overcomplicate Pioneer.
I also feel that by putting stuff on just bots or just Pioneer it would limit the amount of customization available to users--maybe a compromise is seeing what works well to put on Pioneer but still having it on Joystreamstats.