What if building nostr apps took a few lines of code ? As easy as it was to build a website back in the day.

A new browser for interoperable apps without legacy web baggage. Built in bitcoin wallet, local relay, signer, outbox, for all apps.

Offline first, Cross-app coordination via the local relay.

This is gonna be wild nostr:note18aqhwwl6pcqpdupnzkq9gfz89pj30tpu6x3zgxct4s0x4arawzgs07cxc8

Reply to this note

Please Login to reply.

Discussion

How would a local relay work? What’s the use? Other users wouldn’t see the posts, unless it’s just a backup or smth?

Gets synced with negentropy when you come back online, but everything works by default

pretty sick

Another use case is private LANs. I know some remote farms that might benefit from this.

Okay. I'm turned on. When is this lady going to pop out of a cake?

did you see beaker browser? it was a p2p browser based on the dat protocol. ironically I think the dev is working on bsky these days.

anyway I love this idea. thanks for planting the seed, I’m gonna marinate on this one.

isn’t dat meant for data sets

We will replace legacy internet?

The new web…. Nostr

Beaker Browser but do it right this time

🫡

Make building Nostr apps easier for average users like me💜💜💜💜🧡

The easier you can make it to iterate on entrepreneurial opportunities the better

What's particularly cool here is the interoperability of it

Do the work well, do it once, and then everyone can benefit from it

This is capital creation at it's best

glad you're here

Will. I love you. Never stop building. 🫂💜🤙🏻

A future where everyone is using Nostr, but they don't really even know it. They're just being social on the Internet.

nostr:nevent1qqsw44mh9wzu8yx9dppw9cqehf79px93gtp5ygurpnmuax4m82s303qpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygpjuxp8vd29p6ancknaztql3eajk52y8xkppfn7au7elkw9c68zg5psgqqqqqqs43qelj

We (that is, you and https://opfn.co/about ) should really talk in the near future.

I read it but your model looks quite foreign to what im building

yes. it’s an urbit model.

yeah urbit was always kinda crazy to me

what do you mean by "an urbit model"? because I think you might be incorrect.

if you mean "at the level of sitting down and writing code, there is no distinction between on disk and in memory", then sure. there are some other similarities, but less than you (seem to) think.

I mean to be fair thats the first thing this reminded me of, do you have a writeup or video somewhere?

It makes sense. The project did sort of grow out of Urbit, but there are fundamental differences in my mind that are less salient to people who haven't gone deep on Urbit and Pallas - this is very understandable. There are only maybe a few dozen people on Earth who could articulate the nitty-gritty differences between Urbit and Pallas, even though they seem huge to me lol

The technical docs are the best writeup we have: https://docs.opfn.co

but there's also this (sort of old now) comparison of Urbit and our project (which at the time we were referring to as "Plunder"): https://blog.vaporware.network/2024/06/04/plunder-explained-for-urbit-users.html

All that said, if you ever wanted to talk shop in realtime, myself and my cofounders would love to shoot the future-of-the-internet-and-computing shit with you sometime. shoot me a DM if you want to schedule something!

I get that and you're not wrong in some ways. But when you were talking about the technical difficulties you were overcoming (I think it was about paging large amounts of data between disk/memory) with the new Notedeck, there was so much overlap with the problems we're solving.

and our final goals are essentially identical, especially with what you're saying in this note.

So many things happened , can’t wait to get back on nostr and see what happened after back from

Holiday .