Introducing PWAstr

Compose PWAs from events.

Ready to use in approximately 2 weeks

https://github.com/nostrocket/pwastr

Reply to this note

Please Login to reply.

Discussion

πŸ‘€

Whenever g announces something I need to look deep into wether it’s a joke or yet another g-scam or what

This looks legit; 60% chances it’s real and 20% chances it’ll launch

5% launch probably

But I feel Pablo will build it πŸ€”

What's the other 20%

20% is a subset of the 60% πŸ˜‰

With his propensity for airdops it's possible to launch and also not be real

πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚

you win the nostr cup for the day, sir

πŸ‘€

Would be cool if the event that defines each app could embed a bunch of components and share zaps with the components

Imagine if I create a cool event rendering components for, says, music content, and your app embeds that component/event; and if your app gets zapped, or if your users zap from your app and you take a cut, you could have each component/event receive a share of the revenue

That’s a(nother) great idea.

πŸ˜‚πŸ˜‚πŸ˜‚

You could offer β€œpoint on the backend” on Ostrich.work.

Yes, that's actually in the "spec" already.

is this spec in the room with us right now?

πŸ˜‚

fun fact: did you know nostrocket was initially called stalinstr: a project for G to organize his stalin pictures?

πŸ˜‚

🀣🀣🀣🀣🀣🀣🀣🀣

Buying domain now

little did you know, I just bought two domains...

πŸ‘€

Thanks! This might be exactly what I’m looking for.

Oh wow another thing coming out my heads spinning with all the new platforms and updates and STRs 🀣🀣

My point exactly πŸ’―

very cool proposal. structured approach to code management is the future. like what we can see with unison language.

there are some worries about sandboxing and isolation but that's something that can be improved later on after initial experiments.

i would also prefer capability to distribute wasm module which is interpreter for other higher level language that will be able to execute code from events containing that higher level language. but the composition is the key even if you use multiple different languages for different aspects the system.

expressive power of javascript/typescript type of language is very limiting when compared to, for example, prolog where the same code can be re-used in many more ways which is valuable if you want far and wide reuse. meta-interpreters and program synthesis are easy in languages like prolog.

also as it looks rn it's very web tech specific (DOM elements etc) but what's beautiful is that rendering is optional. execution environment doesn't have to render anything just execute code-carrying events enough for various other purposes.

if all tools to develop this core-carrying events are also published and distributed via nostr in the same form (after initial boostrapping process) this will enable more axiomatic and broad self-improvement process to emerge with ports to different execution environments and rapid exploration of new application domains.

can't wait to see where this goes..