# qcast update #7

*龴ↀ◡ↀ龴 buildspace s5 龴ↀ◡ↀ龴*

By [deca12x](https://paragraph.com/@deca12x) · 2024-07-11

---

**\_tldr\_**

*   i'm building a scheduler for casts (posts) on farcaster, join the [waitlist](https://warpcast.com/deca12x/0x79ea082d)
    
*   working on allowing users to upload their images (using Pinata & IPFS)
    
*   see [update #6](https://paragraph.xyz/@deca12x/qcast-update-6)
    

**\_technical\_**

*   users generally don't have a url of the image they want to post, so i need to offer an easy way for them to upload an image and then have it hosted securely.
    
*   i want to avoid storing the images in my own server, cause if it stops running, all images in users' casts won't be available.
    
*   so i'm building in the ability for a user to upload an image to ipfs through pinata. the flow looks like this: user uploads the image, when user clicks on cast button, client-side sends image file to server-side (if present) with a post request. server side generates pinata jwt key, then pins image to ipfs, gets the url and includes it in the cast intent as an embed.
    
*   ...this approach is expensive, as it would cost $20 p/m above 500 uploads (on top of the $9 p/m of neynar) and also it's tricky to implement. i found another solution (below), but i want to get it done this way first to learn and have working code for this approach.
    
*   the alternative is [imagekit](https://imagekit.io/docs/api-reference/upload-file/upload-file), not web3 but has a large free tier and is easier to deal with, even direct from [client-side](https://imagekit.io/docs/api-reference/upload-file/upload-file#how-to-implement-client-side-file-upload) i think.
    
*   in conclusion, this week i want to get the pinata + ipfs approach working. starting next week (i also have ethglobal brussels this weekend) i'll work on the imagekit approach.
    

**\_farza notes\_**

farza says: iterate the build-in-the-open loop:

*   ...create, launch, measure, learn...
    

so i reached out to my 7 early waitlist users with 3 questions:

what not to do when asking for feedback:

*   don't defend
    
*   don't make changes based on feedback without understanding why
    
*   don't ask 'would you use this / check it out?'
    

_"thanks for being amongst the first ppl to join the qcast waitlist!_

_heyoo, i'm_ [_@deca12x_](https://warpcast.com/deca12x) _core member of_ [_urbe.build_](http://urbe.build)

_can i please ❤ get an idea of_

*   _do you always cast from warpcast? (what else?)_
    
*   _do you use any tools to plan future casts?_
    
*   _what is your least favourite thing about warpcast?_
    

_the best way to support qcast rn is to cast a referral frame 👇_ [_warpcast.com/~/compose?te_](http://warpcast.com/~/compose?te)_..."_

[

![](https://ik.imagekit.io/buildersgarden/qcast-landing_3PlsW4FEe.png)

https://www.beearly.club

Beearly - qcast
---------------

Beearly - Launch your waiting list on Farcaster.





](https://beearly.club/w/qcast)

![](https://storage.googleapis.com/papyrus_images/2b671c106973718b64c26ee1353e910a.png)

---

*Originally published on [deca12x](https://paragraph.com/@deca12x/qcast-update-7)*