Ok ok, recently tho

the slowest took 5 days 🫣

00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048

bitcoin, u ok bro?

Not bad!!!!

So many kms (over 35,000) and so much left to see

Currently we're using a fixed set of relays in bitchat which is only a temporary solution. We could let users edit their own relays but 1) users don't know what relays are and 2) if users have no overlapping relays they can't talk to each other.

Here's a solution that we came up with. I'd like to know your thoughts. We're going to crawl a long list of relay URLs every 24 hours. This list will also include their estimated geo locations, also updated every 24 hours. This could be done in an automated GitHub runner.

That list of URLs plus their geo locations will be embedded and shipped with the bitchat app. Users who join a geohash channel will use the five closest relays based on the geohash location of interest.

This solves multiple problems at once:

1) relay centralization

2) privacy

3) speed

4) maybe censorship resistance?

What do you think?

Didn’t see you in there

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqms5cd4pt8xw3m7pnupzmn6z4vc83kv8q5qw3ypqr534x0rc3w3kst2tv6z I can't think of a stupider name

We are all developers now, actually checkout ClipMicro.com it's revolutionary. Uses soon to be ubiquitous TTFS protocol to interface filesystem code with regular AI Chat dialogue.

Why I'm for loosening the OP_RETURN limits ⏎

- In practice, OP_RETURN is already unconstrained: see Carman's OP_RETURN bot or Portland's Slipstream.

- Encoding arbitrary data via OP_RETURN is far more responsible than doing so in witness data, as it's 4x more costly.

- OP_RETURNs are prunable and do not pollute the UTXO set, making them vastly preferable to faux outputs that burden every node indefinitely.

- Mining non-standard transactions that bypass mempools undermines decentralized transaction propagation, disrupts fee estimation, and increases block propagation latency (especially when compact block construction fails due to missing transactions).

- This latency disproportionately impacts smaller miners and encourages direct submission to large, well-connected players, widening the profitability gap and increasing centralization.

- Layer 2 protocols are especially sensitive to fee miscalculations, making transparent and measurable fee behavior essential to their reliability.

While I share the distaste many have expressed toward tokens, inscriptions, and BitVM (when used as a casino), I care deeply about minimizing harm to bitcoin’s base layer. Allowing larger, standardized OP_RETURNs is a pragmatic step in that direction.

It's it not?

#GM

🤙