He got a new iPad Pro yesterday so he needed inspiration 🤣 When he asked me to prompt him I was like, now is the time for Turdsoup to shine.

To add context, the reason I say this here is to provide a gateway to the first implementation of the relay.tools API. Friend lists are important and the question you pose is "where and how should they be stored?"

To me it makes sense to offer NIP-05 verification and NIP-51 friend lists at the domain level. Consider this a domain's "operational relay." From there, users have a realm to explore local relays while maintaining a universal aggregation of users and content.

Some people may want to host different configurations of operational relays depending on their goals. I don't expect Amethyst or relay.tools to decide what every configuration should look like. But, I imagine some users are content in taking a Damus-style approach, while others might prefer to segregate their data across multiple relays to ensure they can cater to every use-case and community goal they have in mind.

nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgawaehxw309a5x7arjd9nksarwdamjumn0wd68yvfwvdhk6tct9vymn I hope this makes sense lol

I think maybe that is the real issue. We don't see it differently- because it's a UI issue, which means it's also a relay.tools API decision.

I will go ahead and say, the way you could view relay.tools as a start9 for Nostr, I like to also imagine it as a start9 for the web. The old web. Web 2.0.

Reddit format is a template. 4chan is a template. Google+, FaceBook, Instagram, TikTok, even traditional BBS forums, WikiPedias are all templates of distributed communication and information channels.

NIP-29 makes sense in some contexts. Relays are decidedly multi-purpose so I imagine NIP-29 would also be decidedly multi-purpose.

If I host a Nostr client that controls relays, then I am running relays, and working with teams of administrators and moderators alike. It would make sense for cliques to exist within the relays to maintain a sense of respectable segregation without relying on the authoritative hammer to come down.

I have no regard for privacy mode outside of NIP-42 but I can't shake the idea that perhaps NIP-29 will become more relevant and desirable in the future. At the very least for segregating users within a relay.

My manager: Give me a prompt for something to draw

Me: There's a Nostr app for that

"So it's monkey, squirt, circlejerk.. What does that even mean..?"

10/10 app nostr:nprofile1qqszd44fgen4ucpl3hjt7muuaazzqdahp3lwu9c07phdweelcdxf3ugpz4mhxue69uhk2er9dchxummnw3ezumrpdejqzyrhwden5te0dehhxarj9emkjmn9qyv8wumn8ghj7un9d3shjtnndehhyapwwdhkx6tpds34hd6x nostr:nprofile1qqs9phjf9nl9guj9phc6q9m0makezh5hedwelrf7enhh6f0lp2y8rhspr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujuum5dahx2u3wvdhk6atrx4p

nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgawaehxw309a5x7arjd9nksarwdamjumn0wd68yvfwvdhk6tct9vymn 🤔

I have transitioned my status from 'Amethyst maxi' to 'NIP-02 assassin' for this very reason.

Would Amethyst consider implementing the upcoming relay.tools API? In my mind this would create a massive expansion of public relays and provide a new paradigm in terms of exposure.

I want to spin up an instance of relay.tools and point Amethyst at the domain to act as a controller. Amethyst should be able to manage and interface with multiple instances of RT.

Nostr is based.

Fuck yes, and since no one asked, I throw Prodigy, almost exclusively.

> A reaccumulation occurs during a long-term up trend, which will continue in the future. Inside a wyckoff reaccumulation schematic, buyers are closing parts of their long positions and sellers are joining the market. With the incoming selling positions, market makers can fill new long positions again.

https://market-bulls.com/wyckoff-trading-method-accumulation-distribution-schematics/

#bitcoin #wyckoff

Reaccumulation complete.

Welcome to the FUD zone.

Relay.tools API and guerilla implementation of client interoperability with said API

7 years of data versus 45 years of data..

nostr:nevent1qqsgck7ajaapljrkhagpq3phz7k8klc3dqeraq2q20sv4u9tdpe6pecpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsza748zkamgmw4he4hm2xhwqpxd5gkwju38wqh3twmtshx8kv8xvgrqsqqqqqpc70z7s

I, for one, welcome our single-client overlord.

A SuperApp client looks like Nostrudel plus relay.tools

Do not fear innovation, even if it looks different than what you had in mind.

If we all use the same client, then relays become the focal point of decentralization. This is a good thing.

Clients are irrelevant in the face of a so-called SuperApp, and that's okay.

Kind-events are the protocol.

Relays are the protocol.

Users are the protocol.

Clients are just a limited gateway to using the protocol.

If we desire to be limitless then there would only need to be one client.

Nostr is a decentralized SuperApplication upon a decentralized protocol.

Nostr-CLI would never demand a competitor if it is built correctly.

Neither should Nostr-GUI.

I only worry that it may be realized long after relays have been forgotten.

Comparison is the thief of joy.

Bro was faking a heart attack to cover up the theft of your wallet, 100%

🤣 Thank you for this masterpiece

🐂🫡 funny how you always post at the same times when I enter positions 😜

What a beautiful wedding

$43.08

Mutually-assured destruction it is, then.