cho.sh
2,244 notes
Liked on XI made a mistake. When Jack and I decided to organize this $100K Hackathon, my biggest concern was cheating. Unlike a regular hackathon, everyone participates from home. And because the winner is whoever makes the most PROFIT (not revenue), there are so many ways to manipulate the numbers. So I added a $99 entry fee. One thing I’ve learned from building businesses is that people tend to be more committed when they pay for something. I thought it would filter out spam, attract serious builders, and make the competition fairer for everyone. But I completely missed the other side. 3 years ago, I was a living with my apps. Today, I’m financially free. My life changed so much that somewhere along the way, I lost perspective on what $99 means to someone else. For someone in India, someone struggling to pay their bills, or someone trying to make their first dollar online, $99 can be a lot of money. And those are exactly the people I want to help! I’ve spent years sharing what I’ve learned, reviewing random people’s landing pages, and organizing free meetups around the world. Not because there’s money to make, but because I genuinely love seeing people build things and succeed. And somehow, I was so focused on keeping cheaters out that I didn’t realize I was also keeping genuine builders out. That’s my mistake. So I’ve decided to make the $100K Hackathon completely FREE :) Everyone who already paid got a full refund. I’m still worried about cheating. That problem hasn’t disappeared, and Jack and I will have to figure out better ways to verify profits and keep the leaderboard fair. But that’s our problem to solve. Thank you to everyone who shared their thoughts. Sometimes you need people to remind you of things you’ve forgotten. I genuinely hope this hackathon changes someone’s life. ❤️Liked on XIt’s time to bring back Cafe CursorPosted on Xyo @pendev i can't live share edit a .pen file? it's the most needed featurePosted on XI'm coining a word "Agentsplaining" Agents condescendingly assuming the user don't know fuck and repeating the obviousReplied on X@jayhxmo @raycast Hard to explain. It's the small detailsPosted on X@raycast iOS keyboard is insanely good. Might resub Raycast pro just cuz of thisReplied on X@ishuagra02 I saw a theory that F5.2 is a post train of 5.1, but O5.5 is a distillation of F5.5(unreleased new pretrain) and thats why O5.5 > F5.2Liked on X@anaclumos don't know what is actually improved 👀Posted on Xam i the only one underimpressed with 5.2 fableReplied on X@bvvst great minds think alike https://t.co/YRFWhb1mcOLiked on XClaude Fable 5.2 is out and it's the perfect time to run this god-level prompt on your codebase: "I want you to audit our codebase, is anything here unnecessary, overly complicated in our current setup, or based on weak assumptions? Challenge them. - What can be deleted entirely? - What can be simplified now that unnecessary pieces are gone? Then make the changes. Prefer deleting over simplifying, simplifying over optimizing, and optimizing over automating. This product is being used by thousands of customers, do not cut any corners." This prompt is one I run often and leads to the best results.Replied on X@akshayadinesh19 @bot can we please BYOM for botsLiked on XTo be fair, the Chinese models have a much lower refusal rateLiked on XF*CK IT, im creating a library of AI slop indicators. my feed is full of taste larpers. stay tuned https://t.co/5Muv8nQRm3Liked on XJENSEN! THATS NOT WHAT WE MEANT BY CHINESE MODELS!!!!!!!Liked on Xmy parents had to declare bankruptcy when I was a kid, so they had every reason to pressure me towards a more stable career path instead, they were so patient with me, even as i failed startup after startup for years so getting to tell my mom that everything turned out okay was a really special moment :) for those who can't read Korean, her first message roughly translates to: "Really!!! Congratulations my son. So much :') Thank you God!" i know I've been posting about my exit for like a week now, but it really is a big deal for me and my family! i'll share more about how this all happened and some tactical advice later this week, but for now i'm just riding out all the emotions to quote my mom, thank you God!!!!Liked on X@thefarmers_Dog it stands for Egg GzampleLiked on X🦍 Introducing Memorilla: memory as a modality for LLMs Memorilla turns everything a frozen LLM needs to remember into just 16 memory embeddings ⚡ It uses up to 4,212× fewer tokens and is 27× faster than full context inference while more accurate 🎯 Pushes the Pareto frontier over RAG and agentic memory in personalization, long-document and knowledge QA A thread 🧵:Liked on XThere's a huge product opportunity downstream of Tailscale etc too. At @tldraw we've started designing for "high trust networks" and it's been a beautiful thing. 1. Features that would be a nightmare on the internet are okay on my computer and mostly okay on private networks. Websites that execute user-generated scripts, control production systems, allow for users to send desktop notifications, spend tokens, or directly prompt my agent. Crazy stuff that would only make sense if everyone was in a committed polycule. 2. When everyone on the server can be trusted to have _external_ reasons for good behavior (eg keeping their job, or maintaining friends, family, church, mafia org), the software can be designed in a default social way. Most apps default to isolation, low horizontal visibility, highly restricted collaboration. Makes sense if the social contracts are inside of the app, but if you can trust that they live outside of the app then you can get wild. Example being small group chat names as an emergent comedy phenomenon because anyone in the group can change the name. 3. This can work for commercial products, too, not just internal stuff. Security matters more than ever but the way we've seen that manifest is that more companies are more confident in their own solutions than anything we could provide, to the point where owning data and access is a better value proposition than having it managed. Always has been true for big companies but now even small companies can get a good secure network set up pretty easily, and the hooks we need to build are easy enough. tldraw offline got us started down this road (and shout out to @pendev for first introducing me to the idea of desktop + mcp). We've been bringing that product to private networks and it's been exciting to see how much we can get away with. Keep an eye outReplied on X@saradu birds eye viewLiked on XApplications close in 2 days!! If you have a cool bio idea, and $5-10k will go a long way for you, please apply!!! https://t.co/NCvmrNC53cLiked on XWe've been early adopters of Rust since 2018 and a lot of our infra, voice tech, and even some of the current client is already Rust, the holy grail was getting the whole client there. That means Electron goes away, and so does React Native, mobile keeps native UI but shares app code with desktop via Rust. We hope to get it into testing with users soon™. (And it's not Tauri, it's GPUI, so good guess everyone.) Alright, back to staring at the WoW Forever login screen.Reposted on XOh boy. https://t.co/X7SSskGuGvLiked on XRIP .si domain squatters
Project Fiesole

