Avatar
Code
80c08670361e4f7420349e5d4281b30a065fde6254489f1c255b4601f40fa85c
I lurk and I zap.

I wish NOSTR allowed me to take zaps from you. Gay.

Replying to Avatar _

Are you?

Oh absolutely not. Are you not then? You're just virtue signaling from the sidelines?

Sure feels like an old elite faction is trying to push a civil war in the United States but what do I know.

Prayers for Charlie.

Wait a sec, I thought GrapheneOS was Pixel only and I didn't think Pixels supported video out. Interesting.

I'm learning as I go. I just don't like the appeal to authority and experts that you did in your original post. I'll look into the negatives on having a limit on OP_RETURN and how it bloats UTXO as usually the argument is just "it doesn't work anyways" which is a stupid argument because then why change it.

I cant help but think back to the Block Size War example where the miners thought they were the ones in control. Turns out that wasn't the case.

I guess it's time we find out if Core devs are the ones in control.

I just have to say that the exception doesn't make the rule. Do you think it's stopping nothing at all right now?

Did I misunderstand your original post? Are you for or against Core's potential move to remove the limit on OP_RETURN?

I'm not the cash guy here. You support Core's move towards removing OP_RETURN or not?

Do I get to decide what goes into my mempool on my node or does Core get to decide that?