⚠️ Deprecation notice ⚠️

Question

⚠️ Deprecation notice ⚠️

mattdonnelly opened this issue 2 years ago · 9 comments

TL;DR This package will be deprecated in about one month. I'm not going to delete it for now but will no longer be maintaining it officially.

Hi everyone,

I created this project back when Swift was a very new language, as a way of learning it and sharing ideas on how to deal with APIs using it. Since then, it's grown a lot of in popularity and has been used by more people than I had ever imagined, which was been amazing to see.

Unfortunately, I haven't had time to contribute actively to this project for several years. For a long time, I relied on other people who did a far better job at maintaining it than me. However, over time this repo has slipped out of date with Twitter's API and there's been less and less activity here.

As a result, I've decided to officially deprecate this project in about one month from now. This means there will be no future changes to the repo, so on the off chance that anyone is still using this, you should seek out alternatives now. To deprecate it I will be will be taking the following steps:

Remove all collaborators with write access to prevent future changes
Update the README to indicate the project is no longer maintained and link here
Edit the README and repo description to indicate the project is no longer maintained
Add a deprecated GitHub topic

My goal here is to prevent this from becoming yet another horror story about an inactive developer of a widely used library unintentionally distributing malware.

I don't plan to the delete or transfer the repo to prevent it suddenly breaking people's code, but if anyone has other recommended courses of action or questions please leave them here.

Massive thanks to everyone that has contributed and helped maintain this project thus far. Especially @meteochu and @zntfdr. I'll follow up here in a months time once I begin taking the steps to deprecate the project.

Answer 1 · 2022-05-07T02:24:49.000Z

It is a sad news.
Everyone have any other library to recommend?

Answer 2 · 2022-05-07T03:25:42.000Z

@mattdonnelly Thanks for the great library.

I was a Swifter user. I appreciate the contributors.

@jianming-work

I have created and am still maintaining a new TwitterAPI library for Swift this year.
It supports v1 and v2 APIs and Swift Concurrency.

Please try it out if you like.

https://github.com/mironal/TwitterAPIKit

Answer 3 · 2022-05-11T09:31:36.000Z

Thanks Matt, was a pleasure to use the library!

Answer 4 · 2022-05-14T09:21:58.000Z

Thank you @mattdonnelly , and also @mironal

Answer 5 · 2022-05-14T12:35:54.000Z

@mattdonnelly fantastic work and the correct thing to do now. Using your code was one of the main pleasures of working with devices the last few years. As you know for every 1 person who bothers to thank you on here, 1000 folks are huge fans! Thanks again and cheers.

Answer 6 · 2022-05-16T00:14:21.000Z

@mattdonnelly (and @zntfdr), it's been an honour! I got to learn a lot about Swift and the Twitter API through this framework and am always glad to have been able to contribute to it in the time that I did.

Cheers!

Answer 7 · 2022-06-23T10:01:10.000Z

https://github.com/mironal/TwitterAPIKit
@mironal hi! i'm very happy to hear about this, please let me know how i can help with the repo.

Answer 8 · 2022-06-23T10:01:29.000Z

@mattdonnelly thank you

Answer 9 · 2022-06-23T10:05:33.000Z

The steps to deprecate this project have been completed and I'm going to leave this issue open for better visibility. Thanks for the words of support everyone!