Trustworthy and helpful reviews
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 25/100
- issue の種類
- 機能追加
- 明瞭さ
- 説明が足りない
- 活発さ
- 静か
- 技術スタック
- typescript
- 領域
- design
調査の方向性
この issue では、ファイル、テスト、エントリーポイントが指定されていません。まず、ATStore に既存する評価およびレビューの実装を特定し、次にプロジェクトが採用したいレビューの仕組みとスコープを明確にしてください。完了には、合意された設計、定義済みのレビュー データと集計動作、および実装計画が必要です。
索引モデルが issue の本文から書いたものです。
説明
I pontificated earlier (😅) about the challenge of using a 5-star review system (anywhere, but particularly on the ATStore). I'd love to see us embrace other mechanisms that could be more informative on the breadth of what the Atmosphere offers, and might even provide a lexicon that other Atmospheric apps might lean on for reviews too!
The big challenges I see with written & 5-star reviews:
- As Ariel mentioned, stale reviews mean you often need to pay close attention to when the review was and what changed on the platform since — who has time for that when browsing lots of potential things?
- Having a time component to how reviews are surfaced seems important
- It requires a bunch of effort from a potential reviewer to summarize the entire app, and to reduce their mixed views into a single output; which means folks either don't bother, or pick a particular aspect to shower praise or criticism upon.
- Making it super easy and fast for anyone to offer a high-context review (with scope for conflicted feelings) would be excellent… if possible
- If folks find something they don't like about an app, the reviews can become a place to 'shout into the void' in a way that can appear overly entitled, stir discontent, and produce pile-ons, when it's a reasonable & genuine frustration (if perhaps ungracefully framed)
- Finding a way to channel frustration into something owners can channel into improvement seems important
- Ensuring there's good context as to what a reviewer should expect from leaving a review seems important
- In small communities, and especially in open systems like atproto, your rating is also a means of support — a "critique in private, praise in public" kinda thing — so early ratings can seem rather one dimensional or fake
- Making sure there's a way to offer balanced feedback without being unsupportive seems important
- There are many interesting critiques of 5 star review systems, often pointing out how folks often vote 5 for 'good', 1 for 'bad' and 4 for 'excellent except for that one thing I want', making it very hard to get useful data out, even when there are lots of respondents.
- Gathering data that maximises the ability for useful analysis seems important
- A single thing often has different value in different contexts. 5 stars for novelty — I want to support this, 1 star for dependability — I wouldn't use it foundationally, yet.
- Allowing expression for nuance, without inflating complexity, seems important
What (I think) people want from a review system:
- To know the thing is worth investing a little time in (via social proof)
- it does what it says
- it's not scammy/doesn't exhibit any dark patterns
- To evaluate A vs. B, if there are two similar things
- To have expectations set. Eg. a thing trying to be artistic and beautiful at the expense of broad feature set vs. a thing trying to be fully featured at the expense of good looks
- … (probably much else not in my head right now 😅)
To that end, here's a pet idea I've had knocking around for a long time, that feels rather suited to atproto, that I call "is/not" reviewing.
- There is an open list of adjectives a review platform has defined for writing reviews.
- A reviewer is offered a handful of them* as three-way toggles; eg. "beautiful" → "is beautiful", "is not beautiful" or not asserted (the default)
- The reviewer picks the ones they have strong opinions about, and offers that "thumbs-up/thumbs-down" verdict on each of the adjective dimensions.
- You could capture a text review too, if you like
- The review system then aggregates these votes in any number of dimensions: how polished it is (is beautiful/is clean/is not work-in-progress), how fun it is (is exciting, is not boring, is artistic), and so on.
You can then extend this as the dataset grows
- Paired with a "Like" button, you can extract that a particular person always rates "is beautiful" for the things they Like → now you can up-rank things specifically marked "is beautiful" for that person
- You can use different languages for the adjectives, and map them in a non-1:1 fashion; "es rico" could boost an "is expensive" signal in Spain, but an "is delicious" signal in Latin America.
- (Hell; with enough data you can eventually ignore what the tag's text is entirely, and just use clustering algorithms to see how a person's ratings fit in with the wider ecosystem)
I feel this system could be particularly good across the Atmosphere particularly (given this kind of methodology could be a lexicon used across review platforms too!) — but this idea hasn't seen the light of day yet, please critique and adapt it; I'd love to hear your thoughts!
Generally: has the ATStore given any thought to other rating/review mechanisms? Do you have any other goals for what you have or will implement?
- 主要言語
- TypeScript
- スター
- 23
- フォーク
- 4
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートなし
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
ATProtocol-Community/ATStore のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
-
Support for referrer_did対応中かも @chris-pardy が 97 日前に担当しました。 オープン
難易度 4/5 3〜5日 初心者へのやさしさ 45/100
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
-
難易度 4/5 3〜5日 初心者へのやさしさ 45/100
-
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
ATProtocol-Community/ATStore#44 · コメント 1 件 ·
ATProtocol-Community/ATStore の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
umbraco/Umbraco-CMS-MCP-Dev#512 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
wimpysworld/sidra#290 ·
メンテナーはふだん 1 日以内に返信
-
defuFn invokes function values for inherited default properties対応中かも @xiehuanyi が今日担当しました。 オープン
難易度 1/5 1時間未満 初心者へのやさしさ 85/100
-
feature request good first issue
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
TabularisDB/tabularis#853 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1時間未満 初心者へのやさしさ 85/100
capricorn86/happy-dom#2474 ·
メンテナーはふだん 2 日以内に返信