Founder @tapedrive_io
store anything →
Joined December 2010
- Tweets5.1K
- Following1.5K
- Followers2.8K
- Likes11.3K
So with 4 compromised, am I safe with this one?
-----BEGIN PRIVATE KEY-----
12345
-----END PRIVATE KEY-----
Something that keeps coming up:
"hey, can i store something for like a hundred years?"
The response has been:
"no, why do you want that?" 🫠
Turns out a few of you really want that ability anyway, so this week I've updated the scheduler to allow that...
Epochs +100 years into the future can be pre-paid with the new scheduler
(rollout tbd)
This last week has been full of user facing fixes.
One of those is ensuring we can scale up *and* down with demand.
This has been a todo forever..
I think the solution is pretty cool; visually as well. But more importantly it lets us dynamically size the minimum storage unit, which means a wider range of you can participate in Tapenet.
Also ssd prices are bananas… using smaller but more nvme drives is now easy 🤓
you could devote yourself to producing a better product and literally do something superior in a year if you really wanted to... for pretty much anything
what a time to be alive
It was an absolute honour to present at @solanaturbine enrichment week.
Looking forward to seeing what you guys build!
Appreciate the kind words🙏
Finally, the session concluding this day couldn’t have been more goated! Session 3 of Day 4 of Enrichment Week at @solanaturbine featured @zelimir__ from @tapedrive_io.
To be honest, I’d been looking for someone like him for a long time. A lot of senior devs in the Solana ecosystem have concluded that Solana and decentralized systems have no practical use cases other than finance. I’ve been trying to challenge this view and building projects around it.
When the session started, @qubitn8 introduced him as someone doing serious work outside the mainstream of the ecosystem. He’s using Solana to build onchain storage where you can save your files, host your websites, and more.
He explained how he came up with the idea, and I have to say, the way he built up to introducing his product was amazing. By the way, it’s live on devnet, and testing is underway!
Using first-principles reasoning, he explained what Solana makes possible that traditional storage systems don’t, walked us through the product’s architecture, and showed us how it works.
At the end, he hosted a simple HTML website on @tapedrive_io. My eyes were glued to the screen!
I studied how divergent thinking plays a crucial role in creating novel products in my design thinking classes at college. Today, I got to experience it firsthand.
He’s doing a fantastic job. His goal is to create an infinitely scalable, permissionless, distributed system and he’s chasing it.
It's been a *long* time since I last touched the storage allocator. This time the goal was to ensure storage nodes with varying raw capacity could participate in the Tapedrive network.
This is a big one for adoption, and I'm hoping to allow way more of you to participate.
We're going to roll this out to devnet sometime soon
Having too much fun with the cute tape machine icons.. lol back to building
Love this for on-prem and local setups though
It was an absolute honour to present and connect with a bunch of you, and even be featured on the giant solana timeline 🫣🤯
I can’t imagine receiving this kind of warm reception anywhere else
If you’re not coming to @SuperteamCAN events, you’re missing out!
🫶
Z retweeted
Hear Zelimir on Solana as the world’s fastest atomic state machine
We heard from @tapedrive founder @zelimir__ about how he's using Solana to empower builders to infinitely scale their ideas.
I want to talk about a happy accident that is working quite well for us.
I've seen a few mentions of this and feel like we're not alone.
When I started Tapedrive last year, it was a totally different project (It literally has nothing in common anymore). I had to pivot a few times to figure out what approach would work and dominate the other storage chains ;)
This created effectively 3-5 completely independent (mostly) projects. At some point i wanted to wire all these together as there was a logical progression from one to the next but the git history was lost between them.
I wrote a tool to re-write the entire history, sourcing commits from each, and appending to the original codebase.
This created an amazing opportunity:
A) I could filter out directories or files i did not want public (internal docs, api keys, thinking that didn't land, etc)
B) I could have a mono-repo locally but have separate codebases elsewhere
C) This is the most important, i could continue to write engineering approved commit messages: "wip", "ugh", "what am i doing", "lol"... and then have an AI agent reword my commits for a more "refined" public audience :)
So, if you see 3 weeks of no activity on our main protocol codebase, it doesn't mean we put the pen down for 3 weeks, it means i have not run the tool to rewrite a clean history for your viewing pleasure 😅😂🤫
More orgs should do this, its awesome
