Apple is Nostr's inverse. Nostr: free, open, easy to build on, permissionless distribution. Apple: paid, closed, painful to build on, gated distribution View quoted note →

GM - We we're rejected by Apple (for just a Testflight) with no feedback... Fuck this dystopia

Testflight invites are now up for Igloo iOS! 
 Just put in your email and we will get the invite to you asap!

Frostr

This is still somewhat of a closed Testflight at first. We need to get our strategy straight before we go to Apple for review.

Will be sending out first testflight invites tomorrow 😤 View quoted note →

Pushing for IOS testflight asap - pray for me frens

Buildout of the our V2 Frostr core library is under way 😤 (written in rust btw)

Really, we just want to get Frost to work great for signing notes over relays so we can start signing Bitcoin transactions over relays ¯\_(ツ)_/¯

Better onboarding instructions / guidance coming soon to igloo apps! We are working to simplify understanding of Frostr within our apps along with doing FAQ and Glossary soon! Lot's of work to do still to make this truly "easy" but it is all possible.

Well that was easier than I thought... Thanks @miljan 😅 View quoted note →

Well that was easier than I thought... Thanks @miljan 😅 View quoted note →

Thinking about two different ways of supporting frostr signer on iOS. One is to just copy primal and use the audio player for keeping background signer online, but who knows if I could get the app approved - also I would hate to copycat so quick and bandwagon onto this workaround, but hey if it works well?? The other way is doing push notifications; which I think I found a way to do very privately where no events are stored and we will have no idea whose device tokens are being held. However that still requires storing device tokens and also running a server which I really wanna avoid doing.... There are definitely more ways around this. There’s a lot that is technically possible, but with Apple, you have the additional question of will they even allow you to release this?? Such an interesting problem, there is no right answer!

Wow really groundbreaking stuff from Primal! This is super inspiring for us as we're trying to figure out best approach for IOS background signing at this moment! It's possible we might even be able to highjack this functionality to work with Frostr without any code changes?? Will report back 🤔 View quoted note →

igloo-cli version 1.0.2 has just been released! - QR codes in CLI for sharing credentials (toggle with Q) - Improved visuals: animated FROSTR intro + cleaner layout - Refactored arg parsing with better flag handling - 100 new tests massively increasing coverage Use igloo-cli to create a new Frostr keyset OR just run it as a signer:

GitHub

Release v1.0.2 · FROSTR-ORG/igloo-cli

What's Changed qr code display for shares and group by @AustinKelsay in #12 Feature/frostr icon by @AustinKelsay in #13 first pass test coverage o...

opus 4.5 is one of the smartest coding models in the world right now but I still struggle to get even the frontier LLM's to be able to grasp a lot of protocol details of Frostr when working with features in the code or docs. So either we are still (a little) smarter than the AI OR we are just retard maxxing too hard (likely) View quoted note →

Yes you could setup a 3/5 with frostr! It would be best to keep the nsec offline and cold after setup. It is worth understanding though that Frostr uses a "trusted dealer" setup of Frost meaning that the nsec WILL be known and contained on one computer in order to setup the 3/5 initially so basically you need at least one "trusted dealer" to setup the quorum View quoted note →

With frostr your keys DM each other to sign notes 💜

Working on nip46 frostr stuff with opus4.5... Bro doesn't stand a chance 😂 View quoted note →

Share it brother! View quoted note →

Absolutely! But we never wanted to change standards we just need them to be implemented consistently (and actually work lol) We are working on proposals internally though and also FIRST wanna do everything we can on the side of our apps / libs to make the experience as clean as possible (before proposing spec changes) View quoted note →

Should clarify - nip07 is quite simple and standardized across the ecosystem! Barely have run into issues with how the spec is implemented on clients BUT it is (mostly) trapped in the extension environment... View quoted note →