Yess good Canadian 🇨🇦🇨🇦 app Very good concept
Amazing app just wish it had desktop site and more proxys or else it would be perfect for my use case
Trash
It’s complete garbage
Not worth it
Good concept but don’t worth it at all
Serious Compatibility Issue After Psylo 1.3.1 Update
Hi Psylo Team,
I’d like to report a serious compatibility issue I’ve experienced since updating from Psylo 1.3.0 to 1.3.1.
With version 1.3.0, I had very good compatibility with certain websites. However, immediately after updating to 1.3.1, I started experiencing significantly more account restrictions on some websites under otherwise similar usage conditions.
I noticed that 1.3.1 introduced several privacy-related changes, including disabling WebTransport and WebAuthn by default, as well as completely disabling DNS Prefetch.
I understand the privacy and IP-leak concerns behind these changes. However, I’m concerned that completely removing certain normal WebKit/Safari behaviors can make a Psylo environment behave noticeably differently from a regular Safari environment.
WebTransport and WebAuthn can at least be re-enabled through the Advanced settings. DNS Prefetch, however, appears to have been completely disabled without an option for the user to restore the previous behavior.
Would it be possible to add a per-Silo option such as:
Disable DNS Prefetch
so users can choose whether DNS Prefetch should be enabled or disabled, just like WebTransport and WebAuthn?
For users who prioritize maximum privacy protection, it could remain disabled by default. But users who need maximum website compatibility could choose to enable it and accept the associated privacy trade-off.
In my case, the difference between 1.3.0 and 1.3.1 has been substantial enough that I would strongly prefer the ability to reproduce the networking behavior of 1.3.0 as closely as possible.
I’m not claiming that DNS Prefetch alone is responsible for the account restrictions I’ve observed. However, because the issue appeared immediately after upgrading from 1.3.0 to 1.3.1, I believe having the ability to individually control these new restrictions would be extremely useful for compatibility testing and troubleshooting.
Additionally, would it be possible for the Psylo team to provide an official way for affected users to temporarily install or downgrade to version 1.3.0?
For example, if possible, you could provide a previous 1.3.0 build through TestFlight or another official installation method. This would allow us to directly compare 1.3.0 and 1.3.1 under the same conditions and determine whether the compatibility issue is specifically related to the changes introduced in 1.3.1.
Even if providing an older build is only temporary and intended for troubleshooting purposes, it would be extremely helpful.
Please consider adding a DNS Prefetch toggle in a future update and, if possible, providing access to the previous 1.3.0 build for compatibility testing.
I’d like to report a serious compatibility issue I’ve experienced since updating from Psylo 1.3.0 to 1.3.1.
With version 1.3.0, I had very good compatibility with certain websites. However, immediately after updating to 1.3.1, I started experiencing significantly more account restrictions on some websites under otherwise similar usage conditions.
I noticed that 1.3.1 introduced several privacy-related changes, including disabling WebTransport and WebAuthn by default, as well as completely disabling DNS Prefetch.
I understand the privacy and IP-leak concerns behind these changes. However, I’m concerned that completely removing certain normal WebKit/Safari behaviors can make a Psylo environment behave noticeably differently from a regular Safari environment.
WebTransport and WebAuthn can at least be re-enabled through the Advanced settings. DNS Prefetch, however, appears to have been completely disabled without an option for the user to restore the previous behavior.
Would it be possible to add a per-Silo option such as:
Disable DNS Prefetch
so users can choose whether DNS Prefetch should be enabled or disabled, just like WebTransport and WebAuthn?
For users who prioritize maximum privacy protection, it could remain disabled by default. But users who need maximum website compatibility could choose to enable it and accept the associated privacy trade-off.
In my case, the difference between 1.3.0 and 1.3.1 has been substantial enough that I would strongly prefer the ability to reproduce the networking behavior of 1.3.0 as closely as possible.
I’m not claiming that DNS Prefetch alone is responsible for the account restrictions I’ve observed. However, because the issue appeared immediately after upgrading from 1.3.0 to 1.3.1, I believe having the ability to individually control these new restrictions would be extremely useful for compatibility testing and troubleshooting.
Additionally, would it be possible for the Psylo team to provide an official way for affected users to temporarily install or downgrade to version 1.3.0?
For example, if possible, you could provide a previous 1.3.0 build through TestFlight or another official installation method. This would allow us to directly compare 1.3.0 and 1.3.1 under the same conditions and determine whether the compatibility issue is specifically related to the changes introduced in 1.3.1.
Even if providing an older build is only temporary and intended for troubleshooting purposes, it would be extremely helpful.
Please consider adding a DNS Prefetch toggle in a future update and, if possible, providing access to the previous 1.3.0 build for compatibility testing.
Show more
Expensive. Unethical developers.
I initially wrote a review giving it 3 stars because, despite the expensive price and annoying yellow block saying your subscription expired, you could still use the basic offline features (which don’t cost the devs any money) with your own proxy or none at all.
Days later they updated the app and completely blocked all basic features unless you pay $11/mo. There was no mention of this in the changelog. They basically tricked people into updating and took away 100% of the previously free features.
I’ll be deleting all of my comments on social media recommending this app for privacy, and I’ll mention that the developers are unethical and untrustworthy any time I see the app mentioned.
Days later they updated the app and completely blocked all basic features unless you pay $11/mo. There was no mention of this in the changelog. They basically tricked people into updating and took away 100% of the previously free features.
I’ll be deleting all of my comments on social media recommending this app for privacy, and I’ll mention that the developers are unethical and untrustworthy any time I see the app mentioned.
Show more
