i stopped using farcaster for a while because i didn't agree with some of the protocol design decisions and how quickly warpcast was iterating on it.

but @yougogirl.eth rightfully pointed out to me that having A protocol infinitely better than having NO protocol.

to that i had no rebuttal 😂.

gm...

Growth is infinite. Work is worship.

/vv /opepen /checks

well said — what are the changes that you disagree with?

the new/future channel design vs sticking to the previous metadata or DNS records for example felt more like a business decision than a protocol decision

and more generally i would have preferred slower standards introduction so apps like yours (super) would have a fighting chance to keep up. 

quite sad to see that go by the way - but congrats on the new position at the same time 😅❤️

Idea re pathway (not onchain)

AFAIK channels are just casts that belong to a certain parentUrl on the protocol.

Why not use DNS and/or OpenGraph to customize how channels (other URLs) are displayed in clients?

- Title = OG title
- Image = manifest app icon / favicon
- Admins = specified in new OG-esque property

thanks Dan!

i just loved the notion of URI based channels and imho it "not working" was more an app issue than a protocol issue. i remember we had a ping pong about this back when the new spec was designed. https://warpcast.com/jalil/0xe7e28829

was very in line with the "global state" thinking as well imho (all/open global conversation about a given thing/topic/event (URI)). the "VV" channel could be all casts with a parentURI of visualizevalue dot com, with channel metadata and settings set via opengraph-style tags.

also i realize it's not really an either or - onchain ownable channels are useful for things like "travel", "cryptography", or "philosophy" i suppose.

love to hear you added more metadata placeholder features will check them out.

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

Just for context:

It was a channels aren't really working decision.

If they are working, we're committed to enshrining on the protocol.

We've since added a bunch more APIs for the metadata as a placeholder.

cc @sahil who is probably the biggest developer on channels right now