Project Fiesole

Warning

Over a year old. May be outdated

The question

Can we VFL MNIST?

Project Fiesole tries to show that a CNN can work inside , so models improve from more data without anyone handing their data over. The data lives in islands here. Different organizations hold different features about the same people. Instead of pooling it all in one place, VFL lets them train one model together, each side bringing its own features. Data stays private, and the model still sees inputs that no single dataset would have. Fiesole is a subproject of .

Method

In VFL each island holds different "input parameters" for the same "subject". So in this demo we split the original image (here, 9) into four distinct pieces. Each will necessarily work as a "distinct input."

63E892

I made four training sets, one per quadrant, with masking.

Control Group

Ran all ten epochs on the original dataset.

  • MNIST CNN: 99.16 %
One by One

I ran ten epochs on one dataset without coming back to it, then moved to the next one.

  • TL(10): 26.82 %
  • TL(10), TR(10): 36.44 %
  • TL(10), TR(10), BL(10): 30.66 %
  • TL(10), TR(10), BL(10), BR(10): 47.24 %

Round Robin

Round-robin

One epoch on TL, then TR, BL, and BR, then back around. Four cycles, 16 epochs total.

  • Cycle 1
    • TL(1): 59.37 %
    • TL(1), TR(1): 79.6 %
    • TL(1), TR(1), BL(1): 88.51 %
    • TL(1), TR(1), BL(1), BR(1): 79.88 %
  • Cycle 2
    • TL(1): 85.68 %
    • TL(1), TR(1): 87.69 %
    • TL(1), TR(1), BL(1): 91.4 %
    • TL(1), TR(1), BL(1), BR(1): 88.52 %
  • Cycle 3
    • TL(1): 82.21 %
    • TL(1), TR(1): 86.56 %
    • TL(1), TR(1), BL(1): 90.98 %
    • TL(1), TR(1), BL(1), BR(1): 89.07 %
  • Cycle 4
    • TL(1): 85.24 %
    • TL(1), TR(1): 86.33 %
    • TL(1), TR(1), BL(1): 91.99 %
    • TL(1), TR(1), BL(1), BR(1): 90.12 %
Round Robin, 10 cycles

Still around 92%, max. Never goes above 95%.

Federated Learning

Results

E0ED4F

DA87AB

2289D2

EC12E1

7147C6

AB6E91

C6F843

EEF724

E2D67A

DFF919

A1DAA5

BC3839

  • The averaged model maxes out around 10-15 federations. Before each one, each learner trains ten epochs on its own dataset.
  • It never gets over 95% accuracy.
  • The full CNN, by contrast, hits 98% quickly.
  • I think this comes from the lack of understanding "across quadrants."
  • I didn't implement optimizing features (dropout, reducing LR, etc.)

Adjustments

  • Instead of just blacking out three quadrants and leaving one, I'll try adding some noise (a random number from 0-255) to the blacked-out three to see any differences. I hypothesize this can mimic or simulate knowledge across quadrants, slightly improving performance.
  • 4 3674F2
  • 5 E9C47C
  • D7DC98
  • Update. Ambient noise drops accuracy a lot, both with one fixed pattern reused across federations and with a fresh pattern generated each time.
  • F6FFBC

Next Steps

  • I'll start working on implementing CIFAR-10 with a similar architecture.

Summary

  1. Performance. The VFL model peaks around 93% accuracy within 10-15 epochs. A full CNN trained on the whole dataset gets to 98% quickly.
  2. Patterns across quadrants. The big worry is whether the network can pick up patterns that span different quadrants.
  3. Record linkage. The current setup ignores record linkage, the step that tells which pieces across quadrants belong to the same sample. Adding it might be what gets us past 95%.

Potential Solutions

  1. Image IDs. Give each image and its quadrants a unique numeric ID. The hope is that the network then learns how the quadrants relate.
  2. Training variations. Use those IDs in different ways, from one example at a time to batches. Speed is the worry here.
  3. Noise. Fill the blacked-out parts of the image with random noise. This might fake some knowledge across quadrants and push accuracy up.

Other Considerations

  • Testing. There is a separate test set. Every quadrant learner and the averaged learner use it only for evaluation.
  • Code review. I shared the relevant code on GitHub so others can dig in and help tune it.

Feedback and Recommendations

  1. Careful with noise. Use a much smaller noise range instead of 0-255, so the network doesn't overfit to it.
  2. Talk it through. This needs in-person discussion or longer meetings before we settle on an approach.

Status

✅ SUCCESS

Further Actions

Superseded by anaclumos/malmantile

Backlinks10