Content
@
0 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
If Warpcast was open source, what are 1-2 things you would want to learn how we do?
38 replies
11 recasts
102 reactions
jj 🛟
@jj
Direct casts. Ability to list convos, view convos, reply. Rendering casts. If you all just had an open source component to render casts, that’d be massive for clients.
1 reply
0 recast
3 reactions
Dan Romero
@dwr.eth
What's hard about rendering casts?
1 reply
0 recast
1 reaction
jj 🛟
@jj
It’s all the logic around embeds, frames, videos, etc…
1 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
In terms of displaying them? Outside of a strict clone of Warpcast UI, wouldn't really work for other clientS?
1 reply
0 recast
0 reaction
jj 🛟
@jj
If you had a standard cast object from the hub, having the ability to render the full Warpcast rendering capabilities is a big thing. I understand there are Warpcast proprietary APIs. But clients right now build nerfed cast (just text and images) rendering because of all that logic.
1 reply
0 recast
1 reaction
Dan Romero
@dwr.eth
I guess I'm a bit slow -- what specifically is hard about it? Is it the design? Is it the logic around what to do with two frames, a frame and image, two images, etc.?
1 reply
0 recast
0 reaction
jj 🛟
@jj
It’s not hard in particular - just bandwidth. If there was a component you just plug and play, I’d say there’d be more clients. It’s around rendering videos, images, embedded URLs, embedded casts, threading, mentions, channel links, etc.. just lot more to think about then testing everything.
1 reply
0 recast
1 reaction
