Skip to content

Commit

Permalink
update some info (botlabs-gg#526)
Browse files Browse the repository at this point in the history
* update yw readme

There was a duped part so i removed that, also fixed some spelling stuff

* Update info.html

change reddit info
  • Loading branch information
buthed010203 authored and jogramming committed Oct 6, 2019
1 parent e29aed1 commit 98e286c
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 19 deletions.
2 changes: 1 addition & 1 deletion info.html
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ <h2>Features</h2>

<h3>Feeds</h3>
<ul>
<li>Super Fast reddit feeds (within 10 seconds normally)</li>
<li>Super Fast reddit feeds (within 1 minute)</li>
<li>Fast youtube feeds (within a couple minutes)</li>
</ul>

Expand Down
19 changes: 1 addition & 18 deletions youtube/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,27 +13,10 @@ Then a video was published (but uploaded a long time ago):
1. vid1 - uploaded 6pm - published 6pm
2. vid3 - uploaded 5pm - published 11pm

vid3 was published after the latest vidoe but still appears at the bottom. this causes issues as we have no idea when to stop looking now. Currently YAGPDB handles this fine as long as it's not uploaded longer than 50 videos ago, in which case it may or may not catch it.
vid3 was published after the latest video but still appears at the bottom. this causes issues as we have no idea when to stop looking now. Currently YAGPDB handles this fine as long as it's not uploaded longer than 50 videos ago, in which case it may or may not catch it.

In the future I'll do a hybrid mode with search. Those super late published videos however will show up in Discord super late. I cannot use search for 100% either because it costs 100 times for api quota to use, meaning it could be up to hours behind.

The feed plugin is complicated because we use the user's `uploads` playlist, and that is sorted by actual upload date instead of publish date

so say you have this channels videos:

0. vid2 - uploaded 10pm - published 10pm
1. vid1 - uploaded 6pm - published 6pm

Then a video was published (but uploaded a long time ago)

0. vid2 - uploaded 10pm - published 10pm
1. vid1 - uploaded 6pm - published 6pm
2. vid3 - uploaded 5pm - published 11pm

vid3 was published after the latest vidoe but still appears at the bottom. this causes issues as we have no idea when to stop looking now. Currently YAGPDB handles this fine as long as its not uploaded longer than 50 videos ago, in which case it may or may not catch it.

In the future i'll do a hybrid mode with search, those super late published videos however will show up in Discord super late, i cannot use search for 100% either because it costs 100 times for api quota to use, meaning it could be up to hours behind.

### Storage layout:

Postgres tables:
Expand Down

0 comments on commit 98e286c

Please sign in to comment.