instead of taking batch timestamp and score (?) into account, make oldest first sorting work consistently with newest first - i.e. rely on feed-provided timestamp

classes/api.php

@@ -222,7 +222,7 @@ class API extends Handler {
 					$override_order = "ttrss_entries.title, date_entered, updated";
 					break;
 				case "date_reverse":
-					$override_order = "score DESC, date_entered, updated";
+					$override_order = "updated";
 					$skip_first_id_check = true;
 					break;
 				case "feed_dates":

classes/feeds.php

@@ -537,7 +537,7 @@ class Feeds extends Handler_Protected {
 			$override_order = "ttrss_entries.title, date_entered, updated";
 			break;
 		case "date_reverse":
-			$override_order = "score DESC, date_entered, updated";
+			$override_order = "updated";
 			$skip_first_id_check = true;
 			break;
 		case "feed_dates":

classes/handler/public.php

@@ -25,7 +25,7 @@ class Handler_Public extends Handler {
 			$date_sort_field = "ttrss_entries.title, date_entered, updated";
 			break;
 		case "date_reverse":
-			$date_sort_field = "date_entered, updated";
+			$date_sort_field = "updated";
 			break;
 		case "feed_dates":
 			$date_sort_field = "updated DESC";