Guarantee engagement goes up if there was a reverse chron feed in Warpcast. Most of my algo feed is posts from 1+ days ago, I literally can’t keep up with what people are saying on Warpcast.

Even if fewer people use it, I assume getting quicker engagement on casts would help distribute them to algo feeds quicker.

my 2 gwei on this:

reverse chronological as the main feed is actually a really mid take. it only works for a very specific size that's not farcaster or twitter. 

no one should be evangelizing it unless they actually use a reverse-chron client like Supercast for a week or two. 

but. but. but. if we have "all channels", "frames" (fucking frames) and "trending" might as well throw reverse-chron in there just to prove how dead it'd be.

There has been controversial opinions on this reverse-chron feed lately here in FC, some calling it mid-take, some a high-priority...

Despite FC being a dlt protocol, I agree that Warpcast is by far the most strong client & that features released on other clients aren't as effective as they being a Warpcast feature.

But, but, I believe in the long-run the best option would be having a:

*Custom No Code BPMS-like Timeline Builder*
- either as a standalone (hopefully Opensource) client
- or via a browser plugin, well-pluggable to multiple clients
- or  hopefully on Warpcast itself.

There are non-technical elements involved in losing that power into the hands of end-users in Web2, but hopefully Web3 doesn't care about it.

There has been controversial opinions on this reverse-chron feed lately here in FC, some calling it mid-take, some a high-priority...

Despite FC being a dlt protocol, I agree that Warpcast is by far the most strong client & that features released on other clients aren't as effective as they being a Warpcast feature.

But, but, I believe in the long-run the best option would be having a:

*Custom No Code BPMS-like Timeline Builder*
- either as a standalone (hopefully Opensource) client
- or via a browser plugin, well-pluggable to multiple clients
- or  hopefully on Warpcast itself.

There are non-technical elements involved in losing that power into the hands of end-users in Web2, but hopefully Web3 doesn't care about it.

https://warpcast.com/kia.eth/0x6ed3e580