vantezzen / bangs-for-google

Automatically use DuckDuckGo for !Bangs, keeping Google for all other searches

Hi, I'm Bennett! I'm a software developer from Germany developing web-apps and other web-based projects. I open-source a lot of my software so you can see it here on GitHub .

🚀 Some interesting open-source projects I'm working on:

• Skip Silence (Source): A browser extension that skips silent parts of a video
• blymp.io (Source): Transfer files in your browser using Peer-to-peer technologies
• minimalpedia (Source): A minimalistic frontend for Wikipedia using React
• Cauldron.js: Run a Minecraft Server in your browser

🌍 Find me on the web:

• You can find my full portfolio on https://vantezzen.io/
• You can find me on Twitter

bangs-for-google's Issues

Does not work on edge

I have tried doing bang searches from the omnibar (my default search engine is Google) and on google.com. Both do not work.

Upgrade Online Extension Packages

Hello,

Thank you for the excellent project! In April 2023, PR #3 came in, allowing users to specify bangs anywhere in the URL. I love this change, but since the last Firefox extension update was in July 2020, and Chromium's was in November 2020, none of the extension's users are getting to reap the benefits!

Could you please either:

1. Upgrade both packages, or...
2. Give me instructions on how to compile the project?

If you want to keep these older versions as-is until V3, I'm happy to upload the half-finished version of extension myself and use it until you're ready.

Please let me know if you have any questions or concerns! Thanks! :)

Request for Input on Porting Bangs-For-Google Extension to Manifest V3

I am currently working on porting your version of Bangs-For-Google to the "new" manifest V3 (because version 2 will be / is already deprecated). That comes with its own complications. I really enjoyed using your extension. Because I am using your work as a base, I wanted to ask, how you would like me to proceed.

Facts about the almost-finished port:
Will support manifest V3 (necessary to be used now / in the future)
Will probably not be specific to Google (will generally only check omnibox and not redirect requests to Google, because of limitations from manifest V3, at least that's my current understanding of V3)

Therefore, I have at least two possible ways to proceed and wanted to ask for your approval for one because of your underlying work.
Way 1: I could fork your repository and open a pull request. (Don't know if this would be in your interest, because the name of the extension is "Bangs-For-Google" and exactly that Google part would be gone after that.)
Way 2: Still fork your repository, give all potential credits and link to your repository / your GH account, but release this extension under a new name, because the Google part isn't really a thing anymore.
I would greatly appreciate your input on this matter! Thanks again for creating this extension!