Yeah I'm also unnerved by that. I can be convinced OP_CAT is safe but trying to activate it before or soon after the incredibly safe CTV seems insane. CTV does so much for us without opening up pandora's box...

There are several different covenants proposals with different complexity and flexibility. CTV is the simplest and least powerful covenant proposal.

It's basically the same, except imagine the difference for users between "I couldn't buy in to Bitcoin because it was congested" and "I bought into Bitcoin but now it's completely stuck because it's congested".

Plus, with L2s like lightning, you need to be able to get your "corrective" transaction on chain within a certain time period, otherwise your channel partner could steal. (You need to get your Penalty transaction in ln-penalty, or update transaction in ln-symmetry confirmed)

I'm pretty sure at least *specifically* with channel factories and timeout trees + lightning, it's not much of a concern, since your channel partner's attempted theft would mean unrolling part of the tree anyway, they actually shoulder most of the fee burden in that scenario, so they have incentive to continue behaving. (Don't take my word on this, I've only half thought it through)

There might be other constructions that create a greater risk though.

The only thing I'm really aware of is the "thundering herd" where you have, for instance, millions of people who have vTXOs who want to get on chain all at once. I think I'm comfortable that it's at least no worse than the status quo where we can't even attempt to serve that many people, but maybe it ends up turning into a "trap" that reks a bunch of people?

I totally agree about unintended consequences, but CTV is so simple I'm pretty confident there's nothing to worry about. It's the simplest possible covenant I'm aware of.

CTV enables coinpools, giant channel factories, Ark, and timeout trees. Each of these offer 10x-1000x scalability improvements (with different tradeoffs). The good news is we don't need to handle billions yet, but CTV gets us close (or maybe over!) the first Billion.

Does anyone following me have a technical/incentives concern with CTV?

Who marked it "Intolerance" ? lmao

You'll have to let me know how you like Damus, I keep hearing good things but I don't have one of them eephones

Have you looked at https://github.com/braidpool/braidpool ?

It's not a substitute for Sv2 but it's an interesting p2pool revival.

Most people vote for what they're told to. Democracy in a mass media world is effectively rule by manipulation.

Seriously. CTV is upgradeable, too. Jeremy Rubin has already presented one upgrade, Rearden has proposed a different one. I feel like we can get really, really far with upgrading CTV before we need to consider anything more complicated (and dangerous).

(Of course it's trivial to create dangerous CTV upgrades, but the way CTV works make new upgrades pretty easy to reason about and identify dangers)

Phoenix literally Just Worked for me (until they ran screaming out of the US market...)

Nevermind, it stopped working again, curious.

nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qguwaehxw309a5x7ervvfhkgtnrdaexzcmvv5h8gmm0d3ej7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3vamnwvaz7tmjv4kxz7fwd4hhxarj9ec82c30qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgssvm5vj Any idea why I need to nuke all of my local coracle "data" sometimes? For instance I had half written a bug report about the search bar when I thought I'd try this real quick, and it fixed it, and this isn't the first time.

I assume my browser is caching part of coracle when it shouldn't?

Makes sense, I'm targeting native first so sqlite is what I'm interested in.

Right now my nostr app is a side-project-for-when-my-real-side-project-is-annoying-me so it'll probably be a long time before I get around to it, BUT if you don't beat me to it, I'll provide some benchmarks for sqlite at least.

Whoops, last one is 2018, regardless.

> my points were all objective and yours are all subjective, you didn't deny my criticisms

you were talking out of your ass and making shit up, verifiably.

As for subjective things like performance, any claims of performance problems ring completely hollow when I run my instance on a tiny underpowered VPS and it runs circles around every nostr client I've tried.

> you just let it slip your bitterness and resentment against Nostr

I don't hate nostr. I want nostr to get better, and I said outright I think it can.

I'm annoyed because nothing you said was true and you accused me of "bullshit".

The search and remote interaction points are verifiably wrong. Here's some screenshots in case there's a third party confused who is "bullshit"ing and who isn't.

These features have been present since 2017. Here's a github issue about search from 2017 that establishes search was present before this PR was submitted. https://github.com/mastodon/mastodon/pull/1582

Here's a PR for remote following from 2017 https://github.com/mastodon/mastodon/pull/898

Here's a PR for remote interaction with individual posts from 2017 https://github.com/mastodon/mastodon/pull/8202

There's receipts, now please GTFO my notifications.

everything you just mentioned is as bad as or 100x worse on nostr

> reply and like counts where always wrong

10000x worse on nostr are you kidding me? There isn't even a canonical version of a thread to know if the count is correct.

> threads never loaded completely

same, except you'd never even know on nostr.

> everything was slow as hell

Maybe *only* 100x worse on nostr

> DMs suck

Nostr DMs weaken the security of your key dude

> no search

Factually incorrect, even in 2017.

> following people if you had their name/address was often cumbersome

Allow me to introduce you to non-human-readable pubkeys for identifiers

> sometimes you're just browsing on other servers, not your home server, for some reason, and there is no way to go home so you can interact

That's wrong, there literally is an "interact on my home server" button. But that's an admittedly clunky UX.

And in closing, mastodon is not the only fediverse server software. Pleroma is what I recommend, with the soapbox frontend. I genuinely have no idea what instance you used, or when, my only conclusion is it was misconfigured. Even in 2017 mastodon's UX was far better.

It's (mostly) not inherently better, it's mostly a maturity issue. The current version of the fediverse has been around since 2017.

My preferred fediverse UI will be coming to nostr eventually via nostr:nprofile1qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcprfmhxue69uhhyetvv9ujuumgd96xvmmjvdjjummwv5hszxthwden5te0dehhxarj9e3k76twve6kuepwv9c8qtcqypuu9jhpzn4z32vpua2eknl8s49ywdfp4rfz5e4m4w06yj8tsg8lvxxqdcn although I think there's a primal-style intermediate server involved.

Most of the more "inherent" problems are solved by some kind of intermediate caching server (local relay might address this). I really don't like the way most clients seem to fetch everything and keep very little state, notes end up loading slowly, out of order and popping in.

markdown notes are great on fedi, I hope they will also come to nostr (there are already markdown kinds, but I'm not sure if there are any markdown "note" kinds)

discoverability is just awful on nostr, feels like I'm shouting into the void here, I'm shadowbanned on twitter and have better reach, and far better than either on fedi.

the instance model in the fediverse has some nice benefits in community, discoverability, moderation, but there's downsides too, obviously.

silly thing, but the fediverse's custom emojis create fun for people (and fun matters).

That doesn't add up to a million x but I hope you'll forgive the hyperbole lol

I think I'm bullish on nostr long term but things are still rough imho