FTCHD

Results 18 issues of FTCHD

I'm seeing an "averaged" response code of **`213`** due to one 404 response (and the rest 200).

enhancement

I'd love to be the one to add it but I'm not so familiar with how this should be integrated. I've integrated prerender in the past and their NextJS middleware...

enhancement

Let me know if this is right, not sure about the **`isOslo`** part but everything else should be fine!

Currently everything you do is auto-saved to the database, every Frame modification. This is good, we are not changing this, it would be a hassle to press “Save” after every...

good first issue

## **Description** as seen in the issues linked below, google is now aggressively blocking alternate frontends, clients such as `yt-dlp`, and non-residential IPs. the only solution is to use `oauth`...

Currently you specify a global `functionName` for each handler. This PR handles specifying a `functionName` for each button. This would remove `target` for `post` type buttons, as it doesn't make...

# Description (500 PTS) - This is a last call Issue, you haven't missed it before. - Implementing Figma Oauth login with its **[standard Oauth flow.](https://www.figma.com/developers/api#oauth2)** - You can add...

        # Description (1,000 PTS) - The goal here is to add the **`wagmi`** & related **`AppKit`** packages, the **`wagmi`** connectors and the **`wagmi`** Provider to the...

# Part of FrameHack2 (300 — 2,000 PTS) ### This **`Issue`** is used during FrameHack2 to connect PRs that add completely new templates to FrameTrain. Not all submissions will be...

# Part of FrameHack2 (1,000 PTS) ℹ️ Terminology - **Viewer:** The person using the Frame on a client. - **User:** The person who created the Frame on FrameTrain. - **Creator:**...