ex workflows intern @cloudflare
Joined September 2022
- Tweets 3,976
- Following 695
- Followers 673
- Likes 2,290
665 Photos and videos
My internship at @Cloudflare has finally come to an end - and it ended with a banger!!!
The past few months on the Workflows team have been an incredible experience, tackling problems at the kind of scale that comes with building at cloudflare. I was also lucky to be surrounded by some of the smartest and kindest people I’ve worked with
Hopefully next week I’ll get to share some of the nitty gritty details and surprisingly weird complexities of building rollbacks on top of workflows!!
Jun 6
Cloudflare interns are cracked
3
2
94
58,601
i am once again looking for cute pet pictures 👀
does anyone have a picture of your pet that i can use on a @cloudflare workers sdk pr? im biased as well :)
1
1
4
274
AYYY!!! Come ship cool projects with us this Saturday!!!! Pretty cool way to interact with the @Cloudflare folks as well!!! See y'all there ⛏️
Jun 10
Bengaluru - @CloudflareDev is hosting a builders-focused hackathon this saturday at the @cengines_studio office in Indiranagar.
Sign up today.
luma.com/vsyebdod?build=true
5
315
one cool thing about this is that this has very creative SLD generation. look at the output:
umamikitchen, fungifare, bowlofshrooms, souptastique, soupsational
those are pretty cool brandable names: food domain synonyms (umami, fungi, etc), collocations (bowl, spoon) and a very interesting affix play (-tastique, -sational, -savvy, whatever)
it seems to be very .com heavy and TLD shallow. the focus seems to be on naming, compared to combining cool names and potentially cool tlds
4
867
I was trying to improve my semantic retrieval and TIL, there are tlds like this
these "xn--..." tlds are apparently punycode: ascii safe encodings for non latin domain endings
look at these examples:
xn--3ds443g = .在线
xn--q9jyb4c = .みんな
xn--80asehdb = .онлайн
real sites use this too: xn--d1acpjx3f.xn--p1ai, xn--d1abbgf6aiiy.xn--p1ai, xn--p8j9a0d9c9a.xn--q9jyb4c
- яндекс.рф is the real yandex russian domain
- президент.рф is the official russian gov domain
- はじめよう.みんな is a google registry promo/example for .みんな
324
AYYYYYYYYY, NOT THE BEST BUT WE'RE GETTING THERE FROM ABSOLUTE SCRATCH
hmmm, the ai search feature over here is pretty interesting. i dont think it's "ai" per se, but it seems to be a version of semantic search on steroids. i have no clue how this works but it'd be pretty cool to tinker around with. really cool and useful feature tho
1
1
8
3,420
now, this is just the first half on how we're storing things. retrieval is up next. for querying, im gonna try with
let's say, "cinema ticketing platform"
- whatever shitty embedding model i use will just turn it into vector
- ill throw @Cloudflare vectorize at the problem and it'll find nearby stored vectors
- we get semantic contexts back
- generator creates domain labels
- reranker sorts them
- resolver checks availability???
- profit?!?!?!??!!
i think this is much cheaper than throwing an ai model at the solution or even a generic string matching solution cause keyword system only knows exact words
with vectors, it can connect related ideas(?):
cinema
movie theater
ticket sales
events
showtimes
booking
my naive way of implementing this is now, for each searchable thing:
text: "scheduling app for trainers and classes"
metadata:
- title
- concepts
- label words
- suggested tlds
- source
vector: [] (whatever the vectorized form is and the vector is pretty much the semantic meaning of the text)
i dont think this will scale well as i dont think it'll handle everything that the end user would throw at me
1
222
my naive way of implementing this is now, for each searchable thing:
text: "scheduling app for trainers and classes"
metadata:
- title
- concepts
- label words
- suggested tlds
- source
vector: [] (whatever the vectorized form is and the vector is pretty much the semantic meaning of the text)
i dont think this will scale well as i dont think it'll handle everything that the end user would throw at me
hmmm, the ai search feature over here is pretty interesting. i dont think it's "ai" per se, but it seems to be a version of semantic search on steroids. i have no clue how this works but it'd be pretty cool to tinker around with. really cool and useful feature tho
1
1
509
you know what? ik jackshit about semantic searches so fuck it, we balling and doing this now
hmmm, the ai search feature over here is pretty interesting. i dont think it's "ai" per se, but it seems to be a version of semantic search on steroids. i have no clue how this works but it'd be pretty cool to tinker around with. really cool and useful feature tho
3
1,655
hmmm, the ai search feature over here is pretty interesting. i dont think it's "ai" per se, but it seems to be a version of semantic search on steroids. i have no clue how this works but it'd be pretty cool to tinker around with. really cool and useful feature tho
the streaming sorcery from the triangle company is so good, i get my domain, suggestions and pricing within like 500ms. insane
1
2
1,386
definitely can attest to this! turbo being open and protocol friendly made this possible. turboflare is a small alpha for folks who want their remote cache in their own @Cloudflare account. excited to see what's coming up later down the line!
turboflare.vaishnav.one
Jun 8
Turborepo is the open platform for your monorepo. We design Turborepo to be a base layer LEGO brick for you and your agents.
Here are 5 examples of self-hosted Remote Caches, Microfrontends, and Module Federation in Turborepos.
First, @wishee0 released today a Remote Cache that you can use on Cloudflare.
x.com/wishee0/status/2064020…
2
233
this is a single domain search for hostinger that took <900ms while the bundle search took around 3-4s. im still surprised that i got results from vercel within a second
yikes, im not really sure how domain fetching works but what even is going on here lmao
1
1
262
LESSGOOOOOO, IT'S FINALLY OUT IN ALPHA!!!
Turboflare is live! (turboflare.vaishnav.one)
A selfhosted @turborepo remote cache on @Cloudflare Workers R2 (optional) kv and so much more:
- clone free setup with one simple command:
pnpm dlx create-turboflare
- R2 backed artifacts (and KV for you weirdos out there, jk!)
- stock turbo client support
- scoped tokens team isolation
- branch aware cache policies (we aint dealing with cache poisoning again!)
- optional signatures, metrics, cleanup and boring admin APIs
In my CI, a rebuild from remote cache dropped from ~95s to ~2s (im bringing hard numbers this time, lmao)
ALPHA, but usable. feedback/bugs/features welcome!!!!!!
github.com/vaishnav-mk/turbo…
(surprisingly easy to self host and absolutely no vendor lock-in from @vercel's end, y'all cooked with this!!)
YOOOOO MY REMOTE CACHING SERVER ON @Cloudflare WORKS, @turborepo IS INSANE WAAAAAAAAAAA. this is probably the most over engineered solution lmao
11
13
148
14,647