Avatar
frphank
47be0b2a89faaa66bc57f5c679203486da45660295cb3db3c2f38f4be8d8816e
Autopoietic. Scratching things from chaos. Homesteading the noösphere. Opportunity farmer: Reading things that are not yet on the page. Haskell. Dollars only, thanks.

You have a lot of frequent flyer miles. Do you have insightful opinions, too.

It's the only controversy you got. Literally no one else responded to your call.

Replying to Avatar fiatjaf

this is what happens in the future if the "outbox-is-broken-let's-use-smart-proxy-relays" people win:

- people start relying on "caching services" to fetch their notes. now every client must run their own caching service to remain competitive.

- as the network grows, syncing from all relays becomes more and more prohibitively and databases grow to the infinite.

- less and less caching services exist, but a "local best scenario" would be if we had like 4 different clients/caching-services to read from, but then if one of them banned alex jones that would mean 25% of users lose access to alex jones. there is nothing alex jones can do to change that.

- users could switch from app A to app B that hasn't banned alex jones, but app B had already banned donald trump, so that move is questionable and uncertain. anyway, it's too much friction for a user who doesn't know how to find this caching-service setting buried deep in their settings (because UX specialists said that's the best place to put it).

- eventually it makes no sense to switch anymore and as one of the caching services gains more market share they merge with the others, saving costs and regulatory burden (these caching servers are so big they need to do spam moderation, find and delete pornography and scam bots, comply with government takedowns, defend themselves against lawsuits, it's a huge cost), so it's much better to just have a single caching-service.

- everybody still publishes to their own relay, so nostr becomes exactly like bluesky and the central service can censor anyone. eventually people give up the stupidity of using intermediary relays and just publish directly to that central service.

- that central service now can serve you ads and blue checks, shadowban everybody who doesn't pay, modify your feed with amazing AI techniques to keep you engaged and prevent you from seeing anything they don't want you to see but keep you nourished with memes.

nostr:note1h0un80snqg99yj35rxrpzuc6p2xq0de2589seayexhfa9nc4jkhsx09c5y

I laid out my reasons in this recent thread. Somehow you missed out on it.

As for the nostrpedia ah that's too much effort feel free to do it yourself.

nostr:note1zp6kj383zwsdvap3uhdv7c23tyvxdvg2s770thme7zhxey6qa03qqsqwec

You don't have to constantly rethink it, as I wrote you can create some software UI on your end that automates this. Like a rules engine. Example: Automatically re-post all notes with a certain hashtag until the rules gets manually canceled. However that's something that's strictly on your (sending) client end and don't need to concern the relays or receiving clients.

As for replies in threads, the sending (posting) client sets the expiration date but it's up to the relays and receiving clients to interpret it. It's more like a hint than a mandate. We can't mandate deletion anyways we've had that discussion. So a relay could keep expired notes around if they're required for thread integrity, but receiving clients should highlight the fact they're expired e.g. by graying out.

We need to arrive at some set of conventions across the ecosystem.

Existential dread got you down? Stack Bitcoin*!

* If symptoms persist, stack even more Bitcoin!

Weeding out the losers. What took so long.

You're asking too many questions. Bitcoin isn't about questions. You stack it. You hodl it. You do as everyone else does. The bigger picture is left to someone else. Who are you even.

If you're in the minority we'll that's too bad then really isn't it.

THE WAY THIS WORKS ON NOSTR IS YOU JUST WRITE IN ALL-CAPS THAT'LL PROVE YOU'RE RIGHT

That's right Bitcoin needs to change let's merge PR 29778

https://github.com/bitcoin/bitcoin/pull/29778