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 摘要。