Mock homepage activity shows the Stellar Development Foundation and Stellar Community Fund 'funding' fake milestones
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #749 by @yggdrasilworld — closed without merging
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start with the recentActivity fixture in mock-data.ts, which lists the Stellar Development Foundation and Stellar Community Fund as funders, then find the homepage section that renders it under "Live on the platform". Check how the timestamps are generated and whether the feed is ever labelled as sample data. Done means the fixture uses clearly fictional sponsor names and the feed is marked as sample data. Open PR #749 already targets this, so review or build on it rather than starting a parallel fix.
Written by the indexing model from the issue text.
Description
Problem
recentActivity in mock-data.ts includes { handle: "Stellar Development Foundation", action: "funded", target: "v2.0: Multi-asset escrow" } and the same for "Stellar Community Fund". The homepage renders this under "Live on the platform" (with timestamps computed to look recent), so production visitors whenever the backend isn't wired are told that real, named organisations funded MergeFi milestones. That's a misleading endorsement claim.
Suggested fix
Use clearly fictional sponsor names in fixtures, and label the feed as sample data.
Related: #201, #284
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 94
- Avg merge
- 1h 2m
- Merged PRs (30d)
- 25
Getting set up
- 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 MergeFi/frontend
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug testing
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
accessibility bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MergeFi/frontend#835 · 1 comment ·
Maintainers usually reply within 1 day
All issues in MergeFi/frontend
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
zapcooking/frontend#946 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
WiliamRosa/cosmos-semantic-platform#40 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
liberation-data/drivine#733 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
makecindy/cindy#10062 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day