Перейти к содержимому
Furbol — How It Works

Activity Log

Это содержимое пока не доступно на вашем языке.

Activity Log

Furbol keeps a running log of every meaningful thing that happens on games and profiles: someone booked a spot, a game hit quorum, the host cancelled, the host nudged the kickoff time, someone posted a message, someone quit, someone checked in. The app shows you that log, sliced into the view you’re looking at.

Where you’ll run into it

You’ll see the same underlying event stream filtered six ways, depending on where you’re looking from.

Game log

What happened on this specific game — from when it was created to its latest booking, quit, quorum update, cancellation, check-in, or message. This is what you see when you open a game and scroll its activity tab.

Venue log

Everything across all games at a specific pitch. Useful when you’re scouting a venue: who plays there, how busy it is, what games have hit quorum recently.

Profile log (someone else’s)

When you open another player’s profile, you see their public activity: games they’ve created, games they’ve joined, who they’ve started following, games they’ve hosted. Not their private moves — just what other players would reasonably see happen to them.

Local log

A feed of what’s happening in games near you (within 50km). A good way to spot “there’s a game across town that just hit quorum” even if you weren’t following it.

Personal log

Your personalized feed: activity from people you follow, and from games at venues you follow. This is “stuff I specifically care about” rather than “stuff near me.”

My games log

Activity on games you’re part of: games you host, games you’ve booked into, games you follow. The operational feed — the one you’d check before heading to a game.

Invitations log

A dedicated list of game invitations you’ve received that are still pending, for games that haven’t ended yet. See Game Invitations.

What every line tells you

Each entry in a log shows four things:

  • Who did the thing (a player, the host, or Furbol itself).
  • What happened (the event — e.g. booked a spot, hit quorum, posted a message).
  • Which game (or profile) it’s attached to.
  • When it happened.

Some events carry extra detail — a moved player shows the old and new position; a message shows the text and its reactions; a check-in shows who was checked in for whom.

How far back you can scroll

The log is grouped by time — today, yesterday, this week, last week, and older. When you open a log, it starts at the top of “today” and, as you scroll, steps through to the next group when the current one runs out. You don’t pick a group yourself; the log just cascades through.

Messages on games

When the event is a message, it’s more than a log line — it’s in-game chat. Other players on the game’s roster can react with a like or a dislike. Messages flow through the same activity stream, so “someone posted” shows up in everyone’s relevant feed without a separate chat tab.

What isn’t in the activity log

  • Wallet transactions. Those live in your wallet history, not here. See The Wallet.
  • Private messages between two users. Furbol doesn’t have DMs — chat is scoped to games.
  • Blacklists. Blacklisting is private to you; other people don’t see you’ve blacklisted them. See Blacklisting.