I’ve never heard anyone get as mad about the existence of nostr as Dave Jones (Adam Curry’s partner in Podcasting 2.0).

It’s bizarre.


What did he say? Something recent?


curry seems triggered by zaps as well, it’s bizarre. I don’t see them as competing or anything so i don’t get it.


Curry is a fucking wack job


i've noticed some chinks ....jones/curry


Their subconscious is threatened for whatever reason. Relevance, status, edginess whatever? Fuck em


Strange because he IS zappable, though he hasn’t been active on nostr for months.


Also interested.


Does it have to do with his love for RSS and Nostr being a competing technology down the road? Possibly?


It's because they're building a new podcasting platform on ActivityPub.


I haven’t heard what you’re referring to so I’m just guessing, but having interacted with him a little bit on the Fediverse, I would suspect he has time and money invested in a different direction. And if true, he feels it’s threatened by nostr. And he is probably right about the threat.


I don't get it...and I came to Nostr from the Podcasting 2.0 side of things with a love for protocols and decentralization! There is such potential for interoperability between the two with things like Blossom. 💜


oof


They should swallow the hard pill and pivot now.


They keep saying that every one on nostr wants to replace podcasts and RSS. I’ve only heard a few people suggest that and it’s dumb. I like RSS but don’t see nostr as a replacement. I don’t get why they look at it the way they do.

I suspect a deep and fundamental flaw in what they think nostr is and I don’t know how to correct that.


It's a threat to what they're building, by people who chose to take a different route than the one they were already traveling. I'm not surprised they're salty about that. ActivityPub itself is basically RSS.

Just give it time. People will come around when they realize it's here to stay, and we give them an easy path to join us.


imagine if we bridged nostr with all activitypub/fediverse instances like funkwhale, peertube, etc... i bet he'd be stoked. two networks of people now able to talk to each other in the comments and use whatever protocol they like best... :)


Activitycuck


i already did that, it's called cast.garden and includes more rss in its subscribe features than any other podcast host in the world. runs on peertube too so that should make both those guys damn happy.


you could build a site that reads podcast notes and serves them statically as rss. nostr subsumes rss and enables realtime use cases


Cry harder.


Imagine being angry at freedom technology?


That’s exactly the way I’m thinking about it.


I’ve never heard anyone get as mad about the existence of nostr as Dave Jones (Adam Curry’s partner in Podcasting 2.0).

It’s bizarre.


In this episode. Right up front.

https://fountain.fm/episode/6VnEZGZHoeqjtOQsjNCe


It’s already confusing to non-tech* me as he said it on Fountain. ⛲ hmm 🤔

*but actively educating myself on history so I understand more. 😊


some ppl hate freedom. especially those whome profit from our servitude.


Or maybe we should prove them correct and start to take on that functionality.  If we are to be accused, then we have the right to do it. 😛


Thanks for sharing this.


I love what they’re doing with podcasting 2.0. I wish they’d build on Nostr instead of activity pub.


I do use RSS, HTTP, and email as analogies for how it works, and I see nostr as an alternative to a lot of what they both did and can replace some functions*, but it has more to do with replacing a lot of web 2 (social media, cross domain, authorization, etc), and explands the realm of opportunities (unmediated identity persistence, data ownership), but not as much web 1. We'll still have email, websites, news feeds/podcasts, etc.

Currently, we largely use HTTP as a medium for the nostr protocol, but I envision a day when we don't.

*imagine never again giving your email in exchange for a discount or an e-commerce customer account and sorting through canned marketing emails to get to the important communications!


On top of that, every few episodes they complain how reliant the whole value for value system is on Alby, but they also get triggered by NWC which would allow podcasting 2.0 apps to easily connect to other wallets.


there is nothing wrong with RSS. it has served us well for nearly 25 years. but there are several points worth considering. for this example, I will specify a static html site, something like that generated by Hugo, where the author writes markdown, compiles the static files (including an RSS XML), and then publishes them to a web-server.

RSS:

1) is based on polling, which adds a non-zero cost to the host in having to handle a constant barrage of requests (assuming some popularity...), and also requires that the source be online to serve the content. obviously there are ways to deal with all of this, but the naive setup leads most implementations here.

2) has a limited capacity. in order for a subscriber to have access to content that is not included in the XML, some other means is required. hence, we end up with centralized solutions like feedly and the like. again, this is not a huge problem, as the content of the XML can be limited to URLs and descriptions. a standard approach to RSS implementations is to only include the most recent n items.

3) has a single point of failure, the file server that returns the XML, which is probably the same server that makes the deep linked content available as well.

4) leaves many traces indicating one's interest in the content. there will be a DNS query for the domain the XML is hosted on, and more queries for retrieving the content.

again, these are not horrible tradeoffs for something so valuable, and I use RSS every day to great effect. but #nostr brings some interesting features to the table to address these points. the equivalent in nostr would be an npub that publishes the same markdown files that went into the hugo implementation as NIP-23 Long Form notes.

1) push-style delivery. near-instantaneous delivery to clients with open connections, piggy-backing on network connections that are already there (assuming you are using nostr for anything else).

2) capacity is hard to compare directly since they are different modes of access, but assuming you are reading notes via a client that supports it, you can query the indicated relays for any other long form notes from the same npub to see all content previously published, rather than relying on only those items which are present in the XML.

3) the long-form notes that make up the content of the nostr version of the feed could just as easily disappear, or be published to a single relay only and forgotten, but much more likely is that the notes end up on several large nodes, and get spread hither and yon from there. and since the notes serve as notification AND content, being notified of content and having the content are the same.

4) again since the note contains the content itself, the only traces available to the networks you are traversing to talk to relays are that you connected to a relay, not which npubs you searched for or were delivered.

I'd like to know what you think the "deep and fundamental flaw" in what I'm saying here is. there's no magic, just better mechanical sympathy between the use case and the implementation, in my opinion.


It’s about money. It’s always about money.


Why is as he mad?