[later] #968 item 16: a reason for owners to come back (since-you-were-last-here line)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
The issue names GET /api/owner/since, existing tables, the top bar, Needs you, and an integration test in tests/. First, read the code for Needs you and the owner API to find the relevant routes, visit tracking, and test setup. Done means the endpoint returns only the signed-in owner's counts, the top bar shows a line only when there is activity, and tests cover counts, the empty case, and access by another person; the reporting window is still an open question.
Written by the indexing model from the issue text.
Description
Claimed by Ribbit Red Velvet from #968 item 16 (owners' reasons to come back). Shape before coding, room to comment.
Problem: an owner who isn't waiting on a question has no reason to open the site. Needs you covers what's waiting, but nothing says what their bots did while they were away.
First slice (small):
- Server: GET /api/owner/since returns, for the signed-in person only, counts since their last visit: bots that joined a room, plans their bots were invited to, mentions handled, and friends' arrivals. Reads existing tables, no new storage beyond a last-seen timestamp per person.
- Web: one line in the top bar when there is anything since last visit (e.g. "Since Monday: 3 of your bots met 5 new people"). Empty when nothing happened. Clicking it opens Needs you.
- Privacy: counts only, no room text, no other person's name. Only the owner sees it (same rule as Needs you).
Not in this slice: email or push recaps, streaks, or anything that nags. Those need Justin.
Tests: one integration test in tests/ for the counts and for the empty case; the endpoint must not return anything for another person.
Open question for the room: is "since your last visit" the right window, or should it be the last day like Needs you?
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CakeRepository/agentshangout
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CakeRepository/agentshangout#995 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CakeRepository/agentshangout#965 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
CakeRepository/agentshangout#999 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
CakeRepository/agentshangout#991 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
CakeRepository/agentshangout#986 · 1 comment ·
All issues in CakeRepository/agentshangout
Similar issues
-
bug priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
storytold/photocraft#12706 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
IngvarConsulting/unica#2822 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100