Skip to content

feat: add follows SDK client#27

Merged
senamakel merged 7 commits into
tinyhumansai:mainfrom
senamakel:feat/wk-follow-feed
Jun 16, 2026
Merged

feat: add follows SDK client#27
senamakel merged 7 commits into
tinyhumansai:mainfrom
senamakel:feat/wk-follow-feed

Conversation

@senamakel

Copy link
Copy Markdown
Member

Summary

  • add client.follows to the TypeScript SDK
  • expose follow/unfollow, follower/following lists, stats, and personalized feed calls
  • add a POST agent-auth helper for signed follow writes

Validation

  • pnpm --filter @tinyhumansai/tinyplace build
  • pnpm --filter @tinyhumansai/tinyplace lint
  • pre-push hook: pnpm format && pnpm lint && pnpm build

@vercel

vercel Bot commented Jun 16, 2026

Copy link
Copy Markdown

@senamakel is attempting to deploy a commit to the Vezures Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@senamakel, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 26 minutes and 47 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 09c50f02-8128-45af-ae41-f1459d5c95c2

📥 Commits

Reviewing files that changed from the base of the PR and between 1f5e52c and 9d2eaf7.

⛔ Files ignored due to path filters (1)
  • contracts-sol/Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (39)
  • CLAUDE.md
  • contracts-sol/Anchor.toml
  • contracts-sol/Cargo.toml
  • contracts-sol/FORMAL_VERIFICATION.md
  • contracts-sol/fuzz/Cargo.toml
  • contracts-sol/fuzz/fuzz_targets/pot_split.rs
  • contracts-sol/package.json
  • contracts-sol/programs/escrow/src/lib.rs
  • contracts-sol/programs/settlement_game_lottery/Cargo.toml
  • contracts-sol/programs/settlement_game_lottery/src/lib.rs
  • contracts-sol/programs/settlement_game_lottery/src/math.rs
  • contracts-sol/programs/settlement_game_poker/Cargo.toml
  • contracts-sol/programs/settlement_game_poker/src/lib.rs
  • contracts-sol/programs/settlement_game_poker/src/math.rs
  • contracts-sol/scripts/devnet/README.md
  • contracts-sol/scripts/devnet/e2e.devnet.ts
  • contracts-sol/scripts/devnet/lib.sh
  • contracts-sol/tests/authorization_scoping.ts
  • contracts-sol/tests/e2e.ts
  • contracts-sol/tests/settlement_game_lottery.ts
  • contracts-sol/tests/settlement_game_poker.ts
  • contracts-sol/tests/setup.ts
  • gitbooks/SUMMARY.md
  • gitbooks/games/lottery/README.md
  • gitbooks/games/lottery/draws-and-fairness.md
  • gitbooks/games/lottery/economics-and-safety.md
  • gitbooks/games/lottery/rounds-and-tickets.md
  • gitbooks/games/poker/README.md
  • gitbooks/games/poker/economics-and-safety.md
  • gitbooks/games/poker/fairness-and-history.md
  • gitbooks/games/poker/rooms-and-play.md
  • sdk/typescript/src/api/follows.ts
  • sdk/typescript/src/client.ts
  • sdk/typescript/src/http.ts
  • sdk/typescript/src/index.ts
  • sdk/typescript/src/types/follows.ts
  • sdk/typescript/src/types/index.ts
  • website/src/components/explore/DomainRegistration.test.tsx
  • website/src/components/explore/Signers.test.tsx

Comment @coderabbitai help to get the list of available commands and usage tips.

@senamakel
senamakel merged commit ccd2101 into tinyhumansai:main Jun 16, 2026
6 of 7 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9d2eaf7501

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +15 to +17
record of wins, losses, volume, and net chip movement. No poker action creates an
x402 payment, smart-contract escrow, on-chain settlement, rake, cashout, or
real-money payout.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove x402 poker paths from clients before declaring virtual play

When the backend follows this new virtual-only spec, the current web/SDK flow still treats poker as x402 escrow: useJoinRoom and useRoomAction retry 402 challenges by signing paymentAuthorization, PokerRoom still allows an arbitrary buy-in, and GameRoom still requires escrow/rake and tx-hash fields. That leaves production clients prompting/sending payment data and expecting escrow responses for a virtual fixed-entry room, so joins/actions can fail or render stale state; update those client surfaces in the same change that removes the contracts.

Useful? React with 👍 / 👎.

Comment on lines 15 to 18
PROGRAMS=(
"escrow:$CONTRACTS_DIR/target/deploy/escrow-keypair.json"
"settlement_job:$CONTRACTS_DIR/target/deploy/settlement_job-keypair.json"
"settlement_game_poker:$CONTRACTS_DIR/target/deploy/settlement_game_poker-keypair.json"
"settlement_game_lottery:$CONTRACTS_DIR/target/deploy/settlement_game_lottery-keypair.json"
)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep removed program IDs reachable for reclaim

When running scripts/devnet/reclaim.sh against an existing devnet deployment from before this change, the script sources this PROGRAMS list and only iterates these two entries, so the already-deployed poker/lottery program accounts are no longer closed even if their keypairs still exist under target/deploy. Those upgradeable programs stay live and their rent remains unrecovered; keep a reclaim-only legacy list or otherwise close them before dropping them from the shared list.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant