Here is our vision map
Spent all morning crafting this
I really, really encourage you guys to read this, and ask me any questions
Will help you understand everything that's coming and what we're trying to build here
https://t.co/CnUn8jdZAz
Quick dev note about @gf_codes - a bug in image generation is causing Twitter to crash when a user sends in an image request
This might impact the agent availability
Fixing this asap.
Introducing Persistent Apps with Phantom Wallet Integration
Weโre making app storage more reliable with Persistent Apps. Gone are the days of relying on browser cache or local storage to retain your creations. Now, all apps generated are securely linked to your Phantom wallet, offering seamless access across devices.
What does this mean for you?
Secure and Decentralized Storage: Your apps are tied directly to your Phantom wallet, ensuring they are always available, no matter where you log in.
Cross-Device Access: Switch devices without losing access to your creations. Simply log in through your Phantom wallet to retrieve and manage your apps.
This update ensures your apps are safe, accessible, and ready whenever you need them.
Can't believe I batted for this @blader dude. Straight up lying that he's "never been in crypto" and "never even had a Sol address" when there's onchain history of him talking NFTs, being active on FriendTech, and now rugging coins
Absolute bottom tier behavior
Be better for your kids dude
Webcontainers are lit and they're going to power the future of CoderGF
Node in the browser?
Hell yes.
Throw in Supabase and baby you've got a fullstack stew going
@zillionary this is a browser side error, usually an extension or caching conflict on your end. Not much we can do, but a hard refresh typically fixes it (CMD/CTRL + R)
see this:
https://t.co/FLuATr1GDM
Quick dev note:
Noticed that a people were getting client side errors
1. This error is caused by the client (the browser) and is out of our control
2. Most of the times, the error is caused by some browser cache issue or conflicting extension (Metamask, fyi, is notorious for this)
Errors like these randomly popping out of the blue typically happens when an extension gets updated in the background and breaks something within the browser. Hotfixes are usually applied within hours by the browser/extension - though Christmas time might be slower.
Since this is a browser issue, we can't really fix it from our end.
However, you can correct it very easily:
How to fix it:
โ A hard refresh - CTRL + R (CMD + R on Mac) - will fix the error in 99% of cases
โ If that doesn't work, you can try clearing the cache
โ If that STILL doesn't work, you can try disabling some extensions - but #1 and #2 should take care of 99.9% of cases
We can't control this error, but we did ship a more elegant way to handle errors so you don't see that client side error message. Instead, you'll see a more graceful refresh button
Here is our vision map
Spent all morning crafting this
I really, really encourage you guys to read this, and ask me any questions
Will help you understand everything that's coming and what we're trying to build here
https://t.co/CnUn8jdZAz
Gm folks
A couple of slower days with Christmas around
Back to the grind
Big Q1 in terms of development. If we can virtualize a backend and somehow create a one-click Supabase connection, I would extremely pleased
Then we cook on revenue generation