You can find #bitcoin in Swiss flea markets
nostr:naddr1qvzqqqy9hvpzpz00j2u7hekure828x8kgaljyl54g2tz0v9r8hyfkeqwzdaj26l9qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtn0d3shxtnpwpcz7qqsvfexwme3d9hnwvek8purgarpvydll469
Para quien conoce nostr, el tuit de Juan Rallo se ve claro: propone Cashu como solución para Argentina.
I don’t even remember that one
I just fed some goats by zapping, pretty cool
Come check out nostr:npub1v60thnx0gz0wq3n6xdnq46y069l9x70xgmjp6lprdl6fv0eux6mqgjj4rp stream on zap.stream! https://zap.stream/naddr1qqjrxvmzv3nrgdfe95exvd3n956xxer995urjwfe95mnzetrx3nrxenpxdjrsqg3waehxw309ahx7um5wgh8w6twv5hszxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qg3waehxw309ahx7um5wghxcctwvshsz8nhwden5te0dehhxarj94c82c3wwajkcmr0wfjx2u3wdejhgtcpz4mhxue69uhhyetvv9ujumn0wd68ytnzvuhsz9thwden5te0dehhxarj9ehhsarj9ejx2a30qgsv73dxhgfk8tt76gf6q788zrfyz9dwwgwfk3aar6l5gk82a76v9fgrqsqqqan86na323
In the parallel universe of Web3, XMTP is overengineering MLS messaging for wallet communication with L3 blockchains, gossip networks, and node partnerships—while Nostr already supports Bitcoin, and Cashu is growing fast.
This should have worked `nak event -k 9002 -t h=MXciDlZ5Me0Q64VL -t open='' -t public='' --auth --sec=xxxxxxxxxxxxxxxxx communities.nos.social`
hey nostr:nprofile1qyxhwumn8ghj7e3h0ghxjme0qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qpql2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqta478g I'm the guy behind it's development. Can you tell me more specifically how did you try to make it open? If you set the group as open, users should be auto-invited on posts. Maybe there's a spec for this that I missed? I will set it for you for the moment.
Which IP is the one misbehaving? At nos.social, we have a couple of scrapers. One respects rate limits, though we might need to adjust the backoff settings. The other one is more likely to be causing the issue, as we haven’t had time to implement rate-limiting there yet. This could be a good wake-up call for us to prioritize that.
Summarizing threads seem to be a perfect use case for Grok, is there some DVM to do the same?:
In 2015, when Apple Music was launched, Apple attempted to stifle Spotify's growth by leveraging its control over the App Store. Here's how Spotify outmaneuvered Apple, providing a blueprint for similar companies facing dominant competitors:
Public Exposure: Instead of quietly complying with Apple's restrictive policies, Spotify's CEO, Daniel Ek, made the conflict public by filing an antitrust complaint with the European Union (EU). This move exposed Apple's practices, which included charging a 30% commission on in-app purchases, blocking external payment links, and rejecting app updates that mentioned alternative pricing or subscription options. By doing so, Spotify not only highlighted the unfairness but also rallied public and regulatory support, which is crucial for smaller companies. Citations:
Strategic Legal Action: Spotify's decision to go to the EU rather than just accepting the status quo was a strategic legal play. This action led to an EU investigation, which eventually fined Apple over €1.8 billion for its anti-competitive practices in the App Store. This legal victory forced Apple to alter its policies, allowing external payment links, which significantly reduced Apple's ability to control Spotify's revenue model. Citations:
Building Alliances: Spotify didn't fight alone; it united other developers and companies in similar situations, creating a broader coalition against Apple's practices. This collective action increased the pressure on Apple and demonstrated to similar companies the power of alliances in combating larger entities. Citations:
Focus on User Experience: Throughout the conflict, Spotify continued to innovate and improve its service, focusing on user experience by expanding into podcasts, audiobooks, and maintaining competitive pricing. This focus ensured that users remained loyal, which was critical in maintaining growth momentum against Apple's aggressive tactics. Citations:
Leveraging Media and Public Opinion: By making the fight public, Spotify turned Apple's pressure into free marketing. The narrative of David vs. Goliath resonated with consumers and the media, enhancing Spotify's brand image as innovative and consumer-centric against the backdrop of Apple's perceived monopolistic practices. Citations:
Persistence and Innovation: Spotify's strategy included never backing down from the fight while continuing to innovate. This resilience led to growth from 75 million users in 2015 to 489 million by 2023, showcasing how sustained innovation and persistence can outlast the initial pressures from a larger competitor. Citations:
For similar companies, the key takeaways are:
Transparency and Publicity: Making conflicts public can gain public sympathy and regulatory attention.
Legal Challenges: Pursuing legal avenues in jurisdictions with strong competition laws can force changes in monopolistic practices.
Alliances: Forming coalitions with other affected parties can amplify the challenge against the dominant player.
User-Centric Approach: Keep the focus on enhancing user experience to retain and grow your user base.
Media Engagement: Use media to tell your story, leveraging public opinion as a tool against larger competitors.
Continuous Innovation: Never stop innovating to keep the product relevant and competitive, turning adversity into an opportunity for growth.
This approach not only helped Spotify survive but thrive, becoming 5.5 times larger than Apple Music in terms of user base by 2025. Citations:
Things to keep in mind when building an app that Apple dislikes https://x.com/futurestacked/status/1878758946170880183?s=46&t=NcPcc0V0XE7jcwO0uEGOGA
Same reason why this is a great ecosystem for devs. Valid for Bitcoin, valid for Nostr.
https://x.com/adam3us/status/1857109609636372817?s=46&t=NcPcc0V0XE7jcwO0uEGOGA
Oh it's the 10002 tag! now it makes more more sense 🙏
What I don’t understand is how to get the “Reads, all pubkeys” type of stat. I mean the writes can be obtained from a firehose sub but I don’t get how to read a count of who reads from a relay. Specially a relay you don’t control
And how. Does `Users per relay` reads counter work ?
Hey nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy how does nostr.band count events in the `Events per relays` graph? A firehose subscription of all posted stuff?
At nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch we did some similar work on top of your library for a probably incomplete version of Nip-17 but it may be useful anyways https://github.com/planetary-social/nos/blob/aebbcb7353ec5cc34584bc3c802ddb6b754cb6ad/Nos/Service/GiftWrapper.swift