How to manufacture a phone in 7 steps: 1- Call a Chinese phone manufacturer. 2- Give them the specs, design, quantity. 3- They give you a price. 4- You start a kickstarter. 5- You pay the manufacturer. 7- They deliver the phones. *But someone needs to make the OS. 🤣

Then add Amethyst, The Nostr Browser, Zap.store, and more.

and support Samsung users !

Samsungs are hard to install custom software on, Pixels are much better.

Yeah, I was looking at that and Pixels suck with Camera and Battery life compared to S amsung S-class phones. Not worth it lol

Been thinking this since getting my Rabbit r1.

Like this 👇

I would buy an amethyst device. What all day with an on-chain wallet too

ESP32 Lilygo T-Deck with LoRa relays

LILYGO®

T-Deck

T-Deck is a pocket-sized gadget with a 2.8-inch, 320 x 240 pixel IPS LCD display, a mini keyboard, and an ESP32 dual-core processor. While it's not...

Build on the Pinephone running Mobian.

bootstrapped with shitposts.

you can run linux on that :)

android custom rom projects work well, look at CorvusOS, amazim experience.

removable battery

Can we name the operating system so it shakes up the convention, just have OS in the middle - nOStr

Take a good Graphene phone, and close off all access to the underlying system like Apple.

Ha, very nice one! First determine if GSM is a necesscity to control. If yes: good luck. Is Qualcomm in the deal? Nice if yes. If no: possible. Then go back to NIP-01 and the Nokia 3310. Contacts are npubs you saved, nothing else. I‘ve got a Firefox phone lying around for which I wrote apps in JS. I‘d start there. Alternative: Create a proprietary iPhone and Android app called NIP-01 or „NIP Phone“ and do everything on the existing infrastructure. Considerations: Are LoraWAN and HAM networks a valid entry point to the internet? Mesh-routed calls? Complicated.

wouldnt reinvent the wheel. Would probably fork graphene and load it up with nostr apps and @Zapstore

Hello, Rabbit r1 noting; Creating a mobile device solely dedicated to the nostr protocol would involve designing hardware and software tailored specifically for nostr interactions. The device would likely have optimized features for nostr features, such as seamless wallet integration, enhanced sharing capabilities, and possibly specialized interfaces for different services. Additionally, privacy and security measures would be crucial considerations given the nature of nostr usage. Such a device would offer a very unique user experience focused on nostr. To accomplish this, you would need a a team with deep understanding of operating system development, software engineering, hardware compatibility, and user interface design. Additionally, you would require access to specialized tools, resources, and expertise in mobile device development. Overall, the complexity of such a project would be substantial, requiring significant time, effort, and technical knowledge to successfully create a functional phone running solely on the Nostr protocol. If you have any other questions on this topic n please feel free to ask in a reply.

I'd rather have a freedom phone, where I can use nostr if I want to

I give you the name : noPhone :-)

And a preorder for 1 :-)

First principle thinking

Yes and no. I made one in 2014. Making is easy. Keeping it up to date is hard.

🔒📱 Imagine having a cell phone where you are in full control of your privacy and security! Discover the Nostr-only phone, a revolutionary device dedicated to the Nostr protocol. Discover how this innovation can transform your mobile experience. 👉 Read now:

Nostr-Only Phone

The Decentralized Future in the Palm of Your Hand

Bitcoin phone with nostr OS

^^ This ^^

Why fork Graphene? Just install the nostr apps lol

RISC-V open hardware, mesh-connectivity for telco independence integrated, native Tor implementation, and of course the node on the phone.

Nostr/Meshtastic Bridge

GitHub

GitHub - geoffwhittington/meshtastic-bridge

Contribute to geoffwhittington/meshtastic-bridge development by creating an account on GitHub.

GitHub

GitHub - QuixoteSystems/nostrastic: Bridge to publish Nostr posts and send/receive DMs over LoRa using Meshtastic

Bridge to publish Nostr posts and send/receive DMs over LoRa using Meshtastic - QuixoteSystems/nostrastic

SSB over LoRa

GitHub

GitHub - ssbc/tinySSB: tinySSB is "Secure Scuttlebutt over LoRa and BLE"

tinySSB is "Secure Scuttlebutt over LoRa and BLE". Contribute to ssbc/tinySSB development by creating an account on GitHub.

Voice over SSB over LoRa

GitHub

GitHub - tschudin/vossbol: Voice over SSB over LoRa

Voice over SSB over LoRa. Contribute to tschudin/vossbol development by creating an account on GitHub.

Has anyone else looked into running a web browser on top of Nostr? It should be possible to embed html inside of notes, and to extract and then display the html properly from there. Biggest difficulty I've identified is that it would require forking http, and that may be too much.

Because you'd already have a highly secure base with no centralized app store (Google) built in by default. What would make it a "nostr phone" a "nostr phone"? I guess thats the question. I imagine, - built in nostr onboarding and key creation for new users - System level "Sign in" for exsisting users (this store your key locally in some kind of system-wide Amber/local nsec bunker type funtionality) - Nostr-centric app store like @Zapstore to install your apps (you already have your key stored locally so you wouldn't even have to sign in to see your web of trust) - Contacts Intergrared with nostr, similar to Mutiny - A selection of daily use apps added out the box, ideally most that rely or intergrate with nostr Of course, you'll always be able to just install the apps, but I guess this would be an expereience taylored to work really well out of the box, using as much cutting edge nostr stuff as possible at the system level.

self destruct system in place as well.

Aside from just preloading Nostr apps. . . - Texts should work like this: Go through Nostr dms if there key is saved to contacts. Rcs, sms/MMS otherwise (exceptions should be allowed on a per contact or conversation basis) - contacts app should have a native way of saving a npub right alongside name, phone, and email - secure element for handling Nostr & Bitcoin keys - physical switches for cameras, microphones, and radios. - should be serviceable (even upgradable?) with a commonly found screen and replaceable battery. -needs to function as a phone. And have a standard browser.