eptcyka

This was never an issue with my Pixel. Using my pixel with graphene without google play services resulted in better battery life than stock.

Go makes signal handling harder. Further, there is no FFI call overhead in Rust, C++, Swift. It isn’t marshalling, a function with no args will still incur an overhead.

The whole point of signal is that they cannot provide you with your data - they do not store it.

Further, I have been frustrated with similar design decisions with Signal - but how can they ensure you can export your messages without allowing letter agencies to do the same? Falling back on platform security guarantees is a rather good choice in terms of the economics - Signal need not gatekeep access to their private data - it is android and iOS that do the heavy lifting there. I’d love to move my messages between devices and sims - but I understand why that is not feasible for now.

Calling C functions is not free, compilation becomes a lot more difficult, Go tooling is not as helpful. Signal handling is still a mess. It works in the happy path where the FFI is not on the hot path.

Go really sucks at calling into C code.

So far.

Not sure about iPads, but going from a pixel 3 to a pixel 5 made me feel like my pixel 3 was broken. Xr to 16 pro was similar, but that is because Xr was legit broken.

Would a Trump puppet not also be anti-NATO and pro-Putin?

Postmarket is very much not like any other aosp derivative.

Swift gas a facility for this type of thing, Rust could adopt it too.

I guess I should update my nextcloud.

No, scratch that. I should replace it with something that is not a trash fire.

Be a tech maximalist- use tech and will power to pull ahead with green energy. Go hard on batteries and energy storage. I do not even care that I may sound delusional - the contrary doomer viewpoint is deluded in a far worse manner. The things we need either are or are not within our abilities- you will never know unless you try. Resigning with *it’s too hard* ensures we will know that we cannot.

Don’t apologize for x, just don’t post x links.

Or use fido/gpg in a yubikey - the user gets to authenticate the use of the secret, but it never leaves the hardware token, let alone the client computer.

Zero hardware changes forced springboard teams hand here.