Try https://nostrlogin.org 

 That's hard to do on native, but pretty easy on the web. Let's start with creators first  

 Never heard of this!
nostr:nevent1qqsrjdx5m8kyuv66fdehg508q77srw8wlntf459r6639mej49dd9ysspzpmhxue69uhkummnw3ezumt0d5hsygzxpsj7dqha57pjk5k37gkn6g4nzakewtmqmnwryyhd3jfwlpgxtspsgqqqqqqspgck7u 

 Coming this week  

 These perform poorly at times. 

 Yes, but it doesn't send EOSE if event isn't found and thus is harder to use. 

 Indeed, I got one too now, apologies. If you're using stock strfry then I probably confused it with something else, will check. Thanks. 

 Shortcut to you-know-what :) 

 Coming soon, Karnage designed the thing. 

 You are 100% fine 😂 

 Oh yes it is! 

 Take a look at https://nostrlogin.org and https://github.com/nostrband/nostr-login/ 
Also AMA 

 relay.nostr.band already supports nip-50 searching across file metadata events, so yes it's all there https://nostr.band/?q=gif+kind%3A1063 

 what issues are you seeing? it has aggressive rate limits, but should be fine aside from that 

 Maybe a little, in theory, if you can figure things out yourself. Can't say more yet.

Why do you believe this is the biggest hurdle? Are there so many people using nostr who want to tip but don't have a wallet?

 

 Can you expand please? People on nostr have wallets but somehow can't pay? 

 Thanks, that makes sense. 

 Ok this makes 100% sense and I agree, existing creators won't migrate until there is a frictionless path to monetizing _existing_ audience on nostr. 

 Can you please expand on how hosting (content/stream/etc) on your own site makes it better for you than on zap.stream? I'm not expressing doubts, I just want to learn more about your perspective. 

 Creator still doesn't own or control the app. Design/feature/culture/vision/etc decisions of the app may make it hard to use for the creator, and then migrating the audience elsewhere might be a big question. 

 Btw wdyt of Ditto by @Alex Gleason 🐍  ? Sounds like a promising tool for creators to connect to their communities? 

 Yes, it's just a question of time. 

 It not really about Patreon (monthly payments to creators), it's just that Patreon is now moving into content platform direction - they're trying to solve the "where/how should you talk to fans" problem, and that what I'm looking at too.   

 I don't think followers will move if one of the creators moves. "The Chat app" means you talk to many creators there, and if one of them moves I'll have to install the new app just for them? An app per creator might make sense if it's been this way from the start, but not when I'm already used to using one "the best" aggregator app.  

 The Chat app as the ultimate format to talk to fans (a "floor plan" of your online space) makes total sense.

> Or they can build/customize their own apps or tools for whatever aspect they need to. 

That's what I think might be the way to go. 

 Thanks a lot for the input!  

 Agree with all you said, but there's more to "owning" your online space. Your preferred Nostr app might present your content well and be usable to talk to fans, but you still can't change the design of it, can't extend it the way you want, can't promote it in all ways possible and can't measure your marketing performance, etc. But that's a story for another day. Thanks for the detailed input! 

 I absolutely love your perspective so please keep sharing it! I agree that ultimately it might be about the financial support in most cases. 

What if existing creator invited their audience to use Primal, which sort of has fiat->zaps. They'd have to invite them somewhere, bcs their fans aren't on Nostr anyway. Could that work? 

 You kind of own a domain name, but not your profile page on Damus. If you have an interoperable customizable nostr app on your domain then you are much closer to owning that place. 

 You'll have to see it first. 

 So you are a creator excited about nostr. You start using app A and like it, and you want your fans to join. You recommend app A and they start using it. Then app A changes - bans, censors, prioritises features you don't like etc. You've spent your clout to promote an app that you no longer like. You can switch, but it's hard to persuade your followers. That may or may not be a big or common problem, we don't know yet. But outbox model doesn't solve it. "Apps are interoperable" lowers the bar for switching, but it remains to be seen for how much. Does this make no sense? 

 The logical end of this path is "custom app per creator", which is roughly what I'm exploring now. 

 Every app has power to censor people, no matter how 'real nostr' it is. Someone's there to blacklist a pubkey and push the 'commit' button and the app gets distributed to it's users one way or another and someone gets censored. The motives for blacklisting don't matter, but I've seen enough in recent years to know that's inevitable.

And I'm not even mentioning the lighter things like changes in design or features. App starts prioritizing Repost instead of Zap button and my audience's behavior changes without my control. Outbox doesn't fix that either.

I'm not saying outbox is failing/wrong, it does the job at the relay level and makes bans in 'real nostr apps' much less likely. But it doesn't solve everything. 

 Yes please 

 > I suppose "an app per creator" would be just some creator adding some branding and distribution to an open-source codebase such that they have control over auto-updates for their community? 

