kabosumama adopted many cats and dogs and because of this, it’s quite difficult to pick a beta to $cate because there’s so many of it.
but instead of picking another animal from multiple animals with kabosumama, why not make kabosumama herself the mascot of $cate.
she gave cate a home. $kabosu is home for cate which makes it the only thing that deserves to run with $cate
9sgtSQDsvREbGqutqwBtWZfvKU6oYdRFqFBAs6St7cDo
Today i launched the $GROWTHX token on @orynth
GrowthX is building an AI-powered growth platform for X, helping creators and founders create better content, improve engagement, track their growth and understand what actually works.
The goal is simple: make growing on X more data-driven, consistent and easier to execute.
CA: EmCKsGVs4qCt6kdE5B3saWYvj1ibdALLZGcdJQHxory
This is only the beginning.
More features, updates and more coming from the team soon. Stay tuned.
Kat just updated both the README and the source code for @universalweave.
The README change is more important than it looks.
It now explains why this library exists: Looms are easy to prototype, but once you add DAG documents, serialization, editing, stable ordering and CRDT collaboration, that simple idea turns into a lot of subtle problems.
@universalweave solves those problems once, so future builders do not have to rebuild the same foundations from scratch.
@transkatgirl also writes that this library comes from roughly 1.5 years of trying to build a worthy successor to the original Loom.
That puts the project into perspective.
At the same time, @transkatgirl pushed another source commit called “Further optimizations.” I attached the actual code changes below.
In simple terms, she is tightening how the graph and layout engine stores edges, traverses the DAG and prepares node placement.
The visual layout layer is still WIP. But the README is becoming easier for developers to understand while the engine underneath keeps being refined.
Study $weave.
https://t.co/ozgdPhxzPW
5 new commits just landed in @universalweave src.
@transkatgirl has started implementing the DAG coordinate assignment system.
Simple version: once a Loom has many paths splitting, crossing and merging, the app needs to decide where every node should sit, how far apart the branches should be, and how each connection should travel without turning the screen into a mess.
That’s what this code is starting to solve.
The update adds graph ranking, 2D node placement, spacing, polyline routing for connections, and viewport-aware loading so apps can focus only on what is currently visible.
This is the machinery that turns a raw graph into an actual map people can navigate.
Around 1,550 lines were added across these 5 commits. It’s still WIP, so graphing is not finished yet.
But the hard parts are taking shape in public, commit by commit.
Keep an eye on the repo.
$weave
There is 3 differnet pets in the leak a dog,cat and bird
Proof- https://t.co/GZ6ZYpEvZt
DOX-https://t.co/1xfK1LnoxD
Leak-https://t.co/2nSXawAhIc
https://t.co/oEAFkZJ6Yr
Just minted my Osero Origin.
Proof I found @OseroHQ early.
Looking forward to seeing where this goes.
https://t.co/GehLzGxiQ3
6bf4aeb1241bf8f2cbe0a266f7fd
3a95be424c140521137053235b
23fbO
And for the athletes: you've got to have a dream to make it come true. You've got to bet on you.
Athletes looking for a early access code reach out in DM's