Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

[Announcement] Repository is being archived #22

Open
lucashuy opened this issue Mar 1, 2023 · 0 comments
Open

[Announcement] Repository is being archived #22

lucashuy opened this issue Mar 1, 2023 · 0 comments
Labels
documentation Relates to Github or code documentation

Comments

@lucashuy
Copy link
Owner

lucashuy commented Mar 1, 2023

Hi,

This repository is being archived and will be placed in read only mode. That means that new commits, updates, issues, and discussions will not be made anymore. The burntbot project was my first large scale project that was deployed for people to use, and I've learned so much from it. Unfortunately though, I will no longer be supporting this codebase.

Why the change to archive this repository?

Late 2022/early 2023, Shakepay began to experiment with protecting their API endpoints more actively, employing resources like Cloudflare's bot detection (kudos to them). This meant that new bot users trying to login, or those that needed to login again suddenly found themselves at Cloudflare's front door.

What does this mean for current bots?

Up until today (2023/02/28), current bots were fine and did not have any issues with any current features. However, Shakepay has invalidated all tokens, requiring users to login again

New authentication attempts through the bot were being blocked, resulting in no new tokens being issued. This effectively meant that conventional (ie. with the bot) means of logging in and authentication no longer worked.

Why not just work around it, or fix it?

I simply decided not to. Shakepay was gracious enough to allow this behaviour when the swapping started and even after it ended. Since Shakepay has made the choice to now protect their authentication endpoint from bots, I've decided to archive this repository to make it clear that I personally won't be open to making any changes to try to fight what they have done and instead will respect their choice.

Plus trying to fight bot protecting/detection is just a game of cat and mouse lol

What's next?

Since this repository is licensed under AGPL 3.0, anyone is free to download and modify the source code to their liking as long as the license requirements are met. This includes things like forking this project, modifying and sharing your fork.

@lucashuy lucashuy added the documentation Relates to Github or code documentation label Mar 1, 2023
@lucashuy lucashuy pinned this issue Mar 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Relates to Github or code documentation
Projects
None yet
Development

No branches or pull requests

1 participant