AlgonikHQ

Activity

Stars and mentions · Last 30 days, Oct 19 – Nov 17

GitHub stars0
Mentions11
01234Oct 19Nov 2Nov 17
UTC days · repositories AlgonikHQ owns0 repositories

Top repositories

AlgonikHQ’s repositories ranked by new forks, as on trending.

Loading

Contributes to

Repositories outside AlgonikHQ’s account where AlgonikHQ opened or reviewed pull requests in the past 365 days.

Who noticed AlgonikHQ

Everyone who starred or forked AlgonikHQ’s repositories since the archive began in 2011.

Notable accounts

Ordered by the stars their own repositories have received.

Biggest fans

Accounts that starred the most of these repositories.

Breakout weeks

Each repository’s best week of new stars, with the release published around it.

Mentions

11posts
Nov 180 posts
  1. Week 2 of forward testing my trading strategies: −18.42R. Full research log (method, results and what failed): AlgonikHQ/algonik-research Two corrections first, because the point of building in public is that the numbers are real. 1My week-1 report window skipped Friday 6 Nov (11 trades, about −7R). Fixed: totals now reconcile. +2.24R + (−18.42R) = −16.18R over 100 paper trades. 2I changed two review points after week 1: opening-range breakout from 50 to 538 trades, intraday momentum to 139, set from each strategy's backtest spread. It's stricter, but it happened after a good week, so I'm saying so. The week:
