RecipeFilter VS thegreatsuspender

https://github.com/sean-public/RecipeFilter Chrome extension that focuses recipes front and center on food blogs - GitHub - sean-public/RecipeFilter: Chrome extension that focuses recipes front and center on food blogs

This is an open source project: https://github.com/sean-public/RecipeFilter

Recipefilter

There's also an extension for both Chrome and Firefox called Recipe Filter, which gives you a popup with just the recipe on those blog sites. Works pretty well.

I get loads of really kind emails and messages on a daily basis from the users. It's been really rewarding in that way. A couple ideas that people have put forth seem really reasonable, such as unit conversions, print-friendly pages, and automatic nutrition labels. In fact, I'd actually love those too as a cook!

One feature that would improve the recipe recognition and unlock lots of other features where it's found would be JSON-LD support. I'm seeing lots of recipe pages containing those handy, structured formats lately.

A comment about JSON-LD: https://github.com/sean-public/RecipeFilter/issues/22#issuec...

But all of these things stray from the fundamental simplicity of what it does. The code is just 92 lines of JS and works (or breaks!) transparently. If I started adding features, it would quickly become another complex system to maintain and I have plent of that at work ;)

Lots of good extensions in this thread.

Here are some optional extensions I like:

- Twemex - https://twemex.app/ - Adds a really useful sidebar to Twitter.

- Recipe Filter - https://github.com/sean-public/RecipeFilter - Focuses recipes front and center on food blogs

- Notion Boost - https://gourav.io/notion-boost - Adds a lot of really nice features to Notion

- Tampermonkey - https://www.tampermonkey.net/ - Lets you create your own JS customizations on web pages without needing to make a whole browser extension.

I really wish it was far easier for everyday people to make their own personal browser extension-like functionality and share it with others. Extending the apps we use feels really empowering and can help people transition from helpless consumers of apps to authors of how their computer works. Here's an essay I like detailing this view:

https://www.geoffreylitt.com/2019/07/29/browser-extensions.h...

And while I'm here I'd also like to plug a service I wrote that lets you easily add paid features to extensions you develop:

https://extensionpay.com

I made it to use myself but lots of developers have found it useful in monetizing their extensions without ads or selling user data. And even to my surprise, users are actually willing to pay for browser extensions! The service has made devs over $13k since I launched earlier this year!

I use Recipe Filter [chrome extension or if you prefer the github]

This is an open source project: https://github.com/sean-public/RecipeFilter

Happened in (2021)[https://github.com/greatsuspender/thegreatsuspender/issues/1...], and then a few others have forked the extension and tried to revive it, only to eventually sell to nefarious owners or sell user data themselves

I went to github and downloaded the last known "good version, installed it manually."

You want someone to die for disabling a potentially malicious extension that is unmantained since 2020?

Also if you want to read up on the removal of the app and the malware issues this post goes over it as well as other recovery options

Similar code projects have had issues like this before, like the open source Great Suspender.

What can happen after a project changes hands - https://github.com/greatsuspender/thegreatsuspender/issues/1263

Better link https://github.com/greatsuspender/thegreatsuspender/issues/1...

> TLDR: The old maintainer appears to have sold the extension to parties unknown, who have malicious intent to exploit the users of this extension in advertising fraud, tracking, and more. In v7.1.8 of the extension (published to the web store but NOT to GitHub), arbitrary code was executed from a remote server, which appeared to be used to commit a variety of tracking and fraud actions. After Microsoft removed it from Edge for malware, v7.1.9 was created without this code: that has been the code distributed by the web store since November, and it does not appear to load the compromised script. However, the malicious maintainer remains in control, however, and can introduce an update at any time. It further appears that, while v7.1.9 was what was listed on the store, those who had the hostile v7.1.8 installed did NOT automatically receive the malware-removing update, and continued running the hostile code until Google force-disabled the extension.

For what it is worth, you may have heard of the Great Suspender incident (https://github.com/greatsuspender/thegreatsuspender/issues/1263). It was used by millions, and was also open source on GitHub, but it could still end up becoming malicious.

Long ass comment: That is not true for the most part. While the increased amount of individuals working of an OSS project may lead to better vulnerability detection according to both parties of the closed-source/proprietary debate, it doesn't lead to a massively more secure software overall. Not all reviewers have the similar experience or expertise and, because of it, not everyone will be able to review, identify or patch any flaws or vulnerability of a specific software since it may require other skills beyond just basic programming skills such as network or cryptographic skills. [1] Some even suggested that the large number of users contributing to the project can lead people "into a false sense of security." [2] Overall, some papers conclude that being an open source software or a proprietary software isn't an important factor for security and suggest considering other factors, such as the particular vendor/maintainer that controls the entire process. [3] After all, what if the maintainer decides to sabotage their own code? What if the project was sold to another maintainer for its own shaddy needs?

If you're referring to The Great Suspender, that extension was bought by an advertising company earlier this year. I'm using the last good version (github) though.