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

Future plans for the extension 🚀 #119

Open
honsiorovskyi opened this issue Sep 22, 2023 · 3 comments
Open

Future plans for the extension 🚀 #119

honsiorovskyi opened this issue Sep 22, 2023 · 3 comments

Comments

@honsiorovskyi
Copy link
Owner

Hello everyone 👋

First of all, thank you for your your interest, support, bug reports and high ratings on AMO! It always means a lot an I really appreciate it.

Second of all, very sorry for disappearing for a long time, I didn't have enough time to properly maintain the project and thus also didn't want to engage in any discussions that would result in just empty plans and promises.

During this my time off, a couple of things have changed.

  • First, I almost completely forgot the codebase of the extension (:joy:), will have to remind myself what's there.
  • Second, some security issues that v2 was supposed to address got addressed by the browser itself, so now they're not relevant.
  • Third, I used both v1 and v2alpha of the extension, and there are some bugs and usability issues with v2 that I'd like to get rid of.
  • Fourth, all your feedback needs to be taken into account.

That being said, I wanted to share with you some plans regarding this extension. Currently I'm thinking of the following things:

  • stop working on v2 of the extension completely, instead
  • start a new branch (v3?), using v1 as a base — it provides the core functionality, it's battle-tested and works quite well
  • try to create some very minimal UI for it — something similar to v2alpha, but simlpified and hopefully with less bugs
  • at the same time I'm also thinking of keeping core functionality in one extension and creating another one for the UI part, just to keep it small and simple for those who don't need the UI — I'll try to evaluate both options and see which one will be less confusing/complicated
  • address the your feedback from the issues that have gathered during this time — please be patient, I'll try to address everything or provide some workaround, but I'm still short on capacity, so it will take some time
  • potentially use some very lightweight framework for the UI, because current code seems to be fast but kinda overcomplicated and hard to support

I hope it all makes sense for you, and I'm looking forward to making this extension better 🙂

Thank you and see you soon!

@honsiorovskyi honsiorovskyi pinned this issue Sep 22, 2023
@honsiorovskyi honsiorovskyi changed the title Future plans for the extension 🚀 🚀 Future plans for the extension Sep 22, 2023
@honsiorovskyi honsiorovskyi changed the title 🚀 Future plans for the extension Future plans for the extension 🚀 Sep 22, 2023
@rehanvdm
Copy link

No need to apologize, thank you very much for this project and the work you have done! Excited for what is ahead.

@Roy-Orbison
Copy link

Came here thinking I might fork and get it going again, then found a whole new version tucked away in the wings! I still rely on this awesome add-on, and look forward to version 3. Thanks.

@nitrocode
Copy link

nitrocode commented Oct 26, 2023

Thanks for all your work.

Please consider this too

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

4 participants