We're going to say goodbye to Frames v1 on July 31st.

When we announced miniapps (v2 frames) back in November, we promised to support the old standard for 6 months, to make the transition as smooth as possible. 

Now that time has come. Most people are building and using miniapps which we are excited about, and the old frames are slowly disappearing from the timeline. 

What happens next?
On July 31st, we'll slowly stop rendering frames and cast actions in feed. Both these features are seeing little to no usage. In the coming weeks, we may also make changes to make cast actions less prominent in the UI to make space for some new features we're working on. 

Why is removing frames important?
It's a lot of work to support older standards and slows down the team from shipping things that people want. No new teams are building frames anymore, and existing teams have largely moved over to miniapps.

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

a Composer Action to search & share GIFs | try it: https://bit.ly/4dg55gk | premium: hypersub.xyz/s/gif | how to use: https://bit.ly/3TIOafc | dev: @0xconca.eth

Hey @v ,
I think this might impact my @gif “composer action”. 
I can post a video on how it works if you are not familiar with it, but I am pretty confident I won’t be able to replace all its functionalities 1:1 into a miniapp… being able to attach a gif from anywhere, especially when composing a cast in reply to another, is indispensable for @gif — what are my options?
Thanks