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
인터넷 공사 (20誠鉉)

인터넷 공사 (20誠鉉)

Warning

Over a year old. May be outdated

때는 바야흐로 2020년 1월 24일이었다.

나는 를 졸업하고, 여기저기 떠돌다 집에 온지 한 1-2주 정도 지났었나?

어쨌든 그런 상황이었다.

우리 집에 이사 오며 2010년쯤 인테리어할 때 부모님은 일부러 내 방에 인터넷이 안 되게 하셨었다.

공부하는 학생들 공신폰 쓰게 하는 그런 심리였을까.

어쨌든 우리 집의 유일한 와이파이/인터넷은 제일 안방에서만 터졌고,

내 방은 대문에서 가장 가까운 방이었다.

벽 두어개는 가뿐히 넘어야하는 내 방에서는 신호가 거의 잡히지 않았다.

어느 정도였냐면 내가 새벽에 몰폰하러 안방에 가까이 서서 서있다가 부모님에게 걸렸었을 정도.

하여튼 내 방은 인터넷 음영 지대였다.

민사고를 졸업하고 미국 유학을 갈 때까지 반년 가까이 집에 있어야 했는데,

인터넷이 안 되는 방에서 산다는 것은 개발자로써 전혀 말이 되지 않았다!

또 나는 을 중시하는 사람인데,

스마트 홈이나 라즈베리파이, 컴퓨터 등이 열심히 일을 하면서 오케스트레이트되려면

LTE나 셀룰러에 의지할 수 없었다.

예를 들어 당시에는 iCloud 백업이나 프로세싱, 자동 업데이트 등은 모바일 데이터로 할 수 없었다.

내가 아무리 생각해봐도, 우리 아파트는 엘리베이터에서 내리면 왼쪽과 오른쪽에 집 입구가 있는 그런 전형적인 아파트였는데, 내가 건물을 지어도 가운데 인터넷 배선을 깔고 나뭇가지처럼 양쪽 집으로 통하게 설계하지, 양쪽에서 2개의 배선을 깔지는 않을 것이었다.

즉, 어떤 구조로든 대문에 가까운 내 방 근처에 인터넷 배선 "상류"가 있는 것이고, 안방 와이파이까지 배선이 이어지는 구조였을 것이다.

이런 사고를 바탕으로, 내 방 근처 벽 안 어딘가에 인터넷 선이 있을 것이라는 합리적 추론을 했고,

인터넷에서 건물 도면 같은 것을 찾아보고 전화선과 TV선 포트가 있는 곳들을 하나하나 분해해보며 건드려보기 시작했다.

그 중 하나의 포트를 깊숙한 곳까지 들여다보기 위해 간이 잠망경을 만들어 뒤져봤다.

그때!

1F2353

바로 위와 같은 도선을 찾았다.

거의 하루종일 집안을 뜯어보며 찾은 유레카 모멘트였다.

또 인터넷 선들이 절연테이프로 묶여 있었는데, 나는 이것이 인테리어 중 내 방에서 인터넷 포트를 없애버린 흔적이라고 판단했다.

이제 남은 일은 이 인터넷선을 다시 끊고(!) 전선 형태로 만들어 내 방에 Relay Wi-Fi 하나를 두면 될 일이었다.

그래서 그 순간 나는 다이소에 가서 랜선 하나와 그럭저럭 괜찮은 와이파이 기계를 샀다.

그 다음 내가 발견한 인터넷 선을 잘라버리고(!) 내가 사온 랜선도 잘라서(!) 둘의 구리선을 하나 하나 이어붙였다.

마지막에 절연 테이프로 감아서 안정적으로 연결되게 만든 다음,

와이파이 기계에 연결해서 내 방에 신호를 하나 쏘게 만들고,

안방으로도 신호를 Relay해서 보내줄 수 있게 연결했다.

결과는 대성공이었다.

9B3B28

C6F520

툭 하나 잘못되면 우리 집 전체 인터넷이 고장나고, 업자를 불러서 벽을 뜯어서 배선 공사를 다시 해야하는 순간이었는데,

어쨌든 무슨 배짱인지 과감히 해버렸고 성공적으로 인터넷이 됐다.

인물 서적을 읽어보면 항상 첫 장에 "~누구누구는 어릴 적 TV를 뜯고 재조립해서 작동했다..." "~누구누구는 자동차를 분해하고 뜯어보며 학습했다..." 같은 내용이 나오는데, 나도 비슷한 일화가 생긴 것 같아서 재밌었다.

완전 어릴 적에 한 일은 아니지만, 어릴 적에 한 것보다는 스케일과 리스크가 있었다고 생각하니까 뭐 쌤쌤으로 치자.

Backlinks2