Nostr stores should support cashu payments sent in secure DMs. Buyer can reclaim the payment if seller doesn't reply. Seller doesn't need a payment processing or e-commerce server, mobile phone is enough. Maybe the cheapest and easiest way to run a small online store. Some sort of order management UI for buyer and seller on the client side would be nice. Just thinking aloud, only tried Shopstr so far but should check out others as well (Amethyst?) Pic kind of related, could be my dropshipping lifestyle store.

@BTCPay Server 💜

Tuesday night in HEL with Behemoth

Couldn’t do much bouldering at the rainy Åland islands, but the nature was beautiful.

Eivør & Heilung in Helsinki last week

Lugano was so much more crazy and fun than I expected 😄 I played my first gig since high school. Can't wait for the next Rockamoto! @knutsvanholm @Luke de Wolf @Samson Mow @Joe Nakamoto @Giacomo Zucco @npub1ydxy...rlcw @NetDiver

My email correspondence with Satoshi in 2009-2011:

Satoshi - Sirius emails 2009-2011

Bitcoin is the free market alternative to banks and government money. How can we do a free market alternative to insurance companies? Insurance is the natural enemy of public harms like the junk food industry. It could even proactively protect our personal safety and health. The problem is, just like banks, current insurance companies are behemoths that are entwined in the system and lobby the government to stifle competition and innovation. We need free market insurance that is independent of government institutions, just like Bitcoin.

👍

Spam prevention should work by discarding events from users that are not connected to your social network like normal users are. For example, swarms of users that are connected by only 1 or less follows from legit users. Iris already discards messages from completely unconnected users, but need to add shared block list support and better detection of sybil swarms. This should work especially for trending algorithms, where reactions from socially connected users are more valuable anyway, and missing a like doesn't matter so much. Currently Iris trending list comes from nostr.band, but I want to do it locally at some point. That's the only way you know what you get.

Iris now supports secret chats that don't leak metadata, implementing the

hrfbounties

Home - hrfbounties

The Human Rights Foundation is supporting open-source developers working to increase the usability and privacy of the Bitcoin and Lightning network...

bounty #3. It works also for group messaging. It's a quick & dirty solution, but works. A shared nostr account is created for the secret chat / group. Its nsec can be shared via link, qr code or invite message from a single-use anonymous account. Users can then communicate using the shared account's messages-to-self. Iris signs the inner messages with your own key, but the arrangement could be used for anonymous group messaging as well. I'll also add inner message encryption at some point, so you can ensure that only certain group participants can read the message. This arrangement doesn't introduce any new event kinds and works also in clients that haven't implemented a special UX for it. You can just log in with the nsec and message yourself. I had to disable the Iris social graph filter to let invites through, so now Iris DMs are open to spam again, but I'll try to figure out a better solution. As always, the UX needs a lot of attention, but I believe here's an MVP. Screenshots: Alice wants to message Bob: Alice sends a secret chat invite to Bob: Bob automatically follows the invite from Alice. They can now message each other in the secret chat: Here's how the invite looks in another client. I will add an "nostr:ninvite" URI in addition to the nsec.

I'm a bit jelly to native app developers for SQLite. Yeah, there's sql.js but it doesn't persist anything. Juggling between storage and memory (and relays) is the difficult part. That said, LokiJS, Dexie and Fuse are great javascript libraries with zero dependencies. Backed by LokiJS, Iris now has some basic filtering tools, and will be adding more. Also need to get a Tauri desktop & mobile version done at some point, so we can be independent of DNS, hosting or someone pushing a version that breaks the UX for everyone.

👁️‍🗨️

Added zaps to Iris. Thanks to #[0] and #[1] for letting us use code from Snort! It's not quite polished yet and zap type selector is still missing. I'm also noticing that zaps don't appear in the listing immediately. Working on it.

I wanted to do fun things instead of useful things, so I added the option to view a profile feed as an image gallery.

Just pushed a data subscription update that should reduce bandwidth and CPU usage. Lmk if it works well or degrades content loading. #TestingInProduction

Following / posts feed jumping should be fixed now. Replies to posts were removing the replied post as a "duplicate" also from the posts feed where the reply wasn't visible. Sorry for the bad UX 🐒 Zap listing and content filtering by follow distance are on the backlog. "Freedom of speech doesn't mean we have to listen."

PV! Just pushed a major refactor of the Iris codebase. Removed a big chunk of unnecessary code and depencencies, and broke down large files into more manageable pieces. Let me know if I broke something in the process. There's not much visible change to the user except for the faster loading search box, but the codebase should be much less obscure for contributors now.

GitHub

GitHub - irislib/iris-messenger: Decentralized messenger

Decentralized messenger. Contribute to irislib/iris-messenger development by creating an account on GitHub.

One issue I'm noticing is that Following / Posts feed starts pushing old posts after a while, looking into it. Also sometimes you get a black page when loading some url. That's because of StaleWhileRevalidate caching and needs to be fixed somehow. Hoping to get zap listing done soon, then zapping, then some updates to the mobile apps. Then maybe user lists and custom feeds.