Avatar
Sabza
c1b9dc151e252ed1c20ad6ab6696922288d924806605a39c6d68790baa779937
UJesu UyiNkosi.

Body language alpha is real. If your CEO don’t sit like he’s guarding Satoshi’s cold wallet, I don’t want it.

nostr:nevent1qqsx4ns8wx9ukmtyvcxwwz52azlgrjrlxecf0k7fs0csv0ej4n24xlgppemhxue69uhkummn9ekx7mp0qgsp4lsvwn3aw7zwh2f6tcl6249xa6cpj2x3yuu6azaysvncdqywxmgrqsqqqqqp2ffa3h

I am building something on nostr. It is called NostrSafu.

Here is the problem. Scammers are showing up. Fake giveaways. Phishing links. People pretending to be someone else. And since zaps involve real money, it is getting worse.

So I am building a tool that helps us protect each other. No company. No middleman. Just real people looking out for each other.

NostrSafe will let anyone report scams or shady stuff they see. It will show warnings when something looks risky. It will help you know who to trust. And it will let you zap the people who help keep the network safe.

If someone saves you from a scam, you can zap them to say thank you.

It will also use simple AI to help catch bad stuff faster.

I will be vibe coding this. That means no big plan. Just me building from the heart every day and sharing progress here.

Everything will be public. No secrets. You will see it all as it happens.

This is for the people who believe in freedom. For the ones who are wide awake.

I will post updates right here on nostr.

Let us build something good.

#nostr #bitcoin #buildinpublic #privacy #vibecoding

I read this whole note. Nowhere does it mention what the role is… classified?

Good morning Uno. Have a great day.

Nostr Needs More Builders, Not Just Users

There’s a strange pattern in every protocol’s early days. First the curious arrive. Then the speculators. Then the sheep. But Nostr is different. It wasn’t built for the sheep — it was built by rebels for rebels. And now that we’re here, we can’t just consume. We must build.

Nostr is raw and beautiful. But it’s still too fragmented. Too many apps are built in silos, with no shared libraries, no open design principles, no collective documentation efforts. Most clients reinvent the wheel. That’s a waste of energy.

We don’t need a thousand different clients doing the same thing. We need tooling, infrastructure, and frameworks that others can build upon. We need developer bridges — not more walls.

If you can code, contribute.

If you can design, make it beautiful.

If you can write, document.

If you can test, break stuff and report it.

If you can organize, bring people together.

If you can dream, propose something wild.

This isn’t a playground. It’s a battlefield for sovereignty. Let’s stop waiting for perfection and start building the future — one repo, one pull request, one protocol extension at a time.

Build for the network. Build for each other.

#nostr #decentralization #sovereignty #opensource #buildinpublic

I don't post to go viral.

I post to signal alignment.

Code, faith, and freedom.

If you're about that too—

Let’s build something that outlives us.

#Nostr #Christian #Legacy #OpenSource #BitcoinBuilder

I don’t want ease.

I want truth.

Give me the raw signal. The ugly data.

The narrow path.

Let the sheep scroll reels.

I’ll build tools that set men free.

#FreedomTech #NostrDev #Whitehat #FaithInCode #Bitcoin

Bitcoin is more than money.

It’s time encoded with truth.

A shield against tyranny.

A quiet revolution happening in blocks, not bullets.

Opt out. Hold your keys.

Freedom doesn’t beg. It verifies.

#bitcoin #freedomtech #selfsovereignty #truthmachine #nostr

The old, gambling me, should've seen this quote back then…gambling almost ruined my life, at first I made a lot of money, and then little by little I lost it all… success" is an illusion in gambling…no such thing!

get involved, anon

Replying to Avatar Final

Our initial port to Android 16 has been completed and can be built for the emulator from our 16 branch. All of the device-independent #GrapheneOS code has been ported. There are some parts of the port which will be redone better and a lot of testing and fixing regressions to do.

Normally, we would have announced the availability experimental releases based on Android 16 already. Unfortunately, Android 16 dropped device/hardware support from the Android Open Source Project and we're going to need to put it together ourselves without being prepared for it.

We'll be starting from the Android 15 QPR2 device support code and stripping it down to a bare minimum. Pixel 9a is a special case and will be more work.

Our hardware-based USB-C port control feature will no longer work with this approach and we need to replace half of the code.

We received early notice of Android 16 removing the device support code from AOSP but were unable to confirm it or determine the details. We have existing automated tooling for this we can significantly extend to generate what we need. It will be difficult and a major regression.

Paying an ODM to make a Snapdragon device for us is increasingly appealing. We would have all the device support code we need, could build it with compiler-based hardening and would be able to harden a lot of the device's firmware. We could also make secure element applets.

We want to be building privacy and security features. We don't want to be wasting our efforts on adding device support and other basic functionality to AOSP. It appears the only way we're going to be able to do that is paying millions of dollars to an ODM to have a proper base.

As an example of what we would be able to do even with an entirely standard reference device, we could add hardware support for our duress PIN/password feature to the secure element so that successfully exploiting the OS could not bypass it. We could do a whole lot with firmware.

Pixels meeting our requirements is why many of them were and are being purchased. We've reported MANY vulnerabilities over the years which have been fixed for Android and Pixels. We've proposed hardware, firmware and many software level security enhancements they've adopted.

We would prefer not having to pay millions of dollars to have a phone produced for us. It's entirely doable but we would need to repeat it every few years. We'd rather work with an OEM with aligned goals and willing to provide first class GrapheneOS support to sell more devices.

Pixels have substantially benefited from meeting our requirements and having GrapheneOS available for them. We know there's a significant market for an OEM working with us to make a more secure device with hardware-based security features not available on Pixels or iPhones.

Yeah, this sounds rough. Google dropped support, so now you have to build it yourself. That takes time and energy you’d rather spend on real security work. Making your own phone or working with a good OEM makes sense, even if it costs a lot. People want what you're building.

First note.

I'm Sabza — Christian, whitehat hacker (sometimes), and freedom builder.

I love exposing scams, building truth-powered tools, and helping others live free.

Faith. Code. Sovereignty.

Let’s decentralize everything.

Hello, Nostr!

#nostr #newhere #introductions #bitcoin #freedom #faith #whitehat #zap