@tobeycodes

2.2K posts

@tobeycodes banner
@tobeycodes

@tobeycodes

@tobeycodes

software engineer • https://t.co/GBhMZbDSJw • https://t.co/D2T2Su7qP1 • views are my own

🌎 Katılım Mayıs 2011
136 Takip Edilen1.4K Takipçiler
Noah 🎈
Noah 🎈@redacted_noah·
Solana Foundation should use their resources to introduce a third validator client that’s as slow as can be included in consensus, preferably written in js. Every time someone complains about the direction of the foundation, they increase Slowlana’s stake by 0.5%.
English
8
0
20
566
@tobeycodes
@tobeycodes@tobeycodes·
@Route2FI i miss the yield until i remind myself i lost everything 😂
English
0
0
1
14
Route 2 FI
Route 2 FI@Route2FI·
Simpler days. I miss the yield haha.
Route 2 FI tweet media
English
83
27
655
59.7K
@tobeycodes
@tobeycodes@tobeycodes·
i can confirm i cannot
@tobeycodes tweet media
English
0
0
0
21
@tobeycodes
@tobeycodes@tobeycodes·
@benln why does cafe cursor go to every city after i leave 😢
English
0
0
0
46
Ben Lang
Ben Lang@benln·
Cafe Cursor in Bangkok
Ben Lang tweet mediaBen Lang tweet media
Indonesia
31
10
334
18.8K
@tobeycodes
@tobeycodes@tobeycodes·
i have not used any sandboxes yet as i have a decent setup working in a vps but that doesn't scale beyond me. that has docker compose but there is quite a bit of complexity to ensure all the containers can talk to each other, agents know the URLs for agent-browser work, making sure the DB has seeded with data, etc. maybe sandboxes solve all of these though
English
0
0
1
20
@tobeycodes
@tobeycodes@tobeycodes·
what sandbox are you using for apps with separate frontend, backend, postgres, redis, etc?
English
1
0
0
78
@tobeycodes
@tobeycodes@tobeycodes·
@beeman_nl @stevensarmi_ @trentdotsol i am also eager to keep working on this and i do think it can be viable. i think after reflecting myself it needed a wider target audience. developers was too small of a niche and a hard one to make money from
English
0
0
1
25
beeman 🐝
beeman 🐝@beeman_nl·
I fully agree with that. If the right/most relevant people in our ecosystem think this is needed, it would be viable and get done. My goal is not to retire from working on this, but being able to go full-time, so I don't have to do any side work and can focus. Having the weight of Foundation behind it would also be good for distribution (this has been an important word this week lol) and ensure it got the right eyes on it in terms of UI/UX, features, security, etc etc etc. It would be a dream to work on this, just still not sure how to make it come true.
English
0
0
2
47
trent.sol
trent.sol@trentdotsol·
if foundation wants to vibe code shitty copypasta of things that already exist to use their "distribution" to "benefit" the ecosystem, right here > 12. All of the top wallets are still closed source. No progress made there, and seems like no one cares.
Noah 🎈@redacted_noah

