The reason why algos can't see that conversation, is because the OP doesn't contain the signal, the thread does.

In fact, social media algos _actively discourage_ human interaction. That's why influencers quickly learn to game the system by refusing to respond. If they respond to someone, and that person responds to them, the discussion thereafter is "invisible" to the algos. All of the responses have to "hang" on the OP.

nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 nostr:npub1fd0t73r8vn3nqezdg93fyj5x5u79zucf3jaspkc2dy9sjuqx5z8qftjal4 nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf

Reply to this note

Please Login to reply.

Discussion

Algostore fixes this

#notedeck

Algos can only surface high signal.

You can't publish **in** them. You can only try to implicitly hack your way into them.

This is what interoperable communities fix.

Both are upgrades over the influensooor loop!

Customer set algos 🤝 communities

my nostr algorithm sees this

I'll provide a parameter to weight mentions in a kind 1 higher than reposts and reactions. I don't even account for zaps at all

it's been a while since I've looked at the NIPs, but I believe all replies mention the root, so that activity will all acrue to the ranking of the root post and it will bubble up

I personally don't care for nested conversations, but the nostr algorithm can be taylored for your use case