Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

original post discovery: handle sites with high post velocity better #771

Open
snarfed opened this issue Oct 10, 2017 · 1 comment
Open
Labels

Comments

@snarfed
Copy link
Owner

snarfed commented Oct 10, 2017

right now, we fetch a site's h-feed(s) and individual h-entries to find syndication links. we do this every 6h if we've seen a synd link recently, ie in the last 2w, otherwise we do it every 2d.

as a hardening measure, we stop after the first 10 entries per fetch. background in #624 and c9e30a2. this means we can miss posts on high velocity site's like @aaronpk's. we currently fetch and process / + /all + /syndicated on his site, which often totals 10-20 or more posts per day. anecdotal post counts per day recently: 13, 13, 25, 22, 25. IRC discussion.

one option is to bump up the 10 post per fetch cap, either globally or for known high velocity sites. another option is to let those sites tell bridgy which feed to use, e.g. just /syndicated, either via UI or rel value or other markup hint.

@snarfed snarfed changed the title original post discover: handle sites with high post velocity better original post discovery: handle sites with high post velocity better Oct 10, 2017
@snarfed
Copy link
Owner Author

snarfed commented Oct 11, 2017

bumped the per-crawl h-entry cap up from 10 to 50, just for beta users (2b47c06). also fixed a bug where manually triggered crawls like Crawl now and Resend weren't updating the last syndication url timestamp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant