Introducing PWAstr
Compose PWAs from events.
Ready to use in approximately 2 weeks
Introducing PWAstr
Compose PWAs from events.
Ready to use in approximately 2 weeks
π
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
π
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
Yes, that's actually in the "spec" already.
is this spec in the room with us right now?

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 π―
G, your ideas are all so big.
Related: https://ostrichscript.com/
nostr:nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg83vtulad30gpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsz9mhwden5te0wfjkccte9e3h2unjv4h8gtnx095szwd0k7 is also working on something similar using WASM: https://gist.github.com/Semisol/fc8747d67765fded62f2e6192e32857d
IMO, lua and wasm are better choices than typescript, since using typescript opens you up to all kinds of security issues unless you can effectively sandbox it (unless that's what you actually want).
This would be a killer #Nostrnests topic with nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn and nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p
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..