If you want Bitcoin to work differently you need to provide a design solution that prevents this behavior. Filters and OP_RETURN limits do not prevent this use case.

Incorrect.

What is exists is what is enforceable.

If you can understand, so can they.

Ironically, the main purpose of the BIP is to correct this misconception. Base units are not divisible and millisats do not actually exist (look it up)

I am not one of those people. I feel clowny saying "sats".

there was a time before "sats"

It's this way because of the formal feedback that was given about the BIP. So I acknowledge that stock tickers are rationally an external spec.

x.com

it's photoshopped you shouldnt believe me

read what you just wrote as if you were the crazy one and see how much more complicated yours is

for example

I understand that you think dropping the name bitcoin from Bitcoin is realistic.

You're welcome! :)

I'm sure he's a great guy IRL.

Take a look at the details of the BIP. The core intent is to correct how bitcoin is displayed due to people misunderstanding it as supporting floating point while it is actually integral.

Ready when you are!

LNURL connect works, i think there is also manual UI in the settings

You can use Bitkit in the USA, you just can't buy the channel from us. You can still connect to other LN nodes or use onchain.

Well, I would (and we have) certainly include a social graph into the design. It's how you deal with sybil/spam/noise inherently (WoT).

Whether to call it "follow" or connect or such matters less when you can also semantically tag your contacts as a another dimension for grouping a filtering URLs.

If you lose followers you are losing relevance (or the platform is).

Optimizing for followers is a generalist/popular approach, but specialization is what is valuable. So, I prefer attempting to design ways to connect users with the URLs they are looking for.