Basically yes, but also being able to selectively extend/change the app with plugins. 

And even if creator is forced to do something (update, switch plugin etc), if that is happening on their own domain which fans are used to using then it shouldn't be an issue. 

Bigger question then is - would "true fans" use best-art-by-megan.com or not. Need to figure that out. 

 We have nip89 for apps to announce support for kinds and with links to kind handlers, and many apps i.e. habla let you select which app to use to open a nostr event, etc. 

 My kids love the emperor  

 Export from twitter exit.pub 

 Writing content includes reactions, so I would say 80/20 might be closer than 99/1 

 No that's not spam accounts, read description of trusted user there on stats page 

 We've got some work to do now

nostr:nevent1qqsxawum7re5nvtaksfj0x2rcnqx8kqxnj22us5c7jca2k7xndd2u9qpz4mhxue69uhhyetvv9ujumn0wd68ytnzvuhsygzccaq65ccv9k3454480sws2wqepz73q5z0m5kckslhyhh6d533jcpsgqqqqqqs5rd4g2 

 I agree with you on auth part, especially given that signer apps can have special cases for file uploads like "sign uploads auths for this hash for any server for 5 minutes"

And I am in Spain too, beers sound nice  

 Ohh that's way too far up to the North :(

Blossom servers should probably support both ways - "upload anywhere" and "upload only here", otherwise I'm forced to assume the server and app might reupload my file anywhere. Maybe nip98 needs a list of servers instead of just one. 

People had to invent "-" tag for events to prevent this permissionless rebroadcasting with relays, I'm sure the same question will rise with files. 

 Anyone can rebroadcast file permissionlessly by authing with their own keys. But ok, maybe delegating this to a server to save bandwidth is an added benefit. Will see how it develops  

 Haven't decided about nostriga yet 

 Congratulations! 

 Health to you and your family man! 

 Is it over? 

 But that knowledge will stay secret because we can't see the quotes 

 Congratulations! Keep up the great work! 

 Blossom and in fact nip96 use file hash to address it, which is easily extracted from a dead url and client can lookup the author's list of used servers and ask for that hash from there. It can also query that hash on nostr relays among file metadata events. No apps have that implemented properly yet, because no big server died yet, but it will be implemented, and it will be much more resilient than yt etc 

 No one is shaming anyone.

What is the satisfying solution to the problem? 

 How does Peertube solve the problem of dead instance/links?
 

 > If that server shuts down or censors you (easy via your npub), then the URL is dead, so the link in your event is, too. It has none of the guarantees of real nostr events that are published to relays in the current form of the spec.

I explained how nip96 and blossom are our poor-man's solution to the problem you stated in this branch. You dismissed it, and proposed we integrate with something that doesn't even try to be a solution. Not sure where you're heading here.
 

 And upload to nostr-native media servers, please 

 Your server is a nip46 client for the nip46 server running inside your client. This is awesome and cool!  

 Is there the npub=>color conversion scheme described somewhere? 

 Hmm this will produce hard to see colours a lot of the time, I guess  

 Ah, it's deployed on next, ok will check them out, I like the simplicity of this. 

 I did nothing, and I don't see it, maybe it was an old deleted event still sitting on some relay...  

 What is that? 

 If we do try to educate users then at least we should do this gradually. Forcing someone to learn keys/relays/etc when all they wanted was to post a "like" or write "hello world" makes no sense. There should be a super-easy way to start and get the value user expected, but then a gradual process of explaining why things are the way they are in the context of tasks that users are trying to accomplish. That's probably 100x harder than just snapping a couple explainer screens here and there. 

 UI of TG shows me the list of communities (groups) sorted by latest post, with a badge with number of new posts. Suppose people could post to many communities with one click. Now TG's interface degrades for me - I'm likely to be in several groups on the same topic, and when I open them one by one I see the same posts auto-crossposted. 

A feed interface of 'all new stuff from your communities' works, because it dedups the posts. But what if I like TG's approach? Any thoughts on this? 

 Ok this one is solving the notification counter! But it means you'd have to re-order the feed when I open the community so that stuff I already read in other places falls down, and stuff I haven't read pops up, even if it's older. Right? 

 What's chat message vs post? Chat message has 'root'? 

 I love the icons and counters and overall the attempt to integrate different kinds of stuff under one "destination"! 

 Thanks, that nip is enormous, need to think it through  

 Suppose community has so many new posts (made worse by being able to post to many at once) that it's feed becomes too big to sift through. The more popular the community is, the more likely it's feed will be huge. Shall we need an algo then? 

 Likers are included in 30k wau 

 There is no way to count those who don't post any events 

 Are there good live examples of nip29 groups/relays?