Support for referrer_did
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- typescript
调研方向
从 ATStore 的 Atmosphere 应用列表及其登录后进行评价的机制开始，然后追踪外发链接是如何生成的，以及已登录用户的 DID 如何可用。在实现提议的参数之前，明确跟踪和身份验证的范围；完成标准是 ATStore 在受支持的链接上携带 referrer_did。
由索引模型根据 Issue 内容生成。
描述
While it's easy to talk about the atmosphere as a bunch of connected apps the reality is that even following a link from bsky to tangled you need to remember that you should log into tangled with your bluesky account. Some of the work around an atmosphere login button will help but there's no reason we can't do something low lift.
I propose a query string referrer_did that includes the did of the logged in use that clicked a link being sent along on links that go to other atmosphere apps. What those apps choose to do with that data is up-to them but the obvious thing is to trigger a login with the given DID. This means that moving between Atmosphere apps will bring your identity with you.
ATStore seems like the right first place to do this because by default we know that it is a list of atmosphere apps that could support this parameter. Additionally it's log in to review mechanism is a good way to show how a thoughtful implementation of the other side of this could work.
Considerations
It's worth calling out that including a query parameter has drawbacks.
- It is effectively a tracking cookie across the atmosphere - DID alone is not enough to be too worried about but when combined with other information readable from the request we can potentially start to capture information about people.
- Each site can choose how they handle the auth process leading to uneven experiences.
Overall I think the basic idea is sound even with these considerations. If the tracking was a major concern there are a variety of approaches that could be leveraged such as writing a "no-track" record to a PDS that sites would honor.
- 主要语言
- TypeScript
- 星标
- 23
- 派生
- 4
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ATProtocol-Community/ATStore 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 4/5 3-5 天 新手友好度 45/100
-
难度 5/5 一周以上 新手友好度 25/100
ATProtocol-Community/ATStore#44 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 45/100
查看 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 天内回复