Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
This reverts commit aea03558bb7c0ac0015a1f1e41c5f5eb1722132e.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
types; tweak error log display
|
|
|
|
removed/uploaded
|
|
color
|
|
|
|
|
|
|
|
|
|
(FEED_CRYPT_KEY)
|
|
|
|
|
|
|
|
Conflicts:
include/rssfuncs.php
|
|
tuning
|
|
|
|
|
|
|
|
|
|
|
|
last_updated
|
|
|
|
|
|
is set to -1 (no update)"
This reverts commit bca1cfbb9580d3ed295f7d93bbf4dce00eae8456.
|
|
to -1 (no update)
|
|
This reverts commit 13b33a3fc3e1b17686894935e3879685cb0578cd.
|
|
|
|
|
|
|
|
sequentially to minimize network access and better utilize caches
|
|
|
|
|
|
|
|
|
|
secondary criteria
|
|
Posts with pubDate in the future always appear at the top, which is ruining the
whole "newest at top" idea. One way to handle this is to use time() instead.
This is what google reader does and seems reasonable.
|
|
|
|
|
|
|