👀👀 $degen – not frames – has been driving Farcaster's growth 📈📈

(data from The Indexing Company; h/t to @aperture)

Monkey on the chain | wrangling data at The Indexing Company
https://www.indexing.co/

I like running, poker and oysters | Founder, Social Forensics (SocialForensics.com) | Berkeley & UPenn | Learning to listen

What changes would you make? Would you simply disallow devs from adding tipping through replies, or is there another solution you have in mind?

Tips could be protocol level reactions (extend with two fields ticker & amount) or a new message type or outsourced to frame servers & processed onchain. 

There’s no way to stop in cast tipping.

Would be super curious to hear how much activity is now in dc & group chats vs onHub

Ethereum builder & people connector. Juicebox, Revnet, Defifa & Footy App

You could filter out reply tipping at the client level. What’s the reason for not having reaction tips at the protocol level? I assumed it’s because Apple doesn’t like it, but clients don’t need to add it if they don’t want to? 

I also want to see some data about dc/group chat.

Filtering at client is fine when the context is isolated. eg this is a cast. This is a tip. Mix the two & 🤦. That’s why new reaction or msg type suggestion.

Why not do that? Good q. Same q for why not have frame interactions (ie messages) onHub? 🤷🏻‍♂️ 

Guessing: speed of iteration 😒

I would prefer cast actions for tipping with frames to show allowances and received tips vs protocol

Keep protocol as lean as possible. No need to have tips there

Farcaster Development Boutique @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

Agreed on not increasing what the protocol does (verify, store & sync).

I wonder in your suggestion, how the recipient of the an offchain, frame base tip would hear about the tip? A cast? Seems heavy if not a new message type. How are you envisioning that?

Keeping protocol ‘clear’ seems like a non issue. It’s gonna be onHub or onchain I think. Having messages on a frame dev’s server is a sad side effect of the existing trade offs. If msg is private whocares where it’s stored. If it’s public then it’s ‘on’ something decentralized

I like the dc idea🤝

Either bot replies (removes 1 tip reply from the set of messages sent)

Or even better programmatic DCs

Bot will DM you every tip you get

That way (until DMs are in protocol) the protocol is clear