|
|
|
Dear Newsletter Subscriber,
|
You've noticed: Of course, our NewsShield feature update was an April Fool's joke and not meant seriously. 😉 Thanks to everyone who laughed with us! 🙏
|
Today's newsletter is no joke and we have very important information for Apple users in particular:
|
Workaround for Apple Captive WLAN dialog
|
With iOS 18.4 and macOS Sequoia 15.4, Apple has introduced a change that can lead to problems with the captive Wi-Fi dialog. This dialog is presented in eBlockerOS protected home networks when you connect to the WLAN. However, this dialog can not always be clicked away and then prevents a successful connection to the WLAN.
|
Additionally, we will release a bugfix with eBlockerOS 3.2 in May, which will fix the problem permanently and without a workaround.
|
eBlockerOS 4 Development Progress
|
The development of eBlockerOS 4, which also supports the Raspberry Pi 5, continues to make progress. We have completely redeveloped and automated the structure of the eBlockerOS images in order to be able to support future Linux versions faster and without major development work. At the same time, the image can now be generated much more easily for different target platforms (Raspi, VM, PC, ...) in order to significantly accelerate further development.
|
Currently, all eBlocker base components already work with the new image structure. However, there are still ongoing problems with one core component: The “Squid Proxy”. Unfortunately, the latest version of the proxy behaves differently than before and we are investigating the problem thoroughly. We hope to find a solution in April and then start an internal alpha test in May. Overall, we are confident that we will be able to release eBlockerOS 4 by mid-year if no further problems arise.
|
1GB RAM is no longer enough for eBlockerOS 4
|
eBlockerOS 4 will only support devices with at least 2 GB RAM. The old “white cubes” as well as Raspberry Pi with 1 GB can therefore no longer be used for the latest eBlockerOS version.
|
But don't panic: We will offer a simple migration option to switch to eBlockerOS 4. So wait until you dispose of your 1 GB device to transfer your previous settings. We will share a buying recommendation and detailed information on switching devices in good time via our newsletter.
|
Tip: Activate All Blockers (only from 2 GB RAM)
|
If you already have an eBlocker device with at least 2 GB RAM and activated eBlocker HTTPS, we have a tip for you from our supporter team:
|
Turn on all pattern blockers to enjoy an even more undisturbed browsing experience (with fewer cookie banners, trackers and video ads).
|
The blockers can be activated under Settings> Blockers> Pattern Tracking Blocker:
|
- With the additional activation of the Consent & Cookie Banner Blocker many standard cookie consent banners are blocked.
- The DuckDuckGo Tracker Radar Blocker can automatically block tracker services recognized as suspicious by the DuckDuckGo search engine.
- Additionally, you can activate the uBlock filter under Settings> Blocker> Video Ads & Content Blocker. This activates various content filters and can also suppress ads in videos on many sites.
Note: If you only have 1 GB or the “White Cube”, do not activate any other blockers, as there is not enough memory and problems are otherwise inevitable.
|
With eBlockerOS 4, the recommended blockers will become the eBlocker standard alongside our curated, daily updated filters. Thanks to the team for this great tip!
|
Boris, Christian and the entire eBlocker team
|
|
--
eBlocker Open Source UG (haftungsbeschränkt)
Hudtwalckertwiete 10
22299 Hamburg
Germany
|
office@eBlocker.org
www.eBlocker.org
|
Geschäftsführer/General Managers:
Dipl.-Math. Christian Bennefeld
|
Sitz/Registered office: Hamburg
Register: Amtsgericht Hamburg, HRB 160491
Steuernr./TaxID: 49 / 717 / 02295
|
|
|
|
|
|
|