It's been about a year, so I think it'd be fun to look back and see which of these complaints has been solved. 1. IDL infrastructure is even more of a mess now. There's now two sources of truth, the original PDA and now a metadata program. Unfortunately, the metadata program was built without first class support for IDL versioning. So, next time IDLs change major versions, expect more pain. 2. Parsing historical programs given the lack of IDL versioning/history is still a problem now, and with the added metadata program it's now slightly worse. 3. The read layer has improved substantially. Most rpc providers heavily index gPA, so it's not as bad (still bad). Indexers have gotten unbelievably reliable now, such that I trust running an entire UI off of indexed data. It's heavier, you have devops costs, but at least it works and you can customize to your heart's content. 4. Running an API powered by indexers is still somewhat pricey 5. Transaction sending and landing is more or less solved. I haven't had to think about this in months. Smooth as butter. 6. Anchor has gotten faster and they've fixed a lot of the issues that blow out memory. There's still a lot of improvements to be made here, and new frameworks/anchor v2 are coming. 7. CPI depth limit is set to be increased. So this will not be an issue for much longer. 8. TX size limits are set to be increased. So this will not be an issue for much longer. 9. Rent costs have gone down because SOL price shit the bed. Yay? They are also going to actually cut rent costs soon™ 10. All of the cNFT issues described still exist. These have mostly been solved by just not using cNFTs. Use core or token metadata nfts instead. 11. Errors have, for the most part, gotten better. There are still quite a few useless errors, though. 12. All of the top wallets are still closed source. No progress made there, and seems like no one cares. 13. Rust anchor client still sucks. 14. Explorers still have issues, but thanks to claude I built my own that solves most of the issues (explorer.chewing.glass) 15. The base RPC spec still sucks, but if you're okay with vendor lock-in, Helius has a ton of useful APIs. Transaction history. Ability to only fetch accounts that have changed since a given slot. Etc. 16. I actually haven't had a dependency hell issue in a few months, I also haven't upgraded anything. Maybe it's getting better? 17. I haven't had issues with preflight disabled transactions in a while. Not sure if they fixed these issues, or I just started simulating more often. 18. Running programs on a cron is largely fixed. I wrote tuktuk for this, and it's been running reliably for almost a year. Largely things seem to be getting better. I've noticed that a lot of the pain goes away if you shove all of your solana-related stuff into an API, and use that API from your various clients web2 style. You can leverage indexers for complex queries. You can change your program and IDLs without breaking all clients. You can record your own transaction history. Etc. I always had a dream that blockchain dev was a way to avoid devops costs and burden by running everything on decentralized infrastructure. We seem to have moved far from this ideal, web3 is just web2 with another kind of database. Doesn't look great for protocols outliving their parent companies, but as we've seen that almost never happens anyway.

English
10
1
40
4K
Samay
Samay@Samaytwt·
in which language you wrote your first "hello world"?
Samay tweet media
English
725
32
738
36.5K
Alex Belov
Alex Belov@belovdigital·
@tobeycodes totally agree, too many engineers get lost in their own abstractions, duplication might feel messy but at least it works, let agents handle the cleanup later
English
1
0
0
7
@tobeycodes
@tobeycodes@tobeycodes·
> “Duplication is far cheaper than the wrong abstraction.” I still see a lot of engineers creating abstraction too early and end up regretting it later. In the age of agents, I think we should double down on duplication. It's far easier and safer for agents to refactor duplication than a bad abstraction
English
2
0
1
57
@tobeycodes
@tobeycodes@tobeycodes·
Agents are extremely good at extending code. Start with good foundations and your velocity with agents will scale easily
English
0
0
3
55
@tobeycodes retweetledi
Stepan | squads.xyz
Stepan | squads.xyz@SimkinStepan·
Cypherpunk blog posts can only get you so far. Instead you can build something customers want and help them move off traditional banking to stablecoin rails. Our mission is to get to end to end stablecoin settlement across all businesses using Altitude because this is how pure velocity and efficiency of money movement is reached. But we have a lot more work to do before we get there. The reality is that most businesses today do require to settle via traditional rails for at least some of their payment volume and we are giving them that option, while they are holding 100% of their balance in stablecoins on the platform. A stablecoin account that connects you to local and onchain rails is how you bridge the gap and fulfill the mission. If you can’t see why this is the way to go, feel free to DM.
Stacy Muur@stacy_muur

Crypto projects are now bragging about rolling out SWIFT transfers for stablecoins. If you can’t see what’s wrong with that, I can’t help you.

English
9
12
76
5.7K
hårkl
hårkl@harkl_·
Seeing @tokens as competition depends on your belief about who should own token verification authority. If a private company owns it, they decide who gets listed, on what terms, and bundle it into their own product. Every competitor builds on their rival's infrastructure. If tokens.xyz is OSS public infrastructure, anyone can build on top of it. Same neutral data layer, infinite product possibilities. Open protocols first. Products on top. Ecosystem growth. 🤝
English
3
0
30
1.2K