RiffBlock: protection should stay clear and precise
Following the 1.0 submission, I am working on clearer protection status, custom domain rules and small everyday tools. The next update is still in preparation.
An enabled switch does not explain whether Safari has actually applied a filter revision. RiffBlock is therefore gaining a protection check that brings together setup, applied rules and the latest local page evidence. Unknown status should remain visible and lead to the appropriate next action.
Custom rules and cleaner links
Custom advertising domains can be added locally. These rules work with Safari’s native filtering, with website exceptions taking precedence. Another small tool removes known tracking parameters from pasted links. It does not visit the destination or keep link history.
Less repeated background work
I have reduced repeated queries and injections in the Safari component. Stale responses are also discarded if protection changes during a request. YouTube work continues: an empty player container retains its normal layout while advertising is handled more selectively. The absence of a warning alone does not establish reliable long-term playback.
An optional extension with deliberate setup
An encrypted DNS profile is prepared for protection beyond Safari. Export installs nothing and does not report active protection. Activating it later in system settings also selects the DNS provider that processes requests. This is a separate setup with its own limits, not a VPN.
The update remains in development
The technical work is implemented and checked locally. I still want to review and refine the visual design before the next update. Real-device behaviour and longer video sessions also need further acceptance. The 1.1 patch notes will therefore remain a private draft for now; RiffBlock 1.0 is still described as submitted to Apple.
