micro-analytics/micro-analytics-cli

IP Blacklist

Open

#11 建立於 2017年1月11日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)JavaScript (738 star) (52 fork)batch import
enhancementhelp wanted

描述

Obviously this could be implemented in the client-side on a per-project basis, but I think it would be a decent idea to implement some sort of IP blacklisting system so that stats don't get bloated during development/QA.

Maybe something along the lines of providing a .ipignore file that follows the same general rules of .gitignore files?

127.0.0.1
192.102.*
*.512.*

Again, not sure if you're trying to keep this as micro as possible leaving things like this up to the individual developer. But seems like a feature that many could benefit from.

貢獻者指南

技術棧
javascriptnodejs
領域
backendanalytics
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
basic Node.js knowledgeunderstanding of .gitignore patterns
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
75
研究方向
Examine the request handling logic in the micro analytics cli codebase, likely in a file like index.js or lib/tracker.js, to see where IPs are captured. Look for any existing filtering or ignore mechanisms. The issue suggests implementing a .ipignore file with pattern matching similar to .gitignore. Consider adding a new module to parse and apply ignore rules. Check comments in the issue for any maintainer guidance on whether this feature is desired and any architectural preferences.