Prediction: to compete with proprietary nostr relays, others will have to build their own proprietary apis to deliver similar value. People will stop caring about interoperability and nostr just becomes isolated twitter-like islands just like before. Most clients then become light clients for these proprietary relays, and users lose control over which relays they can choose to talk to.

This is starting to happen today, how do we prevent this? VCs and people trying to make money won’t care about the hard work of protocol dev and interoperability, in fact, its in their interest to explicitly make it harder for other clients to have similar functionality via protocol improvements.

nostr could go down a very bad path very soon. Which way do you choose anon? Give up on the protocol for shiny new features? Or support less featured clients focused on interoperability? I suspect most will choose the former 😔

Reply to this note

Please Login to reply.

Discussion

outbox fixes dis. or does it? we wont know till 2/3 the network using it..

I'm curious about that too—specifically does outbox make sense in a fully-cached context? As I understand outbox is for selecting the right relays for the right people, but in a fully-cached context the "right relay" is only ever your cache service. Or is it maybe that outbox can be used to more efficiently fill the cache? Or would you even care about efficiency if your pretty much indexing everything anyway?

outbox is for clients who connect to relays, im talking about clients that don’t even talk to relays, which happens to be the most popular client at the moment, and probably most clients in the future if this model wins.

can’t wait to ship outbox in notedeck this month! had to spend a year building the tech to support it but will be worth it.

my time preference throttle is like an ipod circle dial

damus+notedb+outbox retrofit will tip the scales to outbox. im here for it! 🌝moon

💯

#Alexandria is using outboxes, already. Decided to just start off, that way. Skip the bullshit.

All devs are guilty of creating off-protocol implementations.

But we should leave non-nip approved implementation in beta software.

Because at this stage Twitter can claim they are running nostr now (with their current implementation).

😔

I think the solution is twofold: improve the relay API, also implementing HyperLogLog suggested by nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6, and promote more creative client-side business logics, with custom storage layers that can be used to optimize data aggregation and filtering.

agree

I really want something like HyperLogLog to happen

I've started noticing a lot of notes missing from my follow feed in recent weeks. I see them when I visit a profile but they never make it to my feed. I suspect that is related. I don't know a damn thing about programming but I'm pretty okay at pattern recognition.

The Proprietary Nostr Relay Wars 🫡

Maybe it’s a funnel thing, like Bitcoin itself? My hope is that in time and with understanding people will migrate from the shiny to the ethically sound, principled clients that share their values and better defend the decentralised vision of the movement. But the hard path will always be harder 🫂

Build out interoperable solutions, reject proprietary solutions entirely.

Is this a more serious risk if clients with traction stop writing events to outside (as opposed to reading events from outside)? I see that on the read side this introduces risks like seeing content that is out of date, or in the worst case purposefully altered.

Or is it that the read side alone comes with its own potential implications?

> or in the worst case purposefully altered

Fortunately this is not possible, events are signed.

But a blocked/delayed sync could effectively be a dark tactic from a client that has a large userbase.

