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
Why Korean Banks Suck

Why Korean Banks Suck

Warning

Over a year old. May be outdated

Banks falling behind on tech is a familiar story in the U.S., but I'm confident Korea takes it to the next level. To check your balance, you install seven different programs and plugins that run all the time and slow your computer down. To make any transaction, you create a digital certificate file you can't export.

Where it all began

It starts with the Export of cryptography from the United States. In 1999, with the internet booming, Korea couldn't properly use 128-bit AES encryption, so it started with a weakened 40-bit system. Later it built its own 128-bit system that needed ActiveX and made that the standard (SEED).

The U.S. lifted the export restrictions in 2000. Korea kept SEED and ActiveX anyway. ActiveX eventually went away, replaced by mandatory .exe security programs that run on your device all the time. As Wladimir Palant found out, these programs are a pain to use and don't even follow ancient security practices. They're built with a 15-year-old Visual Studio, causing avoidable security problems like simple Buffer Overflows Attacks. But why? Why aren't they fixing any of this? Here's what I see.

Dodging Responsibilities

Korean law says this.

A financial institution or electronic financial provider shall be responsible for compensating the user for damages caused by accident caused by forgery or alteration of an access medium, contract signing, or electronic transmission or processing of transaction instructions.

But some Korean banks figured out they could use the complexity of their security systems to push the blame onto customers after a breach. Add some very vague terms and conditions, and the bank points to them as proof that the customer knew the risks and agreed to take responsibility for any damage.

Limited Room for FDS

Unlike the U.S., which has a tipping system, Korean banks have no deferred transfer system by default. Every transaction is instant and irreversible. That makes a fraud detection system (FDS) much harder to run, because there's barely any time to catch and stop a fraudulent transaction before it goes through. A deferred transfer system like the one in the U.S. gives banks more time, since they can cancel or reverse a transaction before it's processed. Korean banks instead count on each customer to watch their own account for anything suspicious and report it. In other words, catching fraud is the customer's job.

Lack of Competitions

The Korean market is known for weak competition in some industries, banking included. A few reasons.

  • Linguistic and regional barriers. Korean is a unique language, and many Korean consumers would rather deal with companies that speak Korean and get Korean culture.
  • Resistance to external influence. Koreans have a lot of national pride and are often wary of outsiders playing a big role in their economy.
  • Lobbying and Corruptions. There are corruption allegations against Korea Financial Telecommunications and Clearings (KFTC), one of five authorized certification companies, and it makes millions of dollars. KFTC is supposed to be a public interest organization set up by the state. Still, high-ranking Financial Services Commission officials are accused of colluding with it and landing jobs there after retirement. Makes you wonder why those seats are so attractive.
  • Perception of overseas banks. Using an overseas bank or doing business with a foreign company is often seen as unpatriotic or unethical.

So banking, like the rest of the Korean market, doesn't get much competition.

Is there any hope?

Some. New fintech companies like and have shaken up traditional banking with better digital products built around the customer, and Korean consumers finally have options. As fintech grows and people expect more, the old banks will have to adapt to keep up. There are still plenty of obstacles, but these new players show there's room for more competition and better banking in Korea.

Backlinks4