search

It is definitely not clear in the man pages that fd uses regular expression search as its default. That ought to be specified in the DESCRIPTION section of fd's man page.

What about create a design pattern directory with the most popular design patterns examples?
We can create some rules like: have to be an explanation about the design pattern, the structure and one real world example.
The directory can be:

(folder) Design Patterns
-- (folder) Abstract Factory
-- -- AbstractFactory.js
-- -- AbstractFactoryTest.js
-- -- REAME.md

I can send some :

At Jina, we build crazy fun things using Jina and one such example is the meme search.
Meme search allows you to upload a meme of your choice and renders many similar memes to your meme !.

If you are interested in getting your hands on coding with Jina and creating something, this is the issue for you.

Idea:
Create a Pet image classification!.

Currently when clicking an image from search resutls the pop-up includes the image at a fixed size.
I propose to either increase that scaling to a somewhat higher fixed value or factor in the original image size so that very small pictures do not become pixelated.

Currently the preview is too small in my opinion which forces me to visit the website.

Installed it, typed ctrl + space, and the application presented itself as expected. When I started typing in the query box, the dialog expanded and presented a black screen only, with what looked like a Google icon. Clearly not as expected.

After looking around I saw that cerebro had theme settings and since I use a dark theme, many things commonly have issues supporting it so I tried to change

Describe the feature you'd like to see added

Current the /search endpoint returns a HTML file to display the results. This works well for UI users, which might be the first use case of Whoogle. But it's hard for prog

Is your feature request related to a problem? Please describe.
There seems to be duplication of logic in the code for Cloud Plugins. This is an opportunity for us to streamline the codebase and refactor these classes. This issue stems from these comments in #2096.

Describe the solution you'd like