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
국내 은행 서비스가 나쁜 이유

국내 은행 서비스가 나쁜 이유

Warning

Over a year old. May be outdated

노트

이 글의 원문은 영어입니다.

은행이 기술에 뒤처지는 건 미국에서도 흔한 얘기지만, 한국은 거기서 한 단계 더 간다고 확신한다. 계좌 잔액 하나 확인하려 해도 프로그램을 7개나 깔아야 하고, 거래를 하려면 한세월 걸려서 공인인증서 파일을 만들어야 하고, 계속 돌아가는 플러그인 때문에 컴퓨터는 느려진다.

모든 것의 시작

모든 건 미국의 암호 기술 수출 제한에서 시작된다. 인터넷이 급성장하던 1999년, 한국은 128비트 AES 암호화 기술을 쓸 수 없어서 취약한 40비트 보안 시스템으로 출발했다. 그 뒤로 액티브X가 필요한 128비트 보안 시스템을 직접 만들어서 SEED라는 표준으로 삼았다.

2000년에 미국이 수출 규제를 풀었는데도 한국은 계속 SEED와 액티브X를 썼다. 액티브X를 걷어 낸 다음에는 기기에서 .exe 보안 프로그램을 계속 돌리도록 의무화하는 쪽으로 갈아탔다. 블라디미르 팔란트가 밝혀낸 것처럼, 이 프로그램들은 불편할 뿐 아니라 요즘 보안 기술 수준에도 한참 못 미친다. 게다가 15년 된 Visual Studio로 만들어져서, 단순한 버퍼 오버플로 공격처럼 충분히 막을 수 있는 보안 문제도 고칠 생각이 없어 보인다. 근데 왜 아직도 안 고쳐질까? 몇 가지 이유를 보자.

책임 회피

국내법에는 이렇게 적혀 있다.

금융기관 또는 전자금융업자는 접근매체의 위조나 변조로 발생한 사고, 계약체결 또는 거래지시의 전자적 전송이나 처리과정에서 발생한 사고 때문에 이용자에게 손해가 발생한 경우에는 그 손해를 배상할 책임을 진다.

근데 일부 국내 은행은 보안 시스템이 복잡하면 사고가 났을 때 책임을 고객에게 떠넘길 수 있다는 걸 알아챘다. 모호한 약관을 들이밀면서, 이 복잡한 시스템을 고객이 위험을 알고도 손해를 떠안기로 동의했다는 증거로 쓰는 것이다.

FDS를 들일 틈이 없다

지연이체 제도가 있는 미국과 달리, 국내 은행은 기본적으로 지연이체를 하지 않는다. 그러니까 모든 거래가 즉시 처리되고 되돌릴 수 없다. 거래 전에 사기를 잡아내서 멈출 시간이 거의 없으니, 이상거래탐지시스템(FDS)을 만들기가 훨씬 어렵다. 미국에서는 지연이체 같은 장치 덕분에 이체가 처리되기 전에 거래를 취소하거나 되돌릴 수 있어서, 사기 거래를 찾아내고 막을 시간을 더 벌 수 있다. 반면 국내 은행에서는 고객이 직접 자기 계좌에 수상한 움직임이 없는지 지켜보다가 은행에 신고해야 한다. 사기 거래를 잡아낼 책임이 고객에게 있고, 은행은 신고가 들어와야 움직인다.

경쟁이 없다

한국은 은행을 비롯한 일부 산업에서 경쟁이 별로 없는 시장으로 알려져 있다. 여기엔 몇 가지 이유가 있다.

  • 언어와 지역의 장벽. 한국어는 고유한 언어고, 많은 한국 소비자는 한국어를 잘하고 한국 문화를 아는 회사와 거래하는 걸 선호한다.
  • 외부의 영향을 꺼림. 한국인은 국가적 자부심이 강하고, 외국이 경제에서 큰 역할을 하는 걸 경계하는 경우가 많다.
  • 부패와 부정청탁. 금융결제원은 공인인증 업체 5곳 중 하나이자, 한 해 수십만 달러를 버는 사단법인이다. 이 금융결제원에 부패 의혹이 제기됐다. 금융위원회와 기획재정부의 고위공무원들이 퇴직한 뒤 금융결제원에 들어가는 등 업체와 결탁했다는 의혹이 있어서, 부정청탁이나 부패에 얽힌 게 아니냐는 말이 나오고 있다.
  • 해외 은행을 보는 시선. 국내에서는 해외 은행을 주거래은행으로 쓰거나 외국 기업과 주로 거래하는 걸 "비애국적"이거나 "비윤리적"이라고 보는 시선이 있다.

이런 이유로 은행을 비롯한 한국 시장에는 경쟁이 별로 없다.

그래도

한국 은행권은 어렵고 경쟁도 별로 없지만, 나 카카오뱅크 같은 새 핀테크 기업이 나타나면서 좋은 변화도 좀 생겼다. 이 회사들은 새로운 디지털 서비스와 고객 중심의 접근으로 기존 은행 업계를 뒤흔들고, 한국 소비자에게 선택지를 더 넓혀 주고 있다. 핀테크가 떠오르고 소비자의 기대치도 바뀌면서, 한국의 전통적인 은행들은 살아남으려면 바뀔 수밖에 없다. 은행 업계에는 아직 넘을 산이 많지만, 이 새 플레이어들이 한국 은행 업계에 경쟁과 혁신을 더 불러오기를 기대한다.

Backlinks3