I didn't felt a strong need to build me a DIY BTClock using nostr:nprofile1qqst2yn6pr8nxctzwjqq5su83qdflx8qfwwrwytwjt09y5zfsc6uggspypmhxue69uhhyetvv9ujumn0v3jhyatwdejhyuewdejhgam0wf4j7qgmwaehxw309ahx7um5wgh8xct5dphkzunyv4ezucm0d5hszymhwden5te0danxvcmgv95kutnsw43z7f2mgdy code before, but I sure do now :)
☀️ GM ☀️
Testing out Olas 🌊👋, instagram feed spec app
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft when not signed in, heart, or comment actions should prompt sign-in/create keys pop-up.
https://github.com/nostrability/nostrability/issues/130
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z are there other apps following IG spec?

Can react-native generate split abi? 108MB for the umiversal .apk is a bit too much IMO. nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75sprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszynhwden5te0wp6hyurvv4cxzeewv4esdp32r9 nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0
Fuck apple/google stores.
nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 is the way
Throw in a nostr:nprofile1qqszm52qe2qdkc4u7dma0klx3532jka2g8geck6fwxncyp90wktq2xspp4mhxue69uhkummn9ekx7mqprpmhxue69uhhwetvvdhk6efwdehhxarj9emkjmn9qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsy47788 friends and family connection from nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcprdmhxue69uhkummnw3ez6vfwde3x7tnpdenkzmnf9e3k75xqss4 Hub with a dedicated ln address for receiving zaps and you've got yourself a deal ;)
try with --overwrite-app and/or --overwrite-release
Winter is coming.

It DOESN'T work, cannot create offers...
Is Robosats a Scam?
After completing several successful trades with different coordinators on Robosats, I think it's a promising platform with great potential. The concept is appealing, especially as a non-KYC exchange tool, and I genuinely hope it gains more users and achieves long-term success.
However, I've recently experienced situations where I felt I was unfairly penalized, resulting in the loss of my fidelity bond for posting an offer. So far, this has cost me around 30,000 sats.
Here are the offer settings I used:
Public duration set to 23:59
Escrow/Invoice time set to 8:00
These settings should ideally allow you to sleep without risking your bond. If someone accepts your order right after you've gone to bed, the 8-hour escrow time should give you enough buffer to wake up, pay the invoice, and complete the trade.
The issue is that if someone takes your offer close to the end of the public duration—say, with only 1 or 2 hours left—the 8-hour escrow timer does not extend the overall duration of the offer. If you’ve gone to bed with less than 8 hours left on the public timer, you might have less than 8 hours to pay the escrow invoice before the offer expires and your bond is forfeited. This essentially penalizes users for not being able to respond instantly.
This setup seems flawed, as it forces users to stay vigilant during sleeping hours, risking money if they can't respond quickly enough.
I’m unsure if this issue varies by coordinator. Most recently, I noticed this with the Temple of Sats coordinator, but I believe I’ve had similar issues with others.
If this is the intended behavior, it raises concerns about potential bad actors using automation to take orders right before expiration, betting that the trade creators won’t respond in time—causing their bonds to be lost.
Has anyone else experienced this on Robosats? Any advice on managing it?
nostr:npub1v3tgrwwsv7c6xckyhm5dmluc05jxd4yeqhpxew87chn0kua0tjzqc6yvjh
Two ducks talking:
- Quack
- I was just about to say that.
Happy save-us-from-fiat-debt-doom whitepaper day 


