A Reddit-like platform for community-driven curation. Find the best content in an instant
active 2025-10-30 → 2026-04-03 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 156 days from 2025-10-30 to 2026-04-03. Pushes: 46 total, peak 6 in a day. Pull requests: 8 total, peak 5 in a day. Issues: 26 total, peak 12 in a day. Comments: 4 total, peak 1 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| omardoescode | 77 | 42 | 8 | 1 |
| roaa46 | 4 | 4 | 0 | 0 |
| coderabbitai[bot] | 3 | 0 | 0 | 3 |
Recent activity
Latest issues, pull requests and releases
- Pull request#31omardoescode2025-12-20 10:50
- Pull request#31omardoescode2025-12-20 10:50
- Pull request#30omardoescode2025-12-20 10:49
- Issue comment#30coderabbitai[bot]2025-12-20 10:47Interaction service integration
- Pull request#30omardoescode2025-12-20 10:47
- Issue#16omardoescode2025-12-20 07:39Enhance the database schema in content storage to include all possible formats of content
- Issue#15omardoescode2025-12-20 07:39Change the content storage so that it determines if content needs processing
- Issue#18omardoescode2025-12-20 07:39Authentication
- Issue#13omardoescode2025-12-20 07:38Use Content Storage as a cache to avoid unnecessary content processing
- Issue#24omardoescode2025-12-20 07:38Change the api gateway to assign the correct user id based on the JWT token sent with the requests.
- Pull request#29omardoescode2025-12-20 07:37
- Pull request#28omardoescode2025-12-05 21:57
- Pull request#27omardoescode2025-12-05 21:56
- Issue comment#17omardoescode2025-11-15 04:46The Classification Problem
- Issue#25omardoescode2025-11-15 04:31Look into solutions to make the content submission flow faster, either using caching or speeding up content processing
- Issue#25omardoescode2025-11-15 04:31Look into solutions to make the content submission flow faster, either using caching or speeding up content processing
- Issue#24omardoescode2025-11-15 04:28Change the api gateway to assign the correct user id based on the JWT token sent with the requests.
- Issue#24omardoescode2025-11-15 04:28Change the api gateway to assign the correct user id based on the JWT token sent with the requests.
- Issue#23omardoescode2025-11-15 04:27Forget Password
- Issue#23omardoescode2025-11-15 04:27Forget Password
- Issue#22omardoescode2025-11-15 04:25Email Confirmation functionaltiy
- Issue#19omardoescode2025-11-15 04:24Registration using username, name, email, password, optional profile picture, using JWT
- Issue#19omardoescode2025-11-15 04:24Registration using username, name, email, password, optional profile picture, using JWT
- Issue#16omardoescode2025-11-15 04:20Enhance the database schema in content storage to include all possible formats of content
- Issue#15omardoescode2025-11-15 04:19Change the content storage so that it determines if content needs processing
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.