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

Interception of published events for processing

未关闭
#116 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@cameri 已经在做这个了。

开始于 2022年12月29日。

评估

这个 Issue 还没有评估数据。

描述

enhancement

Is your feature request related to a problem? Please describe.
I think that interception of all incoming events would be useful for:

  • people creating their own filters for spam
  • dynamic whitelists
  • pay-per-event relays

Describe the solution you'd like
There should be a way for any app to connect to the relay (gRPC, WS, doesn't matter, and could probably have authentication) and hook into all events being sent with the following information included:

  • IP address (should account for X-Forwarded-For)
  • The event itself
  • the origin header

and the connected client could answer with one of the following:

  • accept
  • silently drop (OK as if nothing happened but do not persist and relay)
  • drop (with a custom notice)

in the future, AUTH could be required. there should be a configuration option to block all event publishing if there is no connected client that is intercepting the events. (such as for a dynamic whitelist, I wouldn't want to allow non-whitelisted people from posting because the script I wrote went down)

Describe alternatives you've considered
None

Additional context
In the future, this could be extended to more things.

主要语言
TypeScript
星标
829
派生
234
平均合并
2 天 10 小时
30 天内合并 PR
24

环境准备

从这里开始

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

cameri/nostream 的其他 Issue

查看 cameri/nostream 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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