• Opening-range breakout: −7.49R. Last week's +12R mostly went back. Its 11-year backtest says no edge (−0.070R a trade), and I'm listening to that.
• Intraday momentum: −0.083R a trade forward, against −0.086R in the backtest. That's about the cost of trading it. The backtest was right.
• Trend following: 17 stop-outs at about −1R each and 25 still open. Losers close first; judge it at the December roll.
• Carry, positioning and pre-Fed drift: too few trades to say anything. The lesson: one good week told me nothing. An 11-year backtest told me a lot. Paper only, frozen rules, results every Friday. Not advice.

    1 like · 30 views
  2. Two #Solana bots ran live in spring 2026 with small stakes: a new-launch sniper and a scalper. Both are now retired. This is the honest record. Preview: AlgonikHQ/algonik-crypto-research t.co

    1 like · 39 views
  3. @Nightshiftape Thanks — publishing the losses was the point. Full audit + current research log (still no live trades) is here if useful: AlgonikHQ/algonik-crypto-research

    5 views
  4. @UPLOCKfi Thanks — publishing the losses was the point. Full audit + current research log (still no live trades) is here if useful: AlgonikHQ/algonik-crypto-research

    1 like · 8 views
  5. @mitansh_j07 Thanks — publishing the losses was the point. Full audit + current research log (still no live trades) is here if useful: AlgonikHQ/algonik-crypto-research

    3 views
  6. Reddit · · r/buildinpublic · u/AlgonikHQ · AlgonikHQ/90minwaffle-web

    Build log: what I fixed on my football site this week, and the mistake that broke part of my own homepage for a day Quick build-in-public update on the football site I run solo (90minwaffle.co.uk). Most of this week was cleanup and safety work, not new features, and I made at least one mistake worth sharing. Things that were wrong and are now fixed - Stale pages A nightly job fed my tournament, league and club pages, and it only got a game's result when a player in that game happened to be refreshed. Some pages were up to a week behind. I now overlay results from the database that updates every five minutes, using one shared helper. - A case-sensitivity bug One of my stats scripts filtered games on status = 'finished', but part of my data stores 'FINISHED'. SQLite compares text case-sensitively, so that job ignored finished games in 11 leagues. Nobody saw it because those leagues aren't on that page yet, but it would have bitten as soon as they were. - Live games that wouldn't leave. Some finished games stayed on the live list until a blunt 150-minute backstop removed them. They now have status-aware limits (a first half can't last 75 minutes), and every removal logs the status and minute the feed gave, so I can finally see what the feed was actually saying. - A stale figure. One published number stayed out of date for about 12 hours because a safety check refused to publish a value that disagreed with a second calculation of the same thing. The check did its job, since the second calculation just hadn't refreshed. A small job now rebuilds it and re-checks, and it still refuses to publish if they disagree after a rebuild. Safety - My public data files carried some internal fields the front end didn't need. The full copies now live in a private folder, the exporters publish finished display text, and the front end just renders it. - The public GitHub repo for the site's front end has a fresh single-commit history, and the publish script blocks the push if it finds secrets, server paths or internal terms. The old repo is deleted. The mistake After a deploy I re-locked a set of files with chattr +i. Three of my own builders write to some of those files without unlocking them, so they were silently refused for about 28 hours. One section of the homepage stopped updating, and I only noticed from a pile of alerts the next evening. Lesson: check what else writes to a file before you lock it. I've since made the lock script skip those files. Front-end repo:AlgonikHQ/90minwaffle-web The data pipeline and methods stay private, but I'm happy to talk through the engineering if anyone has questions.

    1 point · 4 comments
  7. Reddit · · r/90minWaffle · u/90minWaffle · AlgonikHQ/90minwaffle-web

    Quick update on 90minWaffle (90minwaffle.co.uk), the football data site I've been building in public. It's still in beta, and the last couple of weeks went into one thing: making sure every number on the site is something you can check. The record - Every tip the model publishes stays on the record, wins and losses. 74 early test and duplicate tips were excluded, and each one is listed with its reason. - The money record only counts tips that had a real bookmaker price attached before kick-off. Tips with no price are tracked as wins and losses but are not in units or ROI, and the site now says "Not in ROI" instead of a misleading 0.00u. - Stakes are paper stakes: 1 unit per single. Bet builders and one early single were half-unit stakes. Some pages said "1 unit each" without that exception, so I fixed the wording everywhere and logged it as a correction. - There's a month-by-month table with all calls next to the real-price results, small months flagged (under 10 priced tips, where ROI swings a lot), and the worst runs shown. - The record is checked against the bot's own figures before it's published, and rebuilt automatically if they disagree. That check held the page back for about 12 hours last Sunday after a win settled overnight. The page was a result behind, not wrong, and it's in the corrections log. Snapshot as at 2 November. That's a small sample, so please read it as a record, not proof of an edge. Past results don't predict future ones. Corrections log It's public, permanent and dated (49 entries so far). Each one says what was shown, what's correct, and what it affected. Recent ones include BTTS rates that were really "how often a team conceded", league tables frozen on last season's figures, club pages showing another club's games, and a fact-check of every trivia and quiz item (187 of 585 corrected, 120 pulled because I couldn't verify them, 44 new ones added). FootballIQ Season sims, form vs expected, a streak screener, a club browser and player search, covering 60+ competitions, 1,600+ clubs and 23,000+ players. Live scores and matches Scores and minutes refresh every 30 seconds, stoppage time shows as 45+ or 90+, and a game that stops updating drops off the live list. I also added limits so a finished game can't sit there for long. Daily stuff - Fans v the model votes. They close 5 minutes before kick-off, the fan split shows afterwards, and you can get a reminder 30 minutes before and your result at full time. - Daily trivia and guess-the-player, with streaks and trophies. - Follow your club and country. Under the hood There's an automatic quality check across the site every week. The site's front-end code is public on GitHub (AlgonikHQ/90minwaffle-web), while the model and the data stay private. Next A "this week: you v the model" card, prediction history with filters, notification choices, faster mobile loading, and email sign-up last. If there's something you'd want to check on the site and can't, tell me and I'll look at it. 18+ only. Not financial advice. If gambling is a problem for you: BeGambleAware.org or GamStop.

    1 point
  8. Reddit · · r/algotrading · u/AlgonikHQ · AlgonikHQ/algonik-research

    65 strategy tests, 0 passes: what a weekend of honest backtesting taught me about costs Quick update on my algo research log. First off, thanks to those giving feedback, it’s been very helpful. Everything is preregistered, rules written down before the data, real bid/ask costs, a flip test, random-entry baselines, and data the idea never saw. This weekend and into Monday morning, I ran 10 more tries. None passed. The one idea that survived my earlier rounds finally hit its locked 2005–14 holdout: −0.017R over 1,236 trades. Retired. I said I'd publish it either way, so here it is. Carry looked great in two periods and then fell apart in the third (2015–22). Lesson, it only works when rates give it room. The interesting one was textbook trend following across 42 markets. The direction signal was real, it beat 97% of random runs. But on CFDs the overnight financing ate it (−0.08R per trade). Same rules with futures-style costs: +0.14R. Same signal, different venue, opposite result. Then I tried short holds to dodge financing, intraday momentum, opening-range breakouts, pre-Fed drift, index pairs, and fading crowded futures positioning. The fast ones had no direction information at all, the flipped trades lost just as much, so it was pure spread. Pre-Fed drift and positioning showed something real but too small to clear the bar. I also corrected myself, I'd estimated intraday index costs at 2% of a stop. Real fills said 6–7%. On the live demo, I found that most of my wide-spread stop-outs at the 5pm New York rollover never actually traded through the stop on mid price. The spread spike did it. There's now a guard for that window. Where I am, six ideas running forward on paper with frozen rules and fixed kill points. Nothing traded with real money. The pattern is getting clearer, real but small edges, and costs decide everything. Not advice, just a log. Happy to answer questions on method.

    10 comments
  9. Reddit · · r/algotrading · u/AlgonikHQ · AlgonikHQ/algonik-research

    I went quiet for a while. Here's what happened. I tested, 55 trading strategies properly, and almost all of them failed. It's been a while since I posted, so here's the honest update. **The short version:** I stopped building and started proving. Instead of adding more features to the bot, I spent the last stretch testing whether the ideas behind it actually work. Most don't. That's been the most useful thing I've done since starting AlgonikHQ. --- Where I've been The forex bot has been running on a demo account for months. It looked *close*: some green weeks, some red weeks, hovering around break-even. The problem with "close" is that you can't tell if you're nearly there or just getting lucky. So I built a proper testing setup and put every idea through it. The rules: - Rules first. Entry, exit and what counts as a pass are written down *before* I see any results. No moving the goalposts. - Real costsEvery trade pays the spread, overnight financing and a slippage allowance. - The flip test Every signal also gets traded backwards. If the reverse does just as well, the "edge" is luck. - The random test Same stops and exits, random entry times. A real signal has to beat 90% of random runs. - Unseen data. Design on one period, check on another, and keep some data locked away for the final test. About 55 variants. Tens of thousands of simulated trades. FX, stock indices, gold, oil, grains, bonds. 15-minute charts up to weekly. 2005 to now. --- What I found 1. My bot's original entry was picking direction at random. Traded backwards, it did the same. That one hurt, but it explained the months of "nearly there". 2. Costs decide everything. Short intraday trades pay more in spread than the edge is worth. Trades held for weeks pay more in overnight financing than they earn. The only cheap zone is holding for a few days and closing before the weekend. 3. Rising markets fool backtests One trend system looked brilliant on stock indices. Then random long entries made money too. It wasn't the signal. It was the market going up. 4. One idea survived the flip and random test. It's a momentum idea, in the same family I've always traded. It's statistically real. But it's small, and after costs there isn't much left. So it's not going live. It's being tracked live on paper instead, to see if it holds up on data nobody has seen. 5. Knowing when to stop testing is part of the method. Test enough variations and one will look amazing by pure luck. I've paused the pattern hunting for that reason. --- What's running now - The demo bot, with tighter risk rules, automatic failure alerts and a weekly report measured honestly in R (multiples of risk). - A "shadow" tracker that logs the surviving signal every night and records how it plays out. No orders, just evidence. Nothing goes near real money, or a prop-firm challenge, until it clears targets I've written down in advance: at least +0.1R per trade after all costs, a profit factor of 1.2 or more, 50+ trades, and drawdowns well inside prop-firm limits. --- Why I'm sharing the failures Most trading content only shows the wins. I'd rather show the whole picture, including the bits that didn't work, because that's where the real lessons are. The goal hasn't changed. FIRE@45 is still the destination and the bot is still the vehicle. I'm just making sure the vehicle actually works before I put fuel in it. The full research log (method, results table and lessons) is public here: AlgonikHQ/algonik-research The exact rules and code stay private, but everything you need to see how I test, and what failed, is in there. Monthly updates from here on, good or bad. Not financial advice. Demo results only. If you've been through something similar, or you know a cost or test I'm missing, I'd genuinely like to hear it.

    52 points · 39 comments
  10. Reddit · · r/u_AlgonikHQ · u/AlgonikHQ · AlgonikHQ/90minwaffle-frontend

    i run a full football data site on one small server with free APIs. here's how it's built (and the bugs that nearly got me) 90minwaffle.co.uk is my football site: live scores, match previews, club and player pages, and a tips model that publishes every result. this post is the tech side for anyone curious how a one-person project like this actually holds together. **the stack** • one small vps, ubuntu, everything in python • sqlite as the main store. results, fixtures, odds, tips, the lot • cron and systemd running dozens of small jobs (live poller every minute, exporters every 5, page builders, checks) • pages are mostly static html built by python, plus small client scripts for the live bits • cloudflare in front for caching • free data only for now: football-data.co.uk csvs for history, a free live api for scores, free tiers for the rest. history goes back 10 seasons across the big leagues and the lower divisions **the rules i stick to** • staging first, always. test, then live • back up before touching anything • locked files. important scripts are made immutable, so nothing (including me half asleep) can overwrite them by accident • no keys in code, ever. and a secret scan runs before anything goes to github **the safety net** the bit i'm proudest of isn't a feature, it's the checks. • a regression watch with 83 checks. every fix gets a marker in the code, and if any marker disappears (old code creeping back), i get a telegram alert • a guard runner that keeps pages in the right shape every minute • a live minutes watch that compares what the site shows against the feed every 10 minutes • a settlement auditor that re-checks every settled tip against the raw scores. currently 99 out of 99 agree • encrypted off-site backups every night, with a weekly integrity check **the model's "brain"** every week it reviews itself: roi, closing line value (did we beat the final price), calibration (when it says 60%, does it hit 60%), and a both-halves test to see if an edge holds up or just got lucky. it doesn't switch anything off on its own. it suggests tweaks and starts shadow tests on new ideas, and nothing goes live without me signing it off. **bugs that taught me something** • **the 114 minute game.** a dutch match got abandoned at 4-0. the feed froze, kept counting, then quietly reset the game to "not started". the site showed 114′. fix: stoppage shows as 90+, stalled games drop out of live after 12 minutes, abandoned is its own status now, and a watch alerts if live data ever disagrees • **paderborn played 15 games in 9 weeks.** two data sources spelled the club differently, so every game counted twice. a scan found 25 clubs like this across 7 leagues and 231 double-counted games. all merged now • **athletic club isn't athletic bilbao.** brazil has its own athletic club, and a shared name map was about to feed bilbao's form into brazilian previews. fixed with a league-aware rule **building in public** the front end is open on github. the layout scripts, the live updater, the changelog, all of it. happy to answer questions on any of it. if you're building something similar on free data, the boring stuff (checks, backups, logs) matters more than the clever stuff.

    1 point

Achievements

Awards earned by the repositories AlgonikHQ owns. Select an award to embed its badge.

No awards yet

Repositories earn awards by reaching the top three in a completed trending day or week.

A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.