简体中文
English
Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is GoKibitz?
GoKibitz is a web tool for discussing go (weiqi/baduk) games move by move. Instead of writing a game review as one long block of text, you attach comments to specific positions and moves, so the conversation stays anchored to the board. Its tagline describes it as "move-by-move conversations about go games."
H3 How it fits into a study routine A typical use: you finish a game, upload or open the record, then leave notes on the moves that puzzled you — "why not extend here?" or "this felt slow." A stronger player replies on the same move, and the discussion reads in the order the game was played rather than as a scattered forum thread. That makes it useful for teachers and students, for club members reviewing each other's games, and for anyone who wants feedback tied to a concrete position instead of general advice.
H3 Practical considerations
- The board context does the explaining, so reviewers can point at a variation rather than describe coordinates in prose.
- Because comments live on moves, long games stay navigable; you can skip to the parts you care about.
- A move-by-move format suits teaching and post-game analysis better than casual chat, since someone has to be willing to write the first comment.
- The site presents itself as an alpha, so expect rough edges and changing behavior.
As a next step, open one of your recent losses, add two or three honest questions on the moves you were least sure about, and share the link with a stronger player. If you want a broader community for game records and reviews, compare with Online Go or OGS; for structured problem practice, Go Magic covers a different need.
How do I start a kibitz on one of my go games?
GoKibitz is built around the idea of attaching move-by-move conversation to a specific Go game, so "starting a kibitz" means uploading or linking a game record and then inviting comments on it. On GoKibitz, the site presents itself as an alpha service with account features (log in, sign up, profile, password change), which tells you the expected flow: you need an account before you can post a game for discussion.
H3 Practical steps
- Create an account or log in. The navigation shows Log In and Sign Up, plus a user menu once you are authenticated.
- Find the option to add or upload a game. The site's purpose is hosting games for discussion, so look for an "upload," "new game," or similar action after logging in. You will typically paste an SGF file or a game record link.
- Save the game so it gets its own page or thread. That page becomes the kibitz: a place where you and others can comment on individual moves.
- Share the game's URL with the people you want to hear from. Because comments are tied to moves, reviewers can point at a specific position rather than writing vague general notes.
- Optionally use the Feature Requests and Bugs links if you cannot find the upload flow. The site is labeled alpha, so the interface may still be changing.
H3 What to expect
Kibitzing is most useful when you want more than a win/loss result. A reader scenario: you have just lost a close game and cannot tell whether move 40 or move 80 was the real mistake. Posting the SGF and asking "where did this go wrong?" gives stronger players a concrete board to annotate, and you get feedback anchored to positions instead of a paragraph of general advice.
If you want a second place to discuss the same game, Life in 19x19 has long-running Go discussion forums, and Online Go hosts games and reviews. Those are separate communities, so you would need to post the game there yourself rather than expecting it to appear automatically.
H3 Decision criterion
Choose GoKibitz when move-by-move comments on a single game are what you want. Choose a forum or a live review service when you would rather have a real-time conversation or a broader audience. If you are not sure the upload worked, check that the game page shows the board and a comment box before you send the link to anyone.
Can I review a professional go match move by move on GoKibitz?
Yes — GoKibitz is built around exactly that kind of move-by-move discussion. Its own tagline describes it as "move-by-move conversations about go games," and the alpha interface centers on a game view where individual moves can be commented on and discussed rather than just viewed as a finished record.
What that means in practice
You can load a game record, step through it move by move, and attach comments to specific positions or moves. That makes it workable for reviewing a professional match: you can pause at a key fight, ask why a certain move was played, or point out an alternative, and others can respond in the same thread. The focus is conversational annotation, not a polished broadcast-style replay.
A concrete scenario
Suppose you're following a title match and don't understand a quiet territorial move in the middle game. You step to that move, leave a comment asking whether a more aggressive response was available, and other users reply with variations and reasoning. The value comes from that back-and-forth layered onto the moves themselves.
Trade-offs to weigh
- It's labeled alpha, so expect rough edges and a small user base — you may not get many responses on a given game.
- It's a discussion tool, not an official archive; you generally need the game record to load in first.
- Quality depends on who shows up. For authoritative pro commentary, dedicated study sites or strong players' own reviews may be more reliable.
Next step
Find the game record you want to discuss, load it, and start by commenting on one or two pivotal moves rather than every move — that tends to draw more useful replies. If you want broader context around a match, GoKibitz is the place for the annotation thread itself.
How is GoKibitz different from other go game review tools?
GoKibitz is built around move-by-move discussion rather than engine output. Where most go review tools center on an analysis engine that scores positions and suggests moves, GoKibitz centers on the conversation attached to each move — the "kibitz" in its name. You post a game, and the review happens through comments and replies tied to specific positions, so the value comes from the people discussing rather than from a win-rate graph.
H3 Where it fits, and where it doesn't
- Best for: players who want human explanation, teaching, and debate about why a move is good or bad — especially kyu players who benefit from reasoning more than raw numbers.
- Weaker for: fast, objective evaluation of a whole game, or solo study where you want an instant engine verdict with no waiting on other people.
- Trade-off: discussion is only as good as the participants. A game with no commenters gives you little that a plain game record doesn't.
H3 How it compares in practice
| Need | GoKibitz's approach | Typical engine-first tools |
|---|---|---|
| Understanding a mistake | Someone explains the idea in words | A number and a suggested move |
| Speed | Depends on who replies | Immediate |
| Learning style | Conversational, argumentative | Quantitative, self-directed |
| Social element | Central | Usually absent |
Concrete scenario: you lose a close game and can't see where it turned. On an engine-first site you'd replay variations alone and try to interpret the score. On GoKibitz you'd post the game and ask, and a stronger player might point to a sequence you'd dismissed — plus other readers may disagree, which itself teaches you something.
H3 Next step
Post one game you found confusing rather than a game you already understand, and ask a specific question about one move. Specific questions get better kibitz. If you mainly want engine analysis, pair it with a dedicated analysis tool instead of expecting GoKibitz to replace one.
Do I need an account to read or join a go game conversation on GoKibitz?
Reading is open; joining the discussion requires an account.
GoKibitz is built around move-by-move commentary on go games, and its navigation includes both "Log In" and "Sign Up" alongside the game view. That split matters: you can browse a game and follow the comments as a visitor, but posting your own kibitz means registering a username and logging in.
Practical next step: open a game you want to discuss, read through the existing thread, then sign up only if you have something to add. If you plan to comment regularly, create the account before your first review so you are not drafting a long note and losing it at the login prompt.
A concrete scenario: you just finished a club game and want stronger players' opinions. You can send the link and let people read the thread without accounts; anyone who wants to reply will need to register first.
Decision criterion: treat an account as necessary for participation, not for access. If your goal is study and silent reading, skip registration entirely.
How can I report a bug or request a feature on GoKibitz?
GoKibitz lists dedicated links for both bug reports and feature requests, so you do not have to hunt for a contact address. On GoKibitz, look at the footer of the page: it includes Feature Requests, Bugs, and a Github link.
Which link to use
- Bugs: use the Bugs link when something is broken — for example, a move not appearing on the board, a game failing to load, or a comment that will not post. Describe what you did, what you expected, and what happened instead.
- Feature Requests: use this for ideas rather than faults — for example, asking for a different board theme, a new way to filter games, or an extra review tool. Explain the problem you want solved, not just the feature name.
- Github: useful if you prefer an issue tracker or want to see whether someone has already raised the same problem. Check existing issues before opening a new one.
A practical example
Suppose a game record loads but the move numbers are missing. That is a bug, not a feature request. Note the game URL, your browser and device, and the exact step where it went wrong, then submit it through the Bugs link. If you instead want move numbers displayed in a larger font, that is a feature request.
Next step
Open the GoKibitz footer and click the link that matches your case. Keep the report to a few sentences: one line on what you were doing, one on what went wrong or what you want, and any link or screenshot that helps reproduce it. Specific reports are far easier to act on than general ones.
Akamai Connected Cloud
User reviews (0)