Content pfp
Content
@
https://warpcast.com/~/channel/fc-devs
0 reply
0 recast
0 reaction

androidsixteen pfp
androidsixteen
@androidsixteen.eth
Why does Warpcast use so many different hosts / CDNs for PFP urls? I'm having to add a ton of remote patterns to my next config to be able to show external images I could add a proxy route to fetch images and serve them, but this seems like an unnecessary hop Feel like I'm missing something here...
6 replies
0 recast
26 reactions

MOΞ pfp
MOΞ
@moe
just load all external images.
1 reply
0 recast
1 reaction

androidsixteen pfp
androidsixteen
@androidsixteen.eth
Seems like a bad move from security / perf standpoint?
1 reply
0 recast
2 reactions

MOΞ pfp
MOΞ
@moe
yeah if security/performance is a concern, then you'll have to route all media content (pfps, cast images, ..) through your own cdn to resize/cache anyway. my point was that you can't filter based on domains because fc is an open protocol with many clients that can upload content to anywhere, so whitelisting domains isn't practical.
1 reply
0 recast
1 reaction

androidsixteen pfp
androidsixteen
@androidsixteen.eth
That’s a good point — I thought about that, but figured that most of account creation / pfp updates happens thru Warpcast, so if they had standardized their infra, it wouldn’t be as much of an issue Still take your point that the best way to ensure perf is to route thru our own cdn
0 reply
0 recast
1 reaction