Repository navigation
Branding guidance for a Firefox fork of uBlock Origin #4186
Unanswered
mekineer-com
asked this question in
Q&A
Replies: 1 comment
|
Perhaps it is best to NOT use either uBO or uBlock Origin in the branding for your fork. Otherwise, users may think that your fork is endorsed or supported by the uBO project – which it isn't. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
A Reddit moderator directed me here for guidance.
I’m privately testing Quer.ee, a Firefox MV2 fork that retains uBlock Origin’s blocking and adds local filtering of Google and Bing results for a noncommercial-web search project.
Before any public release, I want to make the relationship clear and respect the project’s branding preferences. The fork will remain GPLv3, preserve uBO attribution, provide matching source, use its own extension ID, and state that it is unofficial.
My current preference is:
Quer.ee
Search Filter & Content Blocker
Powered by uBlock Origin
Would the maintainers prefer different wording, placement, or branding? I had also considered “uBO+Q,” but will follow your preference.
All reactions