LinkOff – LinkedIn Filter and Customizer ?
LinkOff cleans and customizes LinkedIn. It filters out the junk, leaving behind the posts and page elements that you want to see.
Make your LinkedIn experience better, instantly! With fewer distractions and better filtered content your sales, lead generation and networking will be a smoother and more enjoyable experience.
No more seeing unwanted likes and comments by your connections. Block the feed or filter it using custom keywords and find the connections and posts you want more easily. Job seeking? Advanced job filtering coming soon. While you are waiting, clean up your inbox – it can do it!
Also available on Firefox. Coming soon to Opera and other browsers.
⭐️ Option to hide the whole feed
⭐️ Post filtering by content (polls, videos, promoted, shared, etc)
⭐️ Hide posts by companies or specific people
⭐️ Filter by custom keywords (politics, coronavirus, vaccination, Noah Jelich, whatever)
⭐️ Hide posts shown due to interactions (comments, reactions, followed by connections)
⭐️ Hide irrelevant old posts (older than an hour, day, week, month)
⭐️ Select messages for mass deletion (clean your inbox)
⭐️ MESSAGE FILTERS COMING SOON
⭐️ JOB FILTERING COMING SOON
⭐️ Block ads on LinkedIn (banners, and sidebar)
⭐️ Hide LinkedIn learning and course recommendations
⭐️ Hide community panel and follow recommendations
⭐️ Stop LinkedIn premium upsell pestering
⭐️ Toggle-able dark mode
⭐️ Fully configurable to suit your need!
⭐️ Completely FREE and with NO ADS
⭐️ Made with ❤️ by Noah Jelich
? Frequently Asked Questions
⭐️ Are you going to make a Tampermonkey/Greasemonkey script?
Unfortunately, no. I do not have time to maintain any more code
⭐️ What about Vivaldi/Brave/Edge/Opera and other browsers?
The extension can be natively installed on all chromium browsers
⭐️ What about Safari and MacOs?
The store charges 100$ per year to post apps, which I cannot afford
⭐️ How can I use this on mobile?
Since neither Chrome or Firefox allow for extensions in mobile browsers, you need to install a chromium distribution that does. I recommend Kiwi Browser (if you have any issues, please report them, still testing mobile support)
Please create an issue before submitting a pull request.
Use npm to install dependencies, simply run
npm i. To rebuild the CSS from SCSS run
npm run css-build.
To install the extension locally follow the instructions below for your browser.
- Type about:debugging in the Firefox URL bar and press enter.
- Click This Firefox on the left, and then Load Temporary Add-on… in the middle
- Navigate to the location of the folder you unzipped, select the manifest.json file inside.
- Type chrome://extensions in the Chrome URL bar and press enter.
- Enable developer mode using the toggle on the right
- Click Load Unpacked on the left side of the screen.
- Navigate to the location of the folder you unzipped, and select it.
Commit message format
Each commit message consists of a header, a body, and a footer.
<header> <BLANK LINE> <body> <BLANK LINE> <footer>
<header> format should be as follows:
<type>(<scope>): <short summary> │ │ │ │ │ └─⫸ Summary in present tense. Not capitalized. No period at the end. │ │ │ └─⫸ Commit Scope: common|home|feed|messages|jobs|misc... or empty │ └─⫸ Commit Type: feat|fix|perf
If the commit reverts a previous commit, it should begin with
revert: , followed by the header of the reverted commit. In the body it should say:
This reverts commit <hash>., where the hash is the SHA of the commit being reverted.
If the prefix is
perf, it will appear in the changelog. However if there is any BREAKING CHANGE, the commit will always appear in the changelog.
The subject contains succinct description of the change:
- use the imperative, present tense: “change” not “changed” nor “changes”
- don’t capitalize first letter
- no dot (.) at the end
Just as in the subject, use the imperative, present tense: “change” not “changed” nor “changes”.
The body should include the motivation for the change and contrast this with previous behavior.
The footer should contain any information about Breaking Changes and is also the place to
reference GitHub issues that this commit Closes.
Breaking Changes should start with the word
BREAKING CHANGE: with a space or two newlines. The rest of the commit message is then used for this.