New Update Osprey Browser Protection discussion and updates

Hello @Foulest
What determines why some engines have "Ignore blocking threshold" enabled by default?
Ignore blocking threshold
AlphaMountain Web Protection
KAD Anti-Scam List
OpenPhish List
Phishunt.io List
Red Flag Domains List
SecureFeed List
SinkingYachts List
THREATfox List
URLhaus List
URLQuery List
Validin List
 
Last edited:
Check out the new website for Osprey: Osprey: Browser Protection
Let me know your thoughts!
The website looks great.
Only the partner logos in black are not so visible with the current background:
1784142527792.png
Maybe add a direct link to the latest changelogs on GitHub?
 
The website looks great.
Only the partner logos in black are not so visible with the current background:
View attachment 298837
Maybe add a direct link to the latest changelogs on GitHub?
Done and done. Partner logos are more visible, and a changelog button has been added. Also, a light/dark mode toggle was added. 😙
 
Check out the new website for Osprey: Osprey: Browser Protection
Let me know your thoughts!
It looks clean, modern, and easy to navigate.

Well done @Foulest.

Keep up the good work.

My main concerns are the project not having any other developers / organizations (EFF, et cetera) / companies / whoever to keep it going if something happens to you et cetera.

And I think that you should have a beta version / beta testers where the testing is done before it goes to the final stable version.

Other than that, the only thing left to make it the ultimate all-in-one security extension would be to add / fork uBlock Origin Lite into it or Brave Browser's Shields.

Keep up the good work.
 
It looks clean, modern, and easy to navigate.

Well done @Foulest.

Keep up the good work.

My main concerns are the project not having any other developers / organizations (EFF, et cetera) / companies / whoever to keep it going if something happens to you et cetera.

And I think that you should have a beta version / beta testers where the testing is done before it goes to the final stable version.

Other than that, the only thing left to make it the ultimate all-in-one security extension would be to add / fork uBlock Origin Lite into it or Brave Browser's Shields.

Keep up the good work.
Hi John,

Forking would require massive ruleset injectons on every page (what uBo does), which complete ruins the lean design of Osprey. When functionality is so different (Osprey preventing you to navigate TO risky website pages and uBo removing/hiding content ON pages) there is no architectural or performance gain in combining them.

Regards

Kees1958
 
Last edited:
  • Like
Reactions: ErzCrz and Back3
Hi John,

Forking would require massive ruleset injectons on every page (what uBo does), which complete ruin the lean design of Osprey. When functionality is so different (Osprey preventing you to navigate TO risky website pages and uBo removing/hiding content ON pages) there is no architectural or performance gain in combining them.

Regards

Kees1958
Yeah, I was just wishful thinking.

The first two things were my real suggestions. ;)
 
It looks clean, modern, and easy to navigate.

Well done @Foulest.

Keep up the good work.

My main concerns are the project not having any other developers / organizations (EFF, et cetera) / companies / whoever to keep it going if something happens to you et cetera.

And I think that you should have a beta version / beta testers where the testing is done before it goes to the final stable version.

Other than that, the only thing left to make it the ultimate all-in-one security extension would be to add / fork uBlock Origin Lite into it or Brave Browser's Shields.

Keep up the good work.
Thanks for the kind words. I'm not worried about not having any other developers. It's an open-source project. If "something happens to me", which could also happen to the uBlock Origin developer, someone will either fork it, or no one will care, and it wasn't deserving of a fork anyhow. In my experience, having multiple developers complicates things if there isn't a project manager present.

As far as having beta versions, Firefox is basically my beta, as they get updates pushed within 10 minutes of me uploading it. I test everything pretty thoroughly, and the proxy server allows me to be very nimble in terms of managing a bad provider.

I won't be roping in an ad-blocker. Different product category entirely. One of Osprey's benefits is that it can't see what's on the pages you visit, so there's no way for it to covertly monitor the content that's on your banking pages, for example. Osprey is compatible with almost anything! :)
 
Thanks for the kind words. I'm not worried about not having any other developers. It's an open-source project. If "something happens to me", which could also happen to the uBlock Origin developer, someone will either fork it, or no one will care, and it wasn't deserving of a fork anyhow. In my experience, having multiple developers complicates things if there isn't a project manager present.

As far as having beta versions, Firefox is basically my beta, as they get updates pushed within 10 minutes of me uploading it. I test everything pretty thoroughly, and the proxy server allows me to be very nimble in terms of managing a bad provider.

I won't be roping in an ad-blocker. Different product category entirely. One of Osprey's benefits is that it can't see what's on the pages you visit, so there's no way for it to covertly monitor the content that's on your banking pages, for example. Osprey is compatible with almost anything! :)
You are welcome.

I disagree, I think some projects that were abandoned were worth continuing.

Like ClamTK, since there is no other working option in the Ubuntu App Center for those who want a free and open source antivirus scanner with a GUI.

I do agree that some / maybe many were not necessary.

That is also my concern with uBlock Origin, like when the original uBlock was abandoned, fortunately Gorhill continued on with uBlock Origin, for now.

I have seen too many projects die, when the sole developer has decided to quit / retire / et cetera.

Especially free and open source projects, which are my favorite.

When possible there should never be one point of failure.

Having others to continue a project is important I think.

It is a shame that a group like the EFF is wasting their time on Privacy Badger when it would be better for them to support uBlock Origin / uBlock Origin Lite and Osprey Browser Protection, in my opinion.

This is a bigger issue for me because I am often helping people and recommending various free things to help them, whether at my public library IT job, or people I help for free outside of work.

When projects die / get abandoned, those people will be left with nothing, unless they notice and return for another free alternative.

Which is not likely, because most people I help do not even pay attention or notice, usually.

As far as beta testing, I think that it would be wise to test the providers, a few beta testers would not hurt.

Then you will not have to keep adding and removing so many providers if they were to be tested beforehand.

But it is cool that you have your own ways to respond to things quickly.
 
You are welcome.

I disagree, I think some projects that were abandoned were worth continuing.

Like ClamTK, since there is no other working option in the Ubuntu App Center for those who want a free and open source antivirus scanner with a GUI.

I do agree that some / maybe many were not necessary.

That is also my concern with uBlock Origin, like when the original uBlock was abandoned, fortunately Gorhill continued on with uBlock Origin, for now.

I have seen too many projects die, when the sole developer has decided to quit / retire / et cetera.

Especially free and open source projects, which are my favorite.

When possible there should never be one point of failure.

Having others to continue a project is important I think.

It is a shame that a group like the EFF is wasting their time on Privacy Badger when it would be better for them to support uBlock Origin / uBlock Origin Lite and Osprey Browser Protection, in my opinion.

This is a bigger issue for me because I am often helping people and recommending various free things to help them, whether at my public library IT job, or people I help for free outside of work.

When projects die / get abandoned, those people will be left with nothing, unless they notice and return for another free alternative.

Which is not likely, because most people I help do not even pay attention or notice, usually.

As far as beta testing, I think that it would be wise to test the providers, a few beta testers would not hurt.

Then you will not have to keep adding and removing so many providers if they were to be tested beforehand.

But it is cool that you have your own ways to respond to things quickly.
The only thing constant in life is change, my friend. I'll be keeping Osprey up and running as long as I can. It only costs me like, $10/month. Unless I die, get kidnapped, or drafted into war, you don't have to worry. Even massive companies regularly discontinue products and services from time to time.
 
The only thing constant in life is change, my friend. I'll be keeping Osprey up and running as long as I can. It only costs me like, $10/month. Unless I die, get kidnapped, or drafted into war, you don't have to worry. Even massive companies regularly discontinue products and services from time to time.
That is good to know, and I am glad that it is not costing you too much in money.

While these big companies do abandon products, especially Google and Microsoft, at least I know that they usually have another to replace it and a team to continue on future projects.

Instead of nothing at all.

The free and open source world has even more graveyards of products with nothing to replace them by those developers.

So unfortunately, it hits differently.

I prefer balance, so as things change, there are less issues. ;)

Having a minimum of plan A, B, and C / being able to survive at least three points of failure when possible. ;)

The people I help usually do not like change and can not handle it usually, which makes it worse.