Steps to reproduce

1. Start up Ulancher
2. Try a currency conversion or look up items on YouTube
3. E.g. curr 80 USD to EUR
4. Note the 'loading...' message

Current behaviour

I've Ulauncher on a couple of Linux machine (Ubuntu desktop - working, Pop OS laptop not working). I have the correct API keys, if I copy and paste the API key into a browser a bunch of currencies come up and everything is working, also desktop is working. I have the same setup on my laptop but the Ulauncher extensions don't work - I just get a Loading.... message as per screen shot

What could be the problem?

Expected behaviour

Extensions should work

Screenshots

https://i.imgur.com/NUfeZm2.png

Is your feature request related to a problem? Please describe

Described in Ulauncher/Ulauncher#471

Describe the solution you'd like

Solution may be similar to how packages are marked as out-of-date in AUR.

Some one can click on a link "Flag extension out-of-date" and then the extension won't show up in the list until developer pushes marks it as up-to-date

Also, the following questions / use-cases should be thought through

• How can a developer find out that an extension has been marked?
• How can a user provide more info for the developer about why the extension was marked?

Following extension doesn't have github repository:

https://ext.ulauncher.io/-/github-zeue-ulauncher-gcp

Steps to reproduce

1.Submit a new extension

Current behavior

When submiting a extension a 401 error is given.

Expected behavior

A extension should be submitted

Screenshots

A connection error occurs while trying to load the extension list on https://ext.ulauncher.io.

Here's the error copied from my browsers console:
Failed to load https://owd2rwb5be.execute-api.us-east-1.amazonaws.com/prod/extensions: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://ext.ulauncher.io' is therefore not allowed access. The response had HTTP status code 502. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Related to #6 #24 and #43, specifically for repos marked as archived ("archived": true, when you make a request to https://api.github.com/repos/user/repo)

A lot of extensions may work despite being archived, but it means they are not going to fix bugs or security issues and can't even receive pull requests.

For example brpaz/ulauncher-file-search is one of the top rated extensions, but it's been unmaintained for a long time and I think there are better file search extensions, such as hillaryychan/ulauncher-fzf. And each installation of imsakg/ulauncher-translator includes a 35mb gif of Richard Stallman. The repo is unmaintained with no way to contact about improvement suggestions to that.

People don't submit unmaintained extensions. They become unmainained, so it would have to be fetched later, like github stars.

I'm not sure how to display this. Maybe sorted at the bottom with a notice of some kind. Filtering them out completely should be avoided though imo. There could be cases where only one extension handles a certain thing, or if users want to find extensions they used in the past, or find extensions they can fork and maintain themselves.

The default sorting shows new extensions and there's a second one that sorts by github stars.
I think these are good to keep, but maybe adding a smarter one that combines factors to highlight both popular extensions and the well maintained ones.

For example, sorting by github stars, but adding a penalty for extensions based on how recent the latest commit was, if they have archived the repo, disabled the issue tracker etc.

(this is intentionally vague because I think it's hard to know what factors and how to weight them, until you sit down with it and try)

Blocked by Ulauncher/ext-api.ulauncher.io#5

Add a filter like this

User should be able to filter by a specific Extension API version.
All extensions should be displayed by default

Technical Details

• Filter should have the next options:
  ** All
  ** v1.0.0 (Ulauncher v4)
  ** v2.0.0 (Ulauncher v5)
• When a version is selected call API with version in query params (like this GET /extensions?version=1.0.0) in order to get a list of extensions
• version param should be either 1.0.0 or 2.0.0
• If user selected All, don't pass version in the request

There are so many extensions now. It would be nice to be able to use search and filter the extension list instead of using Ctrl+F in the browser.