You weren't toldn to blindly trust the hardware. Using GrapheneOS is advised because the hardware can't be trusted.

The guidance given was stating that regardless of a device having 'kill switches' you still have to trust the hardware.

Specifically regards the Pinephone for example.

You cannot avoid trusting the hardware manufacturer for the SoC, the overall device and other trusted components.

Pinephone uses components with serious security issues and doesn't configure the SoC securely. They can't provide the standard expected security updates and the device is missing most hardware-based security features like those depending on a secure element and verified boot.

Hardware kill switches don't make up for having lots of security issues in hardware, firmware and especially software. Using an OS with nearly non-existent application security model, lack of modern exploit mitigations, lack of memory safe language adoption, etc. is not progress.

Android Open Source Project is a Linux distribution, as is GrapheneOS. A substantial portion of our work is on the Linux kernel. We've made significant upstream contributions to the Linux kernel project with the bugs we've found, patches we've provided and code review.

An operating system doesn't need to use systemd, glibc, gcc/binutils, pipewire/pulseaudio, Wayland/X11, GNOME/KDE, etc. to be Linux. Linux is a kernel.

The radios and other peripheral components included in the devices we support are isolated. The common claim that cellular radios aren't isolated is completely false. What sets GrapheneOS apart is that regardless of any 'backdoors' (hypothetical until proven otherwise) is that, like RCE exploits similar to those recently discovered/patched by Googles Project Zero in the baseband, actors will still need to have an OS based exploit on top to compromise your data etc. No other OS provides the level of protection that GrapheneOS offers.

No external actor has ever claimed to have compromised a GrapheneOS Pixel. This includes third party state affiliated operators such as Cellebrite. They however are focusing a lot on older generation Qualcomm based Pixels and may have something in the next 12-18 months. Which is again why we advise uaing a modern OEM hardware firmware/driver supported device. The likes of which Pine/Libre are not.

Any questions? Apps have gotten a bit tricky due to rate limits, aurora store and obtanium will help, youll need to look at the workaround steps for opening google play links from your browser in aurora store.

It is! You can pay with Lightning or even Strike 😄

It's Shopify’s theme that makes the option a little tricky to find. It's right under the credit card option. Let me know if you can't find it!

Hey I'm not a fan of rap music. But it's sounds good 👍

P2P 🌽 🤫

?raw=1

I’ve had it happen where mempool fees just happened to spike as the transaction was being broadcast… and it took a couple days to actually get confirmed. Just unlucky bad timing. I’ve always just waited it out.

This is the scenario where you could try replace-by-fee but it’s not something I can talk about from experience. You’d have to read up on it to see if that’s something you want to do. Sparrow is capable of it. I believe it will require you have more (equal amount) of funds available to replace the transaction currently in mempool.

Ok, so you paid 13 sats/vb. Right now fees are ~22sats for low priority, ~25sats for medium, ~30sats for high.

As long as those numbers are above 13, you’re going to be in mempool queue.

A logo that integrates the Kiwi bird with multiple speech balloons. A very minimal option.

Once claimed, the badge should appear on your profile page.

Click on the "awarded" tab and you should be able to claim the badge.

Yep, all set. Go to badges.page and login with your public key to claim it.

How do we get rid of the live shit on amethyst from showing up?

This ain't FB. I don't care who's live.