Ah yes, I was thinking more along the lines of counts and such that a client can only achieve with some kind of central-server model, and that users would therefore be trusting the client on (seeing as they can't get such accurate counts from the protocol itself.) But I didn't think about blocked/delayed sync for notes themselves as a dark tactic, that's an interesting thought.

Where I'm a little confused still is why this cacheing sometimes seen as a looming threat to the model when it's just on the read side? I'd totally get it if it was on the write side too, but if just on the read side then it seems to be benign enough, like watching live events streamed on YouTube but things being buffered a few minutes for smoothness.

Users always have to trust clients, they don't have the other way.

For reactions/zap/replies at protocol level, we are evaluating HyperLogLog (see https://github.com/nostr-protocol/nips/pull/1561) that seems to be a good (probably the only) solutions to an aggregate counting in a decentralized structure. There are risks about gaming the system, but they can be attenuated; therefore, they are already present today with a plain sum of events done by clients.

The reading cache is not only a cache, is potentially a totally new API abstracted on that data, probably with more processing (e.g. extracting images/videos data, text metrics, etc). This off-protocol approach gets from the network, but doesn't give back nothing, and so it creates an unfair competition since casual users that don't know these technical details see these off-protocol clients as a better choice, ignoring that they cannot exist without the protocol devs that hardly work every day to create a interoperable standard. They also don't know that they aren't Nostr clients at all in the strict sense, since they lost all the decentralized ability (if the API server goes down or is censored, the client is dead).

Very enlightening, thanks!

Dark thought

Why would devs do the hard thing and pour their effort into getting something working at the protocol level thats already available by some popular proprietary nostr app? Especially when they have the majority of the users and they are happy with the solution.

The very few people doing protocol dev will stop doing it. Users will be like: wow you got something working in a janky way which we've already had two years ago on NostrGram, who cares. It's becoming not very rewarding work.

You could have easily built zaps in a way that worked only on one app and all the users used that app because its an awesome feature. Building zaps was non-trivial and required lots of work between many different parties. It's sad we're moving away from this way of building things.

Where is this happening now?

I’m just adding local nip50 search support to damus clients, but this looks like a toy when compared to primals advanced search which you can’t really do on the protocol at the moment. So when i launch it people are going to be like “lame, we already had this on primal”. So unless I do something proprietary or spend the next 6 months trying to get advanced search into the protocol, then proprietary clients will always win.

My only conclusion is that clients will start competing with each other using off-spec advanced features, which means that you won’t be able to build a pure client anymore. Then nostr fails.

The primal advance search is not just a filter?

Or is a filter something we can’t do right now?

It filters based on min zaps, excluded words, and things like that, you can’t really do that without a custom relay as relays aren’t really supposed to know about zaps.

nip50 was nice because it standardizes fulltext search, so i could make damus local search compatible with relays. I can’t really do min zap advanced search “properly” without a relay nip, but i can hack it with nostrdb at least, and just try to pull down as much data as possible.

Oh you mean you can’t send a REQ with this level of detail.

i thought they were pulling what they can pull at the level the relay can understand from a REQ and then applying the filter on client side.

or at least everyone else can do that. I thought that’s the idea of having a local relay and a DB. You can cut slice and filter as your please, no?

You can do that but it wouldn’t be very efficient and you would get fewer results, and wouldn’t scale. They will have to do it on their relay if they aren’t already. We can do it locally but there is no corresponding remote REQ we can execute to get the data. Maybe just negentropy syncing all the zaps for the day would work well enough for a little while.

It's so insane to me that an primal has users. They were requested to implement amber 1 year ago and still haven't, meanwhile 75% of new android apps implement within the first month of release.

Are you thinking that they have a DB that is storing as much notes as possible for search or what?

It's time to implement the "green chat bubbles". Not sure what that is in this case, but users of misbehaving clients could be made aware by their followers "hey, this thing you shared looks weird on my proper nostr client" instead of compensating for broken compatibility.

What I'm still not convinced of is that proprietary nostr clients / ecosystems make much sense as a business model.

Twitter can barely survive bombarding people with shitty ads. How exactly is Primal supposed to make a profit?

This is also my question.

I don't have a problem with proprietary tech or platform building on Nostr.

Many proprietary business can be build on this huge transparent and verifiable dataset. AI and LLM is one example. Search is another one. As long as this dataset remains open and not a walled garden, proprietary technologies built on top of Nostr will not signal its decline — quite the opposite.

I'm thinking somewhat along these lines too. I feel like the protocol, even in its earlier stages, is enough to enable some fantastic and scalable use cases. If the protocol doesn't need to further develop then clients can't so easily be accused of siphoning off development resources from the protocol in a zero sum game.

The problem as I see it is that Twitter-style microblogging, or what they call "Big World" over at ATprotocol to emphasise the consistent global view, isn't one of those use cases. If the end goal is to be at least sort of like Twitter (plus censorship resistant, etc.) then the protocol will always be demanding of more resources, as we'd basically be asking magic of it, and the zero sum game would continue to be played day in and day out.

It's a tough one though because Big World microblogging is part of the founding ethos of Nostr, and even if it turns out that Nostr unlocks a alternate use case, and that use case is glorious and successful, it might still feel a little like things went off the path.

you're right on this

this is nonsense: https://nostrapps.com/

let's come together

shiny fades fast ime & all the best guys*/ i applaud U for a lot of this space so far-T Y

all the best all*/

Disagree. Incentives in a commoditized open source market encourage cooperation/interoperability due to everyone desiring network effects from each other. Siloing is stupid for VCs.

I’m a Damus Maxi.

Tried Primal. Didn’t like Primal. So fuck Primal.

Keep it simple. Damus & Wallet of Satoshi = happier better life.

People think im doing this to shit on primal all the time. Im so tired of this fight and its not my point. Im thinking about what would happen if certain ways of doing things took off and how it might affect the network. My beef is not with primal specifically, the point is the next big VC funded app with 100 devs could do this and it would amplify the badness by a lot

Primal is the canary in the coal mine. It’s good to call them out as the example. And the app sucks. At least on iOS.

I have never lost a canary in any of my coal mines.

I talked to miljan last week and he said hes aware of the concerns. I suggested a degraded experience when the caching relay is down and still let people read from their relays. I think they will need to do it for a good experience unless they can scale their relay somehow and make it more redundant.

I made this in July 2023.

It has turned out more true than I thought

This was before any of the Primal drama, btw.

So I go Primal Island. If they do something I don't like, I find another island. But I can vote with my feet and find a new island. Seems ok to me.

Until your island floats away. That’s the point.

Now beat it.

k. Good talk.

Replace Primal with Twitter in this post and the meaning is the same

👆👆✅

primal's interface is ugly af

also, it's quite notable that i almost never see people replying to miljan in my feed... funny that

Is he the Nostr CEO? Very profitable I hear. 👂

i'm sure they got plenty of runway to shut this down

and also, damus is pretty smelly too, where did all that funding come from

🧐

I'm not well versed in the area at all.. how can you tell what's a protocol feature vs a client implementation?

Just use Damus. ✅

I'm on Android..

Then just use not-primal.

#amethyst

👆

it’s weird there is less fucks given about this issue. I suspect most [users] don’t actually grok the potential reality and the reason why the primal model i so suboptimal.

Shilled as easy onboarding for adoption. It’s almost fiat. Path of least resistance. Most people do not consider the sacrifice made for convenience. This has been clearly demonstrated over last 15-20 years unfortunately

I try and get attacked for it. Just gonna give up. Seems like the number of people who care about this is dwindling by the day anyways.

Please don’t give up.

Says TKay as he responds from his Primal app 😂

Lol

if only you knew how I nostr lol

🧐🤔

go to notedeck folder >

right-click run ternminal >

git pull >

cargo run --release

just to support @jb55

The real deal. I knew it. 👆👌

attacked how? with words on a screen? Let them attack then

I hear you. Keep up the good work.

👆👆👌✅🚀

Same, but WoS stopped working for me.

Primal wanted an anal probe / KYC, so I declined. Coinos for pocket change has worked so far.

WoS on TestFlight works great. Anywhere. VPN required.

my setup as well

Dan gets it. 👆💯🚀🔥🥄

thanks for that , new to primal.

Now setup zaps or this will be the last you hear from me or Nostr in general.

it's so over

I choose less featured clients and interoperability #nostr

Interoperability was one of the main things that attracted me to nostr. Without it, there isn’t any point.

Isn't this generally the challenge that open-source software is up against? I think we're only just realizing how much the fiat system has formed our habits. Hopefully more talent gravitates toward the open-source field as mindsets change, but as it stands we still need fiat to play the game. Maybe software developers need to start choosing more humble paths for the sake of human growth instead of prioritizing large paychecks.

There are many investors in the space that understand the complexity & cost of protocol development and believe in the multiplicative effect it can cause. There are investors that are also excited about the technology, the vision, the solution and they like to help good cause. They need to see some hint of path to success, but especially in the early rounds all investors understand that they most likely won't see their money back. Investors can then provide their network of people, help with hiring, help with resources, exposure and marketing, etc. (i.e. provide not just money, but other values too)

Now, you keep putting all these investors into a single bucket of evil people and attack their integrity with posts like this and that's something that investors are sensitive to. Many investors don't share publicly that they are investors and so you may see people in your comments that seem hurt & attacked without any obvious reason. This could explain some of it.

On the specifics - detailed search functionality with complete DSL is imo overrated. The world is shifting to just text and multi modal search anyway. Even if Primal can do better experience because they don't design a protocol solution, it doesn't matter much. If Damus (and nostr) gets basic search, people will be happy enough.

Further, there are examples where one app pioneers a great experience that users enjoy that is then later codified into a protocol. Sometimes the usecases and user needs need to be more fleshed out before we freeze those into a protocol.

protocols will survive by network itself 💜

( i just thinking about damus x slidestr ? )

I think you had too much Whiskey and it’s cold!!!

Bitcoin-focused VCs like nostr:nprofile1qyv8wumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wsq3kamnwvaz7tmjv4kxz7fwvf5hgcm0d9h8qctjdvhxxmmdqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsz9nhwden5te0wfjkccte9ec8y6tdv9kzumn9wsq3jamnwvaz7tmnv4hxg6t59ehx7umxd3shyefwvdhk6qpq4pymadh04lt8tl3lv93yr3vnlxw39s3ahdvmhvlu6u27fve8umfqzmv7st , #Hivemind, and #EgoDeathCapital and actually benefit from maintaining #Nostr 's open protocol and interoperability just like the non-profits like nostr:nprofile1qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzpmhxue69uhkumewwd68ytnrwghszrnhwden5te0dehhxtnvdakz7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uq3vamnwvaz7tmwdaehgu3wd9hx7um5vyhxxce0qyt8wumn8ghj7mn0wd68ytndd9kx7afwd3hkctcpzpmhxue69uhkummnw3ezumt0d5hsz9thwden5te0dehhxarj9ehhsarj9ejx2a30qyghwumn8ghj7mn0wd68ytnhd9hx2tcprfmhxue69uhhqatjv9mxjerp9ehx7um5wghxcctwvshsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qy2hwumn8ghj7un9d3shjtnwdaehgu3wvfnj7qgewaehxw309aex2mrp0yhxummnw3ezucm0d5hxzaf0qyvhwumn8ghj7un9d3shjtnwdaehgunpw35jucm0d5hszxmhwden5te0wfjkccte9ehhyctwvajhq6tvdshxgetk9uq3jamnwvaz7tmjv4kxz7fwwdhx7un59eek7cmfv9kz7qpq0pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqtlazcs do. The network effects created through interoperability generate more value than isolated proprietary systems, as demonstrated by successful portfolio companies collaborating across the ecosystem.

Rather than fragmenting into isolated islands, Nostr is more likely to follow Bitcoin's development model where:

- Open protocols create more value through network effects.

- Technical challenges are solved through collaborative innovation.

- Economic incentives align with maintaining interoperability.

- Venture capital benefits from ecosystem growth rather than isolation.

The key is understanding that Bitcoin-focused VCs operate differently from traditional tech VCs, prioritizing open infrastructure development that benefits the entire ecosystem rather than pursuing short-term proprietary advantages.

Thoughts? nostr:nprofile1qyv8wumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wsq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5qyvhwumn8ghj7um9dejxjapwdehhxenvv9ex2tnrdaksqgqyey2a4mlw8qchlfe5g39vacus4qnflevppv3yre0xm56rm7lveyr9lldz nostr:nprofile1qy0hwumn8ghj7cnfw33k76twd4shs6tdv9kxjum5wvhx7mnvd9hx2qg4waehxw309ajkgetw9ehx7um5wghxcctwvsqs6amnwvaz7tmwdaejumr0dsq3gamnwvaz7tmwdaehgu3wdau8gu3wv3jhvqgmwaehxw309aex2mrp0yhxy6t5vdhkjmnsv9exktnrdaksz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqyt8wumn8ghj7un9d3shjtnnw3hkuetj9e3k7mgqyprj73q098hejm5j5xrt35eqluvqep2eqwyzukw4phsm302kdycpuc8s2gj nostr:nprofile1qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgqgdwaehxw309ahx7uewd3hkcqgawaehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2aqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzemhxue69uhkummnw3ezummwwdshguewdaexwqg6waehxw309ahx7um5wghx7unpdenk2urfd3kzuer9wcq37amnwvaz7tmwdaehgu3wwaskcmr9w3hkvumpw3hhx6rf9e3k7mgpzpmhxue69uhkummnw3ezuamfdejszxthwden5te0dehhxarj9eax2cn9v3jk2tnrd3hh2eqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3gamnwvaz7tmjv4kxz7fwdehhxarj9e3xwqgcwaehxw309aex2mrp0yh8xmn0wf6zuum0vd5kzmqpr9mhxue69uhhyetvv9uk2u3wve5kzar2v9nzucm0d5qzpqlgrr0man8226c0252hdvla8xn62rsas9vngdgqx686ppwvm9jthez2l5 nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcp2amhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0dec82c33wv6hjufkwaskgamj0pjx2drvdpn8xdfkvahrvdrgwaa826rwvesnvu3ed44rgdekwg6hxdrgdd6ku7n80fchyuekwymh5qgwwaehxw309ahx7uewd3hkctcprpmhxue69uhkummnw3ezuendwsh8w6t69e3xj730qy2hwumn8ghj7mn0wd68ytn00p68ytnyv4mz7qg3waehxw309ahx7um5wgh8w6twv5hszxrhwden5te0wpex2mtfw4kjuurjd9kkzmpwdejhgqg6waehxw309ac82unpwe5kgcfwdehhxarj9ekxzmny9uq3samnwvaz7tmjv4kxz7fwvd6hyun9de6zuenedyhsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qy2hwumn8ghj7un9d3shjtnwdaehgu3wvfnj7qgewaehxw309aex2mrp0yh8xmn0wf6zuum0vd5kzmp0qythwumn8ghj7unnwdkxz7fwdehhxarj9ehx2ap0qqsg2zqd8wkhpnxu6lm5c2dyfa2mhpwte57apjae2ldp6g2mmwf3ypqdsk0y0 nostr:nprofile1qy2hwumn8ghj7mn0wd68ytndv9kxjm3wdahxcqg5waehxw309ahx7um5wfekzarkvyhxuet5qyf8wumn8ghj7ur4wfcxcetsv9njuetnqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsz9thwden5te0wfjkccte9e4kzmts9eekjar9qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqpzdmhxue69uhhyetvv9ukzcnvv5hx7un8qyg8wumn8ghj7atn9eexyu3wvf5k7qpqa2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sw8fdg3 nostr:nprofile1qyshwumn8ghj76mdvvkkummnw3ezuctdd96kuer9wfmkzar9wghxxmmdqy2hwumn8ghj7mn0wd68ytn9v9ekjene9ejx2qg6waehxw309ahx7um5wghx76mpd968xde4xv6zumn9wsq3yamnwvaz7tmsw4e8qmr9wpskwtn9wvq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7qghwaehxw309aex2mrp0yhxsctndqh8xarjv4sk6qgkwaehxw309aex2mrp0yhxummnw3ezucnpdejqz9nhwden5te0wfjkccte9ec8y6tdv9kzumn9wsqzq079lp2n40t48tz8je7yc35vl5yw3juaaecm08sj6kk6kgzmcpxnv67gq3 nostr:nprofile1qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qyvhwumn8ghj7er9wfnkjemf9ehx7um5wgcjucm0d5hsz9nhwden5te0v4jx2m3wdehhxarj9ekxzmny9uq3yamnwvaz7tm909jhxtnxxaazu6t09uq3samnwvaz7tmxd9k8getj9ehx7um5wgh8w6twv5hszgrhwden5te0dehhxarj9ejkjmn4dej85ampdeaxjeewwdcxzcm99uq32amnwvaz7tmwdaehgu3wdau8gu3wv3jhvtcpz9mhxue69uhkummnw3ezuamfdejj7qgcwaehxw309ac8yetdd96k6tnswf5k6ctv9ehx2aqprfmhxue69uhhqatjv9mxjerp9ehx7um5wghxcctwvshsqgrwg6zz9hahfftnsup23q3mnv5pdz46hpj4l2ktdpfu6rhpthhwjvxnknlz nostr:nprofile1qythwumn8ghj7enfd36x2u3wdehhxarj9emkjmn9qyxhwumn8ghj7mn0wvhxcmmvqyw8wumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctvqy8hwumn8ghj7mn0wd68ytnddaksz9rhwden5te0dehhxarj9ehhsarj9ejx2aspzpmhxue69uhkummnw3ezuamfdejszynhwden5te0wp6hyurvv4cxzeewv4esz9thwden5te0wp6hyurvv4ex2mrp0yhxxmmdqyvhwumn8ghj7urewfsk66ty9enxjct5dfskvtnrdaksz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpzfmhxue69uhhyetvv9ujue3h0ghxjmcpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qz9nhwden5te0wfjkccte9ehx7uewwdhkx6tpdsq3gamnwvaz7tmjv4kxz7fwdehhxarj9e3xwqgkwaehxw309aex2mrp0yh8qunfd4skctnwv46qzxrhwden5te0wfjkccte9eekummjwsh8xmmrd9skcqglwaehxw309aex2mrp0yh8xarpva5kueewvekxzumgv9c8qtndv5q35amnwvaz7tm5dpjkvmmjv4ehgtnwdaehgu339e3k7mgqyqqqqqqpl3fzghfd49sqnd5z06yk6kp7u5vf4cn9p80ha3g7tmkjz994umk

nostr:nevent1qvzqqqqqqypzqvhpsfmr23gwhv795lgjc8uw0v44z3pe4sg2vlh08k0an3wx3cj9qqsppr6l7vnvxxk63ec0mhqhmr28q90g67ujww740spcje56hr75k0s7a5drw

What are the highest value features that are moving to proprietary nostr relays?

I support whatever keeps Nostr FOSS and growing too big for Elon to buy.

interoperability above all! 💜

that’s one of #nostr best feeling of #freedom

Exactly 0 shitcoins have ever killed Bitcoin.

Exactly 0 shitcoins will kill this protocol.

It's all about the money. You are probably among the very few having a stady income throug donations, but many who built are not that lucky.

People just want to earn something and honestly I don't think zaps is the answer. I am not even go into the nips which some are are insanely complicated.

The focus must always be efficient but stupid relays, I think that should be a core principle for Nostrs protocol when defining nips.