Age | Commit message (Collapse) | Author |
|
|
|
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.
|
|
|
|
|
|
|
|
force-close db connection in _close()
|
|
(refs #582)
|
|
|
|
published and marked virtual feeds, remove sorting by last_read
workaround
api: add pubsubhubbub ping when article is being set published
bump schema
|
|
|
|
|
|
htmlpurifier might not be relevant anymore because of htmLawed switch,
but <br/>s are annoying
|
|
|
|
|
|
|
|
is allowed
|
|
|
|
stuff (unused)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
plugin_data field for this
|
|
|
|
cache stuff
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|