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

Remove Twitter/tweet analysis #322

Closed
ruebot opened this issue Jul 8, 2019 · 3 comments · Fixed by #323
Closed

Remove Twitter/tweet analysis #322

ruebot opened this issue Jul 8, 2019 · 3 comments · Fixed by #323

Comments

@ruebot
Copy link
Member

ruebot commented Jul 8, 2019

@lintool @ianmilligan1 is there any major reason to keep the Tweet support around? It's not really fully fleshed out, and there are a bunch of dependencies we could clean out if we remove it.

ruebot added a commit that referenced this issue Jul 8, 2019
- Resolves #322
- Resolves #206
- Resolves #194
@ianmilligan1
Copy link
Member

I think removing it makes sense as well: we don't really have the energy and interest to keep that part of Archives Unleashed maintained, and I think keeping AUT on the core mission of "web archive analysis" is a good idea.

@lintool
Copy link
Member

lintool commented Jul 8, 2019

I'd like to keep it, unlike fatjar size is really an issue? Who knows, someone might want to take it up later...? And we have the ambition of doing analysis on webpages mentioned in tweets (and some point in time)?

@ruebot
Copy link
Member Author

ruebot commented Jul 8, 2019

@lintool it's in the git history, and we can add it back in if there is a real demand for it. I'd like to get to the bottom on dependency issues, and removing this will help a lot.

ianmilligan1 pushed a commit that referenced this issue Jul 15, 2019
- Resolves #322
- Resolves #206
- Resolves #194
ruebot added a commit that referenced this issue Aug 15, 2019
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

Successfully merging a pull request may close this issue.

3 participants