Pardon the pun

I've been using GrapheneOS since day 1, because I was using CopperheadOS for several years until the point that Daniel Micay burned the signing keys.

So I don't need to make any switch. I have a Google Pixel 8. And I'll keep using GrapheneOS for the time being.

But I have moods. Sometimes I get really paranoid about Google and Intel processors (more than other companies). I was really paranoid about Google at the time when I made the post. I thought "what if the explanations for why it only works on Google hardware are a lie?" I thought "Anybody can make explanations, they might not be true!"

Turns out you can lock the bootloader on LOTS of hardware that is not Google hardware. And the long list of features that MUST be on the phone to be supported are really not all necessary IMHO for the phone to be plenty secure. So call me a skeptic, but I'm still just not sure, and I don't have the time to dig into it.

Also Daniel Micay seems to be clinically paranoid and accusatory of all kinds of harrassment he doesn't actually receive, and that instability itself is kinda worrying. I like my developers to be paranoid, but not to the level that they can't function with other people. Before even CopperheadOS he was sort-of run off from the Rust community for making drama. They say he stepped down, but he's still the guy producing most of the commits. I hope he gets and stays well, but should I trust the OS? I dunno. I'm trusting it because I don't have a better option (I could read the source, compile myself, compare to AOSP and LineageOS and other AOSP projects, but that would take a year).

I shouldn't have gotten so upset when people pointed me to the FAQ. I asked "Why does GrapheneOS run only on Google Pixel phones?" in my original post and people pointed out that the FAQ answers that question. That is fair enough I guess. I should mark rhetorical questions as rhetorical somehow next time so people don't miss point.

> "Many other devices are supported by GrapheneOS at a source level, and it can be built for them without modifications to the existing GrapheneOS source tree."

Now that is on point. I don't recall reading that part. So I guess your assucation "Maybe you didn't read them" wasn't entirely untrue.

As for Micay stepping down, I'm reading that he was harassed and SWATted. That is not cool. He's got odd social skills but for fucks sake. I feel bad for him.

75% of the annual population increase in the UK each year since COVID has been migrants.

Domestic births are very very low. And historically seems it may have been a catalyst for the management in charge to want to usher in a new revised cattle tax base.

Go pitch your idea. I'll start development when the transaction settles.

Cause I don't care, and I don't wanna talk to lightning retards.

I can. Pay me. Fund the servers and equipment.

Raise the funds first, then ask. Need enough Filecoin for IPFS to be viable. Need more crypto for development. Jack's $1M already dried up.

Raise the funds first, then ask. Need enough Filecoin for IPFS to be viable. Need more crypto for development. Jack's $1M already dried up.

It's not possible because you will not pay for it.

I feel like cloudflare has positioned themselves in a way that makes the pros outweigh the cons. Cons that they created ofcourse

Nostr is already decentralized, so no need for CDN or like IPFS. Now, a way to organize and publish nodes, maybe.

As for DNS issues, lokinet and ENS are options. DNS registry is a bit of a pain in general.

Nostr is already decentralized, so no need for CDN or like IPFS. Now, a way to organize and publish nodes, maybe.

As for DNS issues, lokinet and ENS are options. DNS registry is a bit of a pain in general.

How is a CDN gonna work over Tor?

Just for my own knowledge or awareness, why is Cloudflare the worst or bad? 0.0

Using DNS is retarded for a censorship resistant network

This will be complicated to explain, but I will try.

One stop shop for a new user being onboarded. For people who do not have access to our typical custodial wallets (WoS, Primal).

The solution needs to be able to seamlessly receive and send zaps. Meaning immediate Lightning address, and easy to zap through an app or NWC.