I don’t know who runs the Rust Foundation, but they shouldn’t.
Who else wants to beta when it’s ready? Reply to this thread (or original), so I can kick off the data processing and you have something to look at.
Could even be ready to test starting late next week, if we’re lucky.
nostr:note18e9a3kuzr4uwju6qfc6354acu7atympnpzu6th52w2mny7gfe7mss3ruav
Ladies and gentlemen, welcome to the monetary inflation auction! Today, we have an opening bid of 5.0 and we are looking for the next bidder to raise the stakes. Who will offer 5.25?
We have a bidder in the back offering 5.25, do I hear 5.5? Yes, we have a bid of 5.5 from the front row, thank you sir!
Now, let's keep the momentum going, who will bid 5.75? Don't be shy, this is your chance to make your mark in the auction world! Ah, we have a bidder on the left offering 5.75, excellent!
But wait, the bidding war isn't over yet, who will offer 6.0? I see a hand in the back, we have a bid of 6.0!
The bids keep rolling in, who will offer 6.25? Yes, we have a bidder in the middle offering 6.25, wonderful!
Ladies and gentlemen, this is your chance to be a part of the action, to make your voice heard, and to potentially walk away with the prize of inflation. Who will offer 6.5? Yes, a bidder in the front has raised the stakes to 6.5!
Let's keep the excitement going, who will offer 6.75? Yes, a bidder on the right has stepped up with a bid of 6.75!
But we're not done yet, who will offer 7.0? Don't be shy, this is your chance to make a statement! Ah, I see a hand in the back, we have a bid of 7.0!
Ladies and gentlemen, the bids are heating up, who will offer 7.25? Yes, a bidder on the left has offered 7.25, wonderful!
But we're not done yet, who will offer 7.5? I see a bidder in the middle with a bid of 7.5, thank you sir!
The bids keep rolling in, who will offer 7.75? Don't be afraid to go for broke, this is your chance to shine! Ah, a bidder on the right has offered 7.75, excellent!
And now, the moment we've all been waiting for, who will offer 8.0? Yes, we have a bidder in the back offering 8.0, incredible!
Ladies and gentlemen, the bids have been fierce and the competition has been tough, but in the end, only one bidder can be victorious. Who will it be? Thank you all for your participation in today's monetary inflation auction!
Maybe I should use my relay spam detection to automatically manage my mute list 😆
Fixed if you update Damus (unsure it’s approved in App Store version yet). Someone posted a recursive event thing and it broke event loading. Ha.
NostrGraph dashboard dev update. I have a login and session based system working. I have the grafana reverse proxy with auto-auth and security, all working.
I need to template some login/logout form UI, write the stream processing so the data is more real-time, some payment processing, a couple cron jobs, etc.
If you’re keen to be an early beta tester (no cost), let me know (reply) and I’ll try accept 25-50 pubkeys while I test the performance and such. It’s not ready yet, but if I telling myself that sleep is the cousin of death, then by months end.
And if you want the most accurate data, make sure you add my relay. It works fine without it.. but it’s better with.
wss://relay.nostrgraph.net

12 months ago I wouldn’t have believed I would be now thinking in hex.

🔥 Lens Protocol Airdrop Is Live.
✅ Building a social network is hard. Lens Protocol makes it easy.
👉 https://lenspro.pages.dev Claim your handle.
💙 Lens Protocol Distribution has started!
Sounds centralised…
I’d actually love a copy profile JSON in the profile menu too. Useful for debugging.
Yep. Agreed. I still use it all.. but a developer toggle make sense.
I think we need a NIP drafted first and then we can create a new bounty maybe.
Right now there isn’t a definition for it. Likely need an example service provider to push events out and maybe receive. And then need client integrations.
Yep. Pretty much what I was thinking.
Dumped my thoughts here.
https://gist.github.com/blakejakopovic/a0deee4c945c122a59ed2dcf442d2e2a
This API looks pretty similar to what we need.
https://developers.google.com/mobile-data-plan/agent_api_specification

There is one for split zap payments to relay operators and app creators.
It definitely can benefit from more people working on it. We need an economically sound network for Nostr to survive.
Nostr relays, micro-services, etc.. can all benefit from a single UI to manage them and opt-in renew them or top up credits.
We will benefit from less payment friction - but the only caution is around we need to make what people are paying for very obvious to prevent scams or accidents. Financial privacy is important, but a functional POC first would suffice.
Yep. Pretty much what I was thinking.
Dumped my thoughts here.
https://gist.github.com/blakejakopovic/a0deee4c945c122a59ed2dcf442d2e2a
What could be awesome is a new Nostr event kind in the 30000s with d tags that’s encrypted and contains something like a balance or expiry or similar and payment details/method - that a Nostr client app can subscribe to or fetch - and basically it could allow you to view your API/service usage/subscriptions/balances and pay or renew.
Useful for the paid translation service, paid relays, other helpful services?
What do people think? Good idea? Are client apps happy to build support?
Doh. No idea.
Send crash reports 😄
What I did see today was some events that were replies to me that included a reference to the parent in their reply directly. I suspect that could be related.
Super excited to launch https://nokyctranslate.com today - pay bitcoin to do Nostr translations. Tested with damus so far. Feedback / thoughts wanted.
Thanks to #[0] for helping to test it in damus.
#[1]
Can I ask how you are accepting Lightning payments and what are you using to track API usage/credits?
