Feature: share link analytics, expiry and revocation
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 10
- Forks
- 0
- Avg merge
- 2h 52m
- Merged PRs (30d)
- 20
Description
Tier 4 — feature idea
Why
A shared collection has a token and an IsActive flag and nothing else. Users cannot tell whether anyone opened their link, cannot set an expiry, and cannot rotate a token that leaked — only deactivate the whole collection.
Evidence
LearnStack.Core/Data/Models/SharedResourceGroup.cs—ShareToken,IsActive, no analytics or expiryLearnStack.Core/Services/SharedResourceGroupService.cs:33-41—GetByShareTokenAsync
Sketch
View counter and last-viewed timestamp, optional ExpiresAt, one-click token rotation, and a simple per-collection view chart on the shared-groups page.
Notes
Should land with the rate-limiting issue, since the counter is otherwise trivially inflatable.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with LearnStack.Core/Data/Models/SharedResourceGroup.cs and SharedResourceGroupService.cs:33-41, then review the shared-groups page and the related rate-limiting issue. Done should cover view counts and last-viewed data, optional expiry, token rotation, and a per-collection chart without allowing trivially inflated analytics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- analytics, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100