nostr:npub130mznv74rxs032peqym6g3wqavh472623mt3z5w73xq9r6qqdufs7ql29s I keep getting these errors when I try to use chat.routstr.com that basically say I need 1 more sat than provided (I have well above this amount in my account). I've tried with several models.
Merry Christmas!
He who writes for fools has the benefit of the largest audience
Read through the spec, and it's very well written and thorough. I made one suggestion here: https://gitworkshop.dev/npub1gzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gs3ea5ds/relay.ngit.dev/nsm/issues/nevent1qqsflz6xs779rrcmnd09wxud9luz0jg03kkxjy6demlu8yzfgz9dl8qk2gupm
This is the most nostr:nprofile1qqsxu35yyt0mwjjh8pcz4zprhxegz69t4wr9t74vk6zne58wzh0waycpz9mhxue69uhkummnw3ezuamfdejj7qghwaehxw309ashgmrpwvhxummnw3ezumrpdejz7xtf8w3 vibe coding research I’ve ever seen :)
It so close I want to shout “vervake” so everyone has to drink
https://block.xyz/documents/adversarial-cooperation-in-code-synthesis.pdf
A lot of my inspiration for this vibe coding methodology came from Vervaeke's dialogical co-creation. Cheers!
The means are never greater than the end
I created a POC around this. Results are decent. Having a hard time getting CLAUDE.md and AGENTS.md to respect it, but when I explicitly tell the LLM to check with the Telos, the results turn out well. https://github.com/telos-framework/init
Will definitely be delving into this. Love how you're always pushing the boundaries at lower levels and enabling innovative qpps to be built on top!
This is a cool project. If it's still around in 1-2 years without scandals I will consider using it.
Without scandals... That's my fear and goal!
When AI recommended I name my app Redshift because of its relevance Doppler app, I thought it was a good fit since it also reminded me of the awesome Routstr developer! nostr:npub1ftt05tgku25m2akgvw6v7aqy5ux5mseqcrzy05g26ml43xf74nyqsredsh https://redshiftapp.com/
Leveraging nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr awesome [Applesauce SDK](https://github.com/hzrd149/applesauce) to make the Nostr relay connections seamless in Redshift. https://redshiftapp.com/ gives sovereign great DX and security in managing their passwords #soveng
Built a dead man's switch that actually works. Client-side encryption means we literally can't see your secrets. Miss your check-ins? Your chosen people get what they need. Perfect for crypto holders, journalists, or anyone thinking ahead. keyfate.com #soveng
Garbage in, garbage out
Wow Opus 4.5 is insane! I built this Doppler clone on Nostr in less than 1 day (I literally had the idea last night): https://redshiftapp.com/
The goal is to allow developers a great experience managing their secrets in their project. It leverages Nostr gift wrapping to protect your secrets while giving you a UI and CLI to manage them. #soveng #ai #nostr
nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc would you mind reposting for some publicity?
Guns and cryptography
In and of itself, nothing is whole
Being forgotten can be beautiful
Also I could not Zap you nostr:nprofile1qqsggcc8dz9qnmq399n7kp2yu79fazxy3ag8ztpea4y3lu4klgqe46qpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpzdmhxue69uhhqatjwpkx2urpvuhx2ue0qy28wumn8ghj7un9d3shjctzd3jjummjvuhs8fa6r0; it said your receiving limit was already met
NIP-05 - Mapping Nostr keys to DNS-based internet identifiers
In order to allow human-readable aliases to pubkeys (identities on #nostr) or proving association with a domain, #nip 05 defines the method for linking identity with web domains.
The critical part is to host this file on the domain you wish to prove association (not necessarily ownership) of: /.well-known/nostr.json
This JSON returns the pubkey(s) and (optionally) the preferred relays. If the pubkey returned (from the domain to which you are trying to prove association) matches the "nip05" field in a kind:0 event, then nostr clients can link the two.
#learning
New goal: read a NIP every day
NIP-01: Not really an "improvement" but rather the base of the whole protocol. It defines the client and the relay and the communication between them.
It's a simple event based model (not dissimilar to the CloudEvents spec). It focuses on "who" (pubkey and sig) said "what" (kind and content) "when" (created_at). The "where" is loosely associated with your chosen relay. The "how" is the Nostr protocol itself. The "why" is a much more philosophical answer.
