Skip to content
This repository was archived by the owner on Feb 10, 2025. It is now read-only.

Maintenance: this project has been archived #476

Open
hugovk opened this issue Feb 2, 2025 · 5 comments
Open

Maintenance: this project has been archived #476

hugovk opened this issue Feb 2, 2025 · 5 comments

Comments

@hugovk
Copy link
Member

hugovk commented Feb 2, 2025

I'm no longer using Twitter and all my twitterbots are long dead and thus my use of the API via this library.

I don't even know if this library still works with the API, but I'm not planning on maintaining this library any longer. We've not merged anything since October 2022.

If the other maintainers are of similar opinion, shall we declare this project a success (first commit 17 years ago!), and archive the repo and PyPI project? (PyPI archiving is new.) This would make the maintenance status clear, both actions are non-destructive and reversible, and the PyPI downloads are still available.

cc @sixohsix @RouxRC

@boogheta
Copy link
Collaborator

boogheta commented Feb 6, 2025

That's about the same for me, all my API keys and associated bots or tools are all dead since the spring 2023 and I've personally left Twitter for Mastodon and Bluesky.
I know the lib still works (at least my v2 branch) with the remaining paying APIs but I haven't used it myself.
We have a tool at @medialab (minet) that leverages the lib for providing CLI tools to query the API which apparently still works, but since it uses a fixed released version, if the PyPI existing versions remain, I see no problem in archiving the code. I don't plan on maintaining it anymore either.

@sixohsix
Copy link
Collaborator

sixohsix commented Feb 6, 2025

Unsurprisingly I'm also not using or maintaining this library. The fact that it continued to work with the paid API was quite sad to me. Our free labor letting Twitter make money...

It's been one heck of a ride but it's time to let it go. And yes, I will call this a success. The project is finally complete. And I thank you for maintaining and caring for it for so long when I stepped back. It wouldn't have survived without your efforts.

@hugovk hugovk pinned this issue Feb 7, 2025
@hugovk
Copy link
Member Author

hugovk commented Feb 7, 2025

Open source is always team work, thank you both :)

I've closed 50 open issues and one PR, and opened #477 to leave a note at the top of the README before the repo is archived.

I don't have permission to mark the PyPI project as archived, please could one of log in and visit https://pypi.org/manage/project/twitter/settings/ and click the button?

Image

I'm not too bothered about publishing a final release to PyPI? But I'm happy to do so if you'd like.

I'll also delete the repo secrets at https://github.com/python-twitter-tools/twitter/settings/secrets/actions before archiving this repo.

@boogheta
Copy link
Collaborator

Considering the recent commits since the latest release, I don't think a new release is useful for v1, and there was no new commit in the v2 branch since the latest v2 rlz, so I think we're good.
I'll archive the pypi project right away.
Thanks again @hugovk !
And thanks to you two for the common work on this, it was a nice experience outside X and Musk's shenanigans!

@hugovk hugovk changed the title Maintenance: shall we archive this project? Maintenance: this project has been archived Feb 10, 2025
@hugovk
Copy link
Member Author

hugovk commented Feb 10, 2025

Thank you!

I've closed 50 open issues and one PR, and opened #477 to leave a note at the top of the README before the repo is archived.

Merged:

Image

I'll also delete the repo secrets at python-twitter-tools/twitter/settings/secrets/actions before archiving this repo.

Done.

Let's leave this last issue open and pinned for visibility, and I will now archive the repo at https://github.com/python-twitter-tools/twitter/settings, where it can be later unarchived if needed.

Thanks again everyone! 🎉

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

No branches or pull requests

3 participants