Avatar
PaddleManJoe
181f334d46f8ec615ff12c0c987055ae8dc003a18967205baeeb27d41fe7d9f3
Just a meathead trying to figure out this Freedom tech thing. I occasionally post whitewater kayaking footage from my archive.
Replying to Avatar Willy Cooper

The proliferation of firearms throughout the united states is why I am bullish for freedom ultimately. There is a limit to how far the population can be pushed.

Replying to Avatar Yogthos

Setup your lighting wallet! So that we can zap you!

There more I look around..... It feels like we are being ruled by the NICE people.

RHR has not been posted on the RSS feed. Where is RHR? I demand RHR.

I would give you some SATs, but you still don't have your lighting wallet set up.

And this talk about money pooring into ETFs, but BTC price just keeps crabbin. Makes me suspect the ETF funds have been stacking this whole time, or they are crazy leveraged.

I am disappointed that Trump is the best we could pick to challenge Biden. I might vote for him I guess. I am curious if this will increase disillusionment with the state. Bearish on federal power.

Replying to Avatar Guy Swann

When my meager Bitcoin stack shoots to the moon I will use it to build a citadel of stone in the mountains of the Pacific Northwest. My children and my children's children will dwell in it for 1000 years. It will shrug off fire, it will stand above flood, marauding gangs will break upon its walls.

Have you ever wondered why #GrapheneOS has a separate PDF viewer?

Well that answer is pretty obvious, it is more secure to have a separate hardened, sandboxed utility designed for that instead of sharing such a responsibility with a much larger app with greater attack surface like a web browser or office suite. It is trivial for some threat actors to deliver weaponized, malicious PDF files to their targets.

If we know all of this, the next step for some may be to wonder "Why is the GrapheneOS PDF viewer secure?", for you, I will explain some of the most important details:

The GrapheneOS PDF Viewer app requires absolutely no user-facing permissions to run, it doesn't ask for any, nor does it need them. Without permissions the app is completely contained in the Android app sandbox and the security access model is far greater.

How the viewer opens a file is through making a false request to Localhost from the WebView and then intercepting that request with a stream of the PDF data. The benefits to this include:

1. We don't needing files access in the WebView (both setAllowFileAccess and setAllowContentAccess are set to false).

2. Allowing us to intercept headers into the request like CSP, Permissions Policy for hardening the sandboxing done via the WebView With CSP, all dynamic and inline CSS and JS is disabled. The only scripts loaded are those used for the viewer itself.

3. In addition to using WebView for PDF Viewer, Vanadium takes the place for the WebView on GrapheneOS, meaning GrapheneOS users take advantage of the exploit protections used in Vanadium.

Even with all of this, the PDF Viewer still has a fair amount of room for improvement when it comes to quality of life features and usability enhancements.

If we zap your account does that support the #GrapheneOS project?

I have been using Alby. Would like something else at some point though.