Five

I am a podcast addict. And as my time is becoming scarcer from multiple aspects, I must curate and prioritize heavier. The only pod that I immediately listen to as soon as it ships is nostr:nprofile1qqsfhhjzzjgl86k34ssm68gpvea2h9rlfswy4mv8vfx0yfemqm9q22cpramhxue69uhkummnw3ezuetfde6kuer6wasku7nfvuh8xurpvdjszrthwden5te0dehhxtnvdakqzrmhwden5te0dehhxarj9ekk7mgmkwtv0 . Each episode is a unique dialogue that brings me back to SEC02 where my path as a nostr builder was really born. Thank you nostr:nprofile1qqsxu35yyt0mwjjh8pcz4zprhxegz69t4wr9t74vk6zne58wzh0waycpz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309ahx7um5wghx77r5wghxgetk9uq3jamnwvaz7tmswfjk66t4d5h8qunfd4skctnwv46z7kjtacz and guests, especially nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0dv4ph5 ! Keep it coming!

nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgewaehxw309a5xyu3wvdhhyctrd3jjuum0vd5kzmp0er5gcs the latest welshman master has breaking changes it seems like, and latest Flotilla master doesn't work with it. I got it building, linked locally, but Flotilla is complaining about ctx in welshman/lib. What action do you recommend?

Note was too long, so wrote this in up in an article nostr:naddr1qqgxycnyvvuxxepsv56rvefh89jn2q3q6p8v7varqwjes5hak6q7mz6pygqm4pwc6gve4mrned3xs8tz42gqxpqqqp65wn2a53s

The feed problem as nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0dv4ph5 mentioned on several occasions got me thinking lately. Can't stop wondering communities can fix that too. It is more relevant and not global by default, therefore it's easier to implement: - Smarter, simpler algos and search - Non-spammy digests as notifications - Well-defined borders and therefore easier connection with the rest of nostr (whatever that means) - Easier moderation - ... any problem is more soluble that I can think of The only use-case I can think of that benefits from a feed is marketplaces. The user is inherently more goal-oriented and data is inherently less noisy, only contains the bare necessities. So it's still simple to handle, regardless of abundant data. So more liquidity on marketplaces actually makes user choice easier, while more social type of posts from a wide variety users is inherently disruptive to people seeking signal. Social use cases: less is better, from selected people Marketplaces: more is better, feed is justified, don't really care about people just their reputation in the marketplace context Thoughts?

Good idea, good luck to it! Who needs customizable nostr widgets when we can wrap everything in JSON ! Sounds hilarious but it could turn out as sth like nostr itself: a simple yet ingenious idea that changes the status quo.

Some people seem to think that if we make nostr the go-to social media, then somehow the "inherent properties of nostr" will always keep bad things in check. We can all just lay back on the beach and sip cocktails in decentralized la-la land. Sorry folks, that is not how it works. And you know what happens in B-movies with characters like that. Entropy is the default. Stay sharp and keep building.

The benchmark for zapping should be the "zap the devs" feature of #amethyst . #NWC took for ever. I initiated the payment, went for a shower, got dressed and when I looked at my phone it was still zapping. We might want to switch to sth actually working, like Nostr Wallet. I think it could take about 10 seconds at most. #cashu

#Amethyst / #Amber combo keeps popping up windows randomly despite having full perms and checking allow always whenever it asks for new perms. I initially set "trust app fully" at login

The amount of protocol alchemy used in nostr group specs is wild. We truly have embraced chaos. I hope for a sliver of order at this point though.

Reading through Jack's thread makes me realize I need some kind of #wot -based reply ordering.