🌐 My personal website.
active 2024-07-02 → 2026-01-19 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 567 days from 2024-07-02 to 2026-01-19. Pushes: 52 total, peak 11 in a day. Pull requests: 7 total, peak 4 in a day. Issues: 0 total, peak 0 in a day. Comments: 9 total, peak 4 in a day. Stars: 6 total, peak 2 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 |
|---|---|---|---|---|
| lostf1sh | 55 | 50 | 5 | 0 |
| Copilot | 11 | 1 | 1 | 5 |
| netlify[bot] | 3 | 0 | 0 | 3 |
| google-labs-jules[bot] | 2 | 0 | 1 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#4google-labs-jules[bot]2026-01-19 23:15Restore Homepage Scroll
- Pull request#3google-labs-jules[bot]2026-01-08 04:52
- Issue comment#3netlify[bot]2026-01-08 04:33fix: restore mobile responsiveness
- Pull request#2lostf1sh2025-09-28 04:06
- Pull request#2lostf1sh2025-09-28 04:05
- Pull request#2lostf1sh2025-09-28 04:05
- Issue comment#2netlify[bot]2025-09-28 04:04[WIP] pin my re-started repo to the projects section, with pin icon, heres the repo link @lostf1sh/re-started
- Pull request#2Copilot2025-09-28 04:04
- Pull request#1lostf1sh2025-05-24 22:40
- Issue comment#1netlify[bot]2025-05-24 22:40Fix: Implement Lanyard WebSocket heartbeat Previously, the Lanyard WebSocket connection could drop, leading to an incorrect 'offline' status. This was likely due to your client not sending the required heartbeat packets to keep the connection alive. This commit implements the Lanyard heartbeat mechanism: - Listens for the `op: 1` (Hello) message from Lanyard to get the `heartbeat_interval`. - Sends an `op: 3` (Heartbeat) message back to Lanyard at the specified interval. - Clears the heartbeat
- Pull request#1lostf1sh2025-05-24 22:40
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 6 stars here means stars gained during the window, not the repo's star count.