Useage rate is better expressed in number of signing requests received and events signed rather than kb
Uninstalled obtainium.
nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 is better.
The zapstore experience is much better than the obtainium one. Although I still use obtainium for a fee apps not on zapstore.
Well I guess I cant watch youtube videos anymore. although maybe that's a good thing, I was wasting a lot of time there

nostr:npub1klr0dy2ul2dx9llk58czvpx73rprcmrvd5dc7ck8esg8f8es06qs427gxc do you have instructions on how I can start running a youtube downloader / uploader for novia? I tried the app but there doesn't seem to be any downloaders running
I relax watching videos on YT but I opted-out of the surveillance capitalism world and I'm not prepared to turn off my VPN or sign up to watch. I want to be on the free internet. Let's make nostr:nprofile1qqst03hkj9w04xnzllm2rupxqn0g3s3ud3kx6xu0vtrucyr5nuc8aqgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3samnwvaz7tmhv4kxxmmdv5hxummnw3ezuamfdejsz8mhwden5te0dehhxarj9ejkjmn4dej85ampdeaxjeewwdcxzcm99e5uqv's novia flourish and let's move towards a world where creatives can be rewarded by their audience rather than advertisers.
Yes, its only worth showing if it validates.
The screenshot looks interesting. On GraheneOS vanadium, the remote signer login didn't reach my remote signer. I used the extension on Firefox and logged in. But now it's not getting past "... checking the Brainstorm Calculation Engine API for user profile with pubkey"
My gut feeling tells me that this stuff should be done in a nostr-native way, ie with DVMs or similar.
Each server we add is just a cobblestone of the path that will eventually lead us back to hell, so we either have to do it locally or with stuff that's easily and dynamically replaceable.
Thoughts? CC nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0dv4ph5 nostr:nprofile1qqsfnw64j8y3zesqlpz3qlf3lx6eutmu0cy6rluq96z0r4pa54tu5eqpz9mhxue69uhkummnw3ezuamfdejj7q6hdgd nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpr3mhxue69uhhxct5v4kxc6t5v5hxs7njvscngwfwvdhk6tcpzfmhxue69uhkummnw3e82efwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsk7wj75
I agree. My intention was to build the graph client side, downloading the follow lists via relays slowly overtime as a background task. starting with the logged on user. It's potentially quite a lot of follow lists to cache and keep up to date. So maybe the idea of outsourcing it to a DVM has potential.
🚀 GitHub Actions over Nostr DVM's
Working with nostr:nprofile1qyt8wumn8ghj7cn9wehjumn0wd68yvfwvdhk6tcpg4mhxue69uhkkdnywp3kjmm80q6xvctzde5hq6m4xemkccm9x3ex5a3nvenx56rkxenkxatwv33hsancdcm8qmm9wyexscmwxd5kgtn0de5k7m30qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcqyrts65qfz5ztnyk3swyz9teyt40kkwskhqkez7kt0yjvaas76jkwu4295fp on this Proof of Concept ^^
https://cdn.satellite.earth/43463990dd11c9506989e5eda915757cf3ec1b32e8d472579cd2ee18d5685f0d.mp4
This is fanatic!
Thanks for pushing forward the CI/CD stuff. I like these weekly updates.
Great to see. Gitworkshop.dev rewrite coming Soon tm to lay the foundation to make issue management easier
I don't. It would be sort of weird to seek there private contact info it out just to send them some.
Do you ever find yourselves feeling dissapointed when you want to zap someone for being helpful online but realising you can't because the intetaction wasnt on nostr? It just happens to me on github
Added documentation for the NostrConnectSigner in the applesauce docs https://hzrd149.github.io/applesauce/signers/nostr-connect.html
Its going to be released in applesauce v0.11.0 and should be flexible enough to be used with any other nostr library 😀
It also supports creating a connection from the client side ( nostrconnect:// URI )
I'm hoping to use applesauce for accounts and signers.
I'm glad you find it useful.
Yeah, I use it a lot. I think it's from nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7hycrvd right?
Yes, I made it.
gasoline is petrol. It's more explosive than diesel.
Nostr is mostly outsiders. It's fitting to be an outsider in a community of outsiders. I appreciate you. I've been having some sad moments over the last few days also. Its that time of year.
Its usually translated to English as 'I can do no other' but we will let you off because your both German and Catholic.
Nice. I think my wife expected a token surprise gift alongside the ones she chosen in advance herself.
Were you and your wife's gift given expectations aigned?
Have you tried https://radicle.xyz? Did it work for you? Do you know how it works underneath? Should we stop the NIP-34 efforts and just adopt Radicle for decentralized code publishing and collaboration?
I'm really impressed with radicle v1.0.0-rc4. There is a lot to like; some great ideas, well executed with good engineering, publicity and momentum.
NIP-34 on the other hand, has no usage, little momentum, and really basic tools with jagged edges and confusing interfaces.
I can see why your question arises and here is my answer:
Nostr has fundamentals which set it apart as a superior protocol for code collaboration.
Radicle has had 6+ years, $7m in funding and a team of 12 to mature, create polished experiences and build momentum.
NIP-34 is new and has 1 person full-time alongside a small number of contributors who are focused on other priorities.
With patience and a concerted development effort the features of nostr can shine through and provide an attractive decentralised alternative to github.
From the simplicity of design, existing relay infrastructure, and vibrant development community to the growing userbase and ecosystem of social clients which will notify users and enable them to interact without leaving their app.
I have drafted quite a few more thoughts about what we can learn from Radicle but they must wait for another note on another day.




