Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to use full archive search by default #650

Open
Iseratho opened this issue Jul 26, 2022 · 2 comments
Open

Option to use full archive search by default #650

Iseratho opened this issue Jul 26, 2022 · 2 comments

Comments

@Iseratho
Copy link

I would suppose that users that have Academic Research access would typically use the full archive search.
However, it is easy to forget the --archive flag, especially since it is not available for all commands.

It would be preferable to be able to set that full archive search to be the default option.

I understand that silently changing the endpoint is not a good idea. Instead, a warning could be displayed if recent search version is used, where full archive would be available.

@igorbrigadir
Copy link
Contributor

I'm ok with changing defaults for sure, but not frequently, so this should be part of #608 , personally my preference would be to keep the current behavior.

Otherwise, the new command could have:

twarc2 search archive --start-time "..." --end-time"..." "foobar" 
twarc2 search recent --start-time "..." --end-time"..." "foobar"

Something like that maybe? I'm leaning towards having to specify what endpoint you want.

The alternative, is try and maybe guess from the parameters and show an error if academic access isn't available?

The problem is that even descriptive errors confuse people. Also I've no idea what proportion of people using twarc use it with Academic Access vs "Essential" or "Elevated" but I guess twarc could get around it if it could make a test call and find out? Just thinking out loud anyway.

@Iseratho
Copy link
Author

Thanks for your response and thoughts. I agree that it should be part of normalizing commands.

I like the proposed subcommand syntax, as it closely resembles the Twitter API.
Nevertheless, there are a few points to consider:

  • It would require implementing it in counts and conversation as well. In my particular case, I initially performed a full-archive search, but then forgot to specify the option when retrieving its conversations.
  • Nesting too many subcommands (e.g., with the proposed bulk command) could also become confusing (e.g., twarc2 bulk conversation archive confids.txt).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants