That “local” feed default in Olas…

Heard about this one, but didn’t try yet:

note1mta5jmk6yajs99k8nfhdmys94da3dcw8k8mulw6n87fjt0cgyshqjfv47x

Does any client support recommended follow lists?

Could be implemented with public sets and even build a WoT based mapping between pubkeys and Twitter handles (and others)

nostr:note1gendervu5y34nattkv9lg2h9csxm737wql6pz7z6pf43vw3ez3mqadd3dw

The protocol can and does change, but I don’t think there’s a verifiable way to guarantee that a relay will honor your wish not to send events to a certain pubkey

If it follows the web, v3 is a terrible idea nostr:note1ytcez395r5cxf8wjjfcay525yxcdytcg2eg3jr0w0z6dpc4phqxqf7y4hu

Only in the landing page, seems fine in other pages

Btw, the burger icon in your landing page isn’t working 😉

Reminds me of this episode of The Hustle: https://www.imdb.com/title/tt0608717/

Two main characters (conmen) are dropped naked in the middle of London, the one with most money at the end of the day wins 😅

On npubs vs nprofiles nostr:note13ptqprywcl427eg20086vyppwzuyd8snmskae3yn0a25rmqmt3xsax4pev

Stay safe!

Some spy shit right here! 🤯 nostr:note1k0d6ntn5y595sfz25wmmp9dvzghj8cpnkxz7z8v5e9l8vpq44lqs2j2z5k

Bot to notify about earthquakes in Japan. Cool to see life saving stuff in nostr! nostr:note1xtl64n6yzxzh7n36p4mcra7hznxe78tjugjgqmnqcjejq50a7r3s39mw50

Well, I interpreted the point of the discussion as why would devs chose webapps when that doesn’t provide the most reach.

I think your point about users not knowing how to deal with web apps applies equally to not knowing how to deal with alternative stores - and in ios is not possible at all.

However, a web app can still be used as a regular website in the browser, even if the user can’t figure out how to add it to the Home Screen.

I do agree with the rest you said. Webapps do provide a worse experience on mobile.

I get it and agree, but the majority of mobile users are also exclusively using the official stores (in iOS they don’t have a choice). If I remember installing from APK on android (it’s been a while), you have to ignore a bunch of scary pop ups from the OS.

Don’t get me wrong though, I do think native apps provide better UX, cause you don’t have the indirection of a browser between you and the device. And Zapstore is a very cool way to distribute those apps!

But for now, I see web apps as the best way to avoid App Store bureaucrats and their shenanigans, while still reaching most users.

But you wouldn’t be targeting 90% of users anymore.

8 options and they’re all bad

In my case, single reason: I don’t want to ask permission to publish an app

Revokable subkeys will be a need for sure. It’s a matter of time until a bad client (intentionally or not) leaks a bunch of nsecs.

The dual stack approach sounds reasonable, but could also demand a lot from devs, when there are still few clients that reached maturity.

I think the path forward would be to have a prototype client with this dual stack approach, to learn how to do it as painlessly as possible. It would also give time for more clients to stabilize before they need to think about this.

But obviously, that will require someone’s time.

Focusing too much on which breaking changes to adopt would make it a harder and longer discussion than what the upgrade approach should be, assuming people agree that breaking changes will at some point be required. nostr:note1ms89ppa3pmtk9atl8zfrt5ejjnnhd79ydzaydjrmwfpzqz4umfvsf2xadr

About governments and their strategic reserves nostr:note15hd6hu22ew8gf8jtvvqxgrp85kudeha4z94eaxqp4a25gp6ek0ysg5mrc3

I don’t think they’ll sell bitcoin for economic reasons (they can always extract more money from us, or print, in bigger amounts), but they will sell for political reasons when anti-bitcoin or even neutral politicians get elected. That could even cause a bear market.