sigmoid.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A social space for people researching, working with, or just interested in AI!

Server stats:

587
active users

#ghostery

0 posts0 participants0 posts today

We don't track you. Don't care where you come from or where you go (or if you would have been married a long time ago).

You don't need blockers on our website. Always good to have them enabled but you should always see a "0" on any extensions like #Ghostery.

This is how the web should be. It was how it was. You see that "0" on #mastodon too which is why it's the best social media.

Roastinghouse.co.uk

Goodbye Chrome, Hello Ghostery Browser! A New Dawn In The Browser Wars!

This dream involved me testing the Mozilla Firefox web browser with the Ghostery Tracker & Ad Blocker web browser extension.

I also tested the Ghostery Privacy Browser web browser, which has built-in ad blocking.

https://www.youtube.com/watch?v=0yoU6j_IxlE

I tested them online against many advertisement (ad) filled websites, especially bootleg websites.

This was all done from my desktop computer using the Linux distribution (distro) Ubuntu LTS.

My goal was to compare the ad blocking abilities between both of them.

I wanted to see if there was a difference.

Was there a difference between using the Ghostery web browser extension and it being built into the web browser?

I also wanted to see if it was worth using instead of Brave Browser or Mozilla Firefox with Ghostery installed.

At some point, my computer crashed / froze.

I started to worry as I feared that a malicious ad or something had done this.

Then I wondered why I did this from my computer.

I questioned why I did not use a virtual machine or a live USB with Ubuntu instead.

I probably was not even using private mode.

Then I hoped that I was not a victim of a session hijacking attack.

I did not want all of my passwords, browser cookies, et cetera stolen / copied.

I woke up as I restarted my computer, hoping for the best.

The hope was that Linux, Ubuntu, would be more resistant if my fears were correct.

I also prepared for the worst while wondering why I did something so stupid.

The end,

  • John Jr

https://johnjronline.wordpress.com/2024/10/30/testing-mozilla-firefox-with-ghostery-ghostery-privacy-browser/

Bold statement in Apple's recent privacy ad that using Safari solves all tracking problems: youtube.com/watch?v=0HjDpPnxcP

One thing to mention is that Safari supports extensions; it is more limited than on Firefox, but it works. Ghostery also has a Safari extension for iOS:

apps.apple.com/us/app/ghostery

If you wonder why the app has little history (and only three reviews): two weeks ago, we moved the remaining Ghostery Inc parts to Ghostery GmbH. In the Apple store, it was surprising not possible to update the company. Thus, we had to create a new developer account and start from scratch. All Ghostery users that installed the app are now stuck on the old version and need to manually install the new one.

More details can be found in our blog post: ghostery.com/blog/adblocker-sa

Continued thread

Ikke at media-institusjoner bryr seg om at de gir bort trafikkdata og sporing til ørten forskjellig leverandører

ghostery.com/whotracksme/websi

men de kunne gjort litt arbeid for å hindre at openstreetmap ikke får unødvendig trafikk.

Ghosteryadressa.no | WhoTracks.MeExplore the tracking landscape of adressa.no on WhoTracks.Me, revealing the most common trackers like Schibsted Media Group and their impact on privacy

Ghostery 10 (Manifest V3) has just been released on Chrome.

That completes the Manifest V3 migration on all our supported Chromium platforms. Supporting MV3 was not easy: Ghostery 10 is a major rewrite, started around two years ago; except for the core of the adblocker engine, it is a complete new code base.

We are working hard on bringing back missing configuration options. Also, fixing the issues that have reported already when we released earlier on Opera and Edge.

If you run into a problem, our bug tracker is here:
* github.com/ghostery/ghostery-e

If an individual website is broken:
* github.com/ghostery/broken-pag

If you have a general question, you can also reach out to our support:
* ghostery.com/support

We plan to have more releases over the upcoming weeks and months. There is already a new release scheduled with some smaller fixes (10.3.5).

GitHubIssues · ghostery/ghostery-extensionGhostery Browser Extension for Firefox, Chrome, Opera, Edge and Safari - Issues · ghostery/ghostery-extension

Since the Manifest V2 phase-out in Chrome is near, my two-cents on how browsers rank in their API support for adblocker extensions:

Firefox >> Chrome > Safari

Firefox already had a slight edge before because of its DNS API (needed to prevent CNAME cloaking). Now with MV3, the gap is getting higher after replacing blocking webRequest API by the more limited Declarative Net Request.

Chrome and Safari are close, and it is a bit apples and oranges. I would still rank Chrome higher for writing a adblocker extensions, because it has less bugs and the limits for the blocklists are less restrictive.

Especially, the latter is currently a problem on iOS: it is hard to debug, but from trial-and-error we learned that it only works reliably up to a certain limit. Thus, we had to disable certain blocklists on iOS.

Another disadvantage of MV3 extension is that the adblocker rules can only be partly updated without extension releases. Though most rules that cause breakage are on the level of cosmetics and scriplets (both not handled by the DNR API), rules that block requests can only be updated quickly on Firefox now. For instance, Ghostery will check for updates every hour. Extension releases, on the other hand, are more involved; they require more testing, and also going through reviews and can take days. Perhaps this will get smoother in the future, but currently the ecosystem is not ready for frequent releases.

Most other browsers are forks from Chromium or Firefox. Whether Chromium-based browsers will be able to keep support for MV2, time will tell. Browsers are complex, and once Google removes the code, it could be difficult to maintain it. On the other hand, the Ghostery Browser is based on Firefox. Fortunately, Mozilla stated that they will not remove the API unless there is a proper (full-featured) replacement.

But don't get me wrong. Even though Firefox is the best platform for adblocker extensions, it does not mean that Chrome or Safari extensions are not providing value. They will lack certain functionality and its filters may be more outdated, but most blocking will still work.

Ghostery 10 is now in review on Chrome. It is the first version to support to Manifest V3, meeting Google's deadline of June 2024.

Background: we have already released Ghostery 10 on the extension stores of the other Chromium-based browsers
(Opera & Yandex in February and Edge two weeks ago).

A challenging aspect of Manifest V3 is to support the same level of customization as in Ghostery 8. Instead of handling everything inside our own adblocker engine, there are now two components:
1. request blocking requires to use the new Declarative Net Request API
2. the adblocker engine (implemented in the extension) still handles all non-blocking aspects (scriptlets and cosmetics like hiding blank parts of a website that was reserved for ads)

We are still working on bringing back more customization options, so expect to see improvements over the upcoming weeks and months.

What about Firefox? It continues to support blocking webRequest API; thus, you can still use the old API and let the adblocker engine handle the blocking. When we eventually roll out Ghostery 10 out on Firefox, it will share the same UI with Chrome, but its privacy protection will be more capable. For instance, a feature like Anti-Tracking that modifies requests by removing tracking parameters cannot be implemented with the DNR API.