Skip to content
This repository has been archived by the owner on May 19, 2021. It is now read-only.

WARNING: This extension is DEPRECATED, no updates in over 2 years #98

Open
gtallen1187 opened this issue May 12, 2020 · 10 comments
Open

Comments

@gtallen1187
Copy link

While the features and functionality of this browser extension look awesome, the unfortunate reality is that this project is no longer maintained. The last update was on in Feb of 2018, over two years ago.

Posting this issue so that it sits at the top and potential new users can see this warning message right away.

@ax4
Copy link

ax4 commented Jun 16, 2020

Hi, @gtallen1187 Good point! However, I don't think it's deprecated, the source code of it runs stable, but it's just unmaintained from the commit history since Feb 2018 I guess.

Note that, there's some difference between deprecated and unmaintained. The former one is a state defined when the code owner no longer uses a function name or intentionally abandons a project then it could be called deprecated. But the later one is the state that a project received some bug reports but unable to update it.

So I would prefer to call it unmaintained, but the core feature it provides still runs stable.

I've been using github-awesome-autocomplete on Chrome extension for three years, and its core feature runs stable. Except that it has some overlapping issue after GitHub introduces its new frontend after 2019 I guess. I am not sure what's the other problem (I see some people report that it won't work in other browsers).

Maybe fork and modify the code would be a good consideration if you wish to use its awesome feature implementation. I am currently login back to this repo because I want to read the code to fix the UI overlapping issue.

Take care! 😉

@ax4
Copy link

ax4 commented Jun 16, 2020

#96 (comment)

#97 (comment)

Quote:

PR is welcome. on Sep 27, 2019 @Haroenv
We need to update .... on Jan 23, 2020 @rayrutjes

So I think it cannot be called deprecated. Rather it's just unmaintained but welcome pull requests and forks.

@Haroenv
Copy link

Haroenv commented Jun 16, 2020

That's definitely correct @ax4, it's true that we haven't had time to work on features for it, the chrome version definitely still works, and is used by many people. Anyone who feels like contributing will definitely be taken seriously, but we worked two years ago to make it stable in the long run.

@pixelastic
Copy link

Is the index still updated regularly?

I can't find my own repositories (tried with https://github.com/pixelastic/firost, https://github.com/pixelastic/aberlaas and https://github.com/pixelastic/norska)

@rayrutjes
Copy link
Member

Hi everyone,

Like Haroen said, unfortunately no one is currently maintaining the project.

As a result we might be officially deprecating it in the weeks to come so as to better manage user expectations.

If you know someone that would like to take over from where we stopped, let us know.

@pixelastic
Copy link

I might be interested in helping in keeping the index updated and running, depending on the complexity of the project, as it is a very valuable source of information

I'm not interested in maintaining the browser extensions, though.

@ax4
Copy link

ax4 commented Jun 29, 2020

I’m also interested in how much work it will take to maintain this project to a longer run. Let me know ☺️

@Boscop
Copy link

Boscop commented Apr 25, 2021

I just saw that the extension disappeared from Chrome, and when I checked, I saw this. Any idea why chrome says it violates the policy?

image

@Haroenv
Copy link

Haroenv commented Apr 26, 2021

It was removed from the chrome web store since we didn't update some metadata. Unfortunately we haven't had time to check exactly what's wrong, but you can definitely run the extension manually by downloading the source files here

@Boscop
Copy link

Boscop commented Apr 26, 2021

Maybe what's wrong is related to permissions that are asked but not used?
At least that seems to have caused the same warning for the module linker extension:
fiatjaf/module-linker#60 (comment)

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

6 participants