Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Trustworthy and helpful reviews

未关闭
#10 5 条评论 3 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
typescript
领域
design

调研方向

该 issue 未指定任何文件、测试或入口点。首先确定 ATStore 现有的评分和评论实现,然后明确项目希望采用哪种评论机制以及范围。完成该工作需要达成一致的设计、定义评论数据和聚合行为,并制定实施计划。

由索引模型根据 Issue 内容生成。

描述

enhancement

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 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ATProtocol-Community/ATStore 的其他 Issue

查看 ATProtocol-Community/ATStore 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。