Skip to content

feat(feed): find more LinkedIn posts and import links in bulk - #83

Merged
junaiddshaukat merged 1 commit into
mainfrom
feat/feed-more-posts
Nov 1, 2026
Merged

junaiddshaukat merged 1 commit into
mainfrom
feat/feed-more-posts

Conversation

@junaiddshaukat

Copy link
Copy Markdown
Member

Summary

/feed had stalled at about 119 posts. The collector ran 5 searches a day with 10 results each, from a fixed list of 20 queries that mostly returned posts we already had. This makes discovery cover far more ground and adds a manual way in.

  • 25 results per search, the Olostep maximum (API reference), limited to linkedin.com with include_domains.
  • About 99 searches instead of 20: 40 program, topic and year searches (Fellowship by year, DSOC, GSoC, LFX, MindMaster, Tech Talks, FYP…), plus one per known member, so each member found leads to their other posts. The list grows as members are found.
  • The collector remembers where it stopped (FeedCollectorState), so the daily cron and admin runs work through the whole list instead of repeating searches. The cursor only moves when some searches succeed, so a bad key or an outage doesn't skip part of the list.
  • Deep search admin button: 40 searches (about 200 credits) for a one-time backfill, with a confirmation that shows the cost. Requests are capped at 60 searches.
  • Bulk import in admin: paste LinkedIn post links (for example, collected from WhatsApp groups) and they go live straight away. Duplicates and non-LinkedIn links are reported.

Limits worth knowing

Search can only find posts that are public and indexed by search engines. Posts visible only to connections, or never indexed, can't be found by any tool without logging in to LinkedIn, which LinkedIn's terms don't allow for automated collection. That's why bulk import and the submit form matter for reaching the full set.

Test plan

  • tsc and next lint clean for the changed files
  • Local MongoDB, bulk import: 5 links gave 2 added and live, 1 already there, 1 invalid rejected
  • Search list built with 99 searches (40 topic + 59 members)
  • With a wrong API key: all searches fail and the cursor does not advance
  • A request for 500 searches is capped at 60, and logged-out requests get 401
  • Real Olostep run: needs the production key. After merging, use Deep search in admin.

🤖 Generated with Claude Code

/feed had stalled at about 119 posts: 5 searches a day, 10 results each,
from a fixed list of 20 queries that mostly found posts we already had.

- Ask Olostep for 25 results per search (the API maximum), limited to
  linkedin.com
- Grow the search list to about 99: 40 program, topic and year searches,
  plus one search per known member, so every member found leads to their
  other Dev Weekends posts
- Remember where the collector stopped (FeedCollectorState), so the daily
  cron and admin runs work through the whole list; the cursor only moves
  when some searches succeed
- Add a "Deep search" admin button (40 searches, about 200 credits, with
  a confirmation) for a one-time backfill, capped at 60 per request
- Add bulk import: admins paste LinkedIn post links and they go live

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@junaiddshaukat
junaiddshaukat merged commit f82cb1b into main Nov 1, 2026
2 checks passed
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