LAION-AI / LAION-AI/Open-Assistant
Early detection of possible bot spam
Open
Nobody has claimed this yet.
backend
- Dominant language
- Python
- Stars
- 37.4k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
As the amount of users we have grows, we might face malicious actors who would use bots to spam our API with "bad" data.
We need to have some sort of system to protect or at least detect such occurrences.
Possible solutions (non exclusive):
- Use cloudflare
- Tracking the IP's of the users in the data backend
- GDPR compliance: don't store IP directly, instead salted & hashed.
- Some legitimate users might be affected by this inadvertently, for example: VPN users
- A general tracking / analytics solution would be helpful to detect suprise influx of users / data, some tools mentioned:
- Zabbix
- PostHog
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by mapping the API and data-backend request paths, then evaluate the proposed Cloudflare, hashed-IP, Zabbix, and PostHog approaches against bot detection, GDPR, and false positives; done requires an agreed design and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, observability, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100