Why not implement newest, near and oldest for the CDX Server API as we have for the Availability API

[akamhy]

Is your feature request related to a problem? Please describe. Yes, the Availability API is not reliable when compared to the CDX server API. And Server usage has a steeper curve, and instead of telling users to implement these methods on their own using the interface, it would be cool to have these methods in the WaybackMachineCDXServerAPI class.

Describe the solution you'd like The following three methods should be inside the WaybackMachineCDXServerAPI class.

• WaybackMachineCDXServerAPI.newest()
• WaybackMachineCDXServerAPI.near()
• WaybackMachineCDXServerAPI.oldest()

Describe alternatives you've considered N/A

Additional context See #154

[akamhy]

• limit=-1 : Latest/Newest CDX server archive
• https://github.com/akamhy/waybackpy/issues/154#issuecomment-1041536164 For oldest.
• No idea what to do for near as of now. https://web.archive.org/cdx/search/cdx?url=google.com&limit=1&closest=20101010101010

[akamhy]

see also https://github.com/internetarchive/wayback/blob/master/wayback-cdx-server/src/main/java/org/archive/cdxserver/CDXServer.java

[akamhy]

Near can be implemented by leveraging the to and from params.

waybackpy --url google.com --cdx --limit 1 --from 201010101010

waybackpy --url google.com --cdx --limit -1 --to 201010101010

Pick the closest one which has a better HTTP status code.

[akamhy]

Use https://github.com/internetarchive/wayback/issues/237#issuecomment-1042577291 for near.

[akamhy]

Implement near from https://web.archive.org/cdx/search/cdx?url=google.com&limit=1&closest=20101010101010&sort=closest&filter=statuscode:200 and oldest and newest should invoke near with appropriate args.