AfterSnow

815 posts

AfterSnow banner
AfterSnow

AfterSnow

@0xAfterSnow

Building Backend & Web3 infra | Payments | Technical Writer Shipping real products ~ endless threads @AmongFriends_io | @Tgcleaner

127.0.0.1:8000 Katılım Ekim 2020
96 Takip Edilen300 Takipçiler
Sabitlenmiş Tweet
AfterSnow
AfterSnow@0xAfterSnow·
Hi, I'm Shagbaor Agber, a full-stack developer and Web3 builder focused on building scalable systems that generate utility and revenue in the real world. I have experience in backend architecture, smart contracts, and product engineering-from building high-performance APIs with Django and FastAPI, to writing on-chain logic for decentralized applications. In the last year, I've been building systems centered around: - Secure and scalable backend architecture - Web3 Products such as Betting Protocols, Staking Systems, and On-Chain Logic - Automations and Micro-Products with monetization built-in I don't just ship products; I build systems that can handle significant growth. Some of the technologies that I use include: Python (Django, FastAPI), Solidity, Next.js, Postgres, and a host of Web3 tools. I am currently exploring opportunities in product engineering, Web3 infrastructure, and monetizable micro-SaaS.
AfterSnow tweet media
Technical Ben@TechnicalBben

Hi, I’m Benjamin Olamide, a lifecycle and email marketing specialist. Most brands chase more traffic. I focus on, revenue, retention and customer lifetime value. I build automated flows and lifecycle systems that turn first-time buyers into repeat customers and keep revenue compounding over time. Experience includes working with Webtoons. Tools stack: Klaviyo, Braze, Mailchimp, HubSpot HTML, CSS, Liquid. J You?? Tell us about what you do.

English
0
3
17
288
AfterSnow
AfterSnow@0xAfterSnow·
Lol, now watch that rate raise from another IP
Avi Patel@avipat_

We have removed Kled from the Nigerian app store and IP banned the entire region. The first thing I would like to say is I have nothing against Nigeria. I have a ton of friends from this region and these were some of our earliest app adopters. Genuinely, thank you all for the support. Kled has been up and running and out of beta for 4 months now. We have paid out hundreds of thousands of people for their data, and our users have uploaded over 1 billion assets onto our platform. After several months of uploads we found that Nigeria had a ≈95% fraud rate. Instead of real, usable data, users were uploading pictures of black screens, duplicate photos, internet generated images, AI generated images, etc. at an unimaginable scale. In comparison, Malaysia, Indonesia, and the Philippines have a less than 10% fraud rate across 10x the userbase size. Our fraud system is fast to catch these issues but the level of complexity of these schemes is getting out of hand. This weekend we were flooded with thousands of fake Japanese passports and identity cards with Nigerians photoshopped onto them in our KYC system. That was the final straw. As a startup we can't afford to eat the costs of that data overhead, so we temporarily removed the app from the region while we improved our fraud detection and banning system to quickly filter out bad actors when the time is right. On top of all of this, every time we make a post there is someone asking us to bring the region back within seconds. We hear you, but it's gotten out of hand. We've made this decision with great care. We love everyone who has genuinely supported Kled from Nigeria, and we hope to return when the time is right. -Kled Team

English
0
0
0
5
Kyriakos
Kyriakos@Kyriakos_Pelek·
@0xAfterSnow ship a small free tool, then document how it works
English
1
0
0
6
AfterSnow
AfterSnow@0xAfterSnow·
how to grow a Web3 product (with solid engineering and distribution): first, i'd build for discoverability. launch a free tool that solves one specific pain - bulk cleanup, rate-limited automation, anything people search for. make it work before you make it pretty. write one technical post explaining how it works under the hood. then i'd build trust through transparency. document the auth flow, explain what data you store and why, publish the architecture decisions. builders trust builders who show their work. next, i'd treat distribution like infrastructure. one working product becomes a thread, a short demo, a write-up, and a reddit comment in the right subreddit. find where your users already complain and show up there with a solution, not a pitch. i'd also automate the boring ops early. session management, rate limiting, cleanup jobs - build it once, make it reliable, then tell people about it. the product is the marketing. and i'd ship lead magnets for the technical crowd: open-source a small piece of the stack, publish a breakdown of the MTProto implementation, drop a free tool with a clear use case. the builders winning in Web3 aren't the loudest. they're the ones who made something that actually works and documented it well enough that others trust it. you still need to know who has the problem and why they haven't solved it yet. build that answer into the product itself.
English
2
0
2
29
AfterSnow
AfterSnow@0xAfterSnow·
What every builder needs to understand: Shipping a broken product is closer to a working one than planning a perfect one. Broken products become polished over time. Planning becomes irrelevant over time. (TG Cleaner started the same way.)
English
0
1
3
18
AfterSnow retweetledi
Jon - TechX'26
Jon - TechX'26@jorniks·
As a community organiser/manager, how do you collect your community data and ensure it is accurate?
English
0
2
2
42
AfterSnow
AfterSnow@0xAfterSnow·
What people think building in Web3 is like: shipping cool tech and getting paid What building in Web3 is actually like: believing in something enough to keep building when no one's watching
English
0
1
3
24
AfterSnow
AfterSnow@0xAfterSnow·
A senior engineer once told me: "Your architecture is not a decision. It's a habit." Most builders think they win by picking the right stack early. But that's not how durable systems work. Every technical decision you make starts decaying the moment you ship it. New tools emerge. Scale exposes cracks. What solved yesterday's problem becomes tomorrow's bottleneck. The builders who last aren't the ones who chose well once. They're the ones who keep revisiting, refactoring, and compounding their understanding of the system. Being wrong about a design call is fine. Refusing to revisit it isn't. Your stack is not a noun. It's a verb.
English
0
0
2
8
AfterSnow
AfterSnow@0xAfterSnow·
Stuck is a mindset. Stuck builders.. 1. Ship nothing waiting for perfect 2. Blame the market, the timing, the tools When I was grinding on side projects with zero users I always knew two things. 1. I understood systems most people ignored 2. That knowledge compounds And that's enough to keep building through the noise. You're not stuck.. you're just pre-traction.
English
0
2
5
23
AfterSnow
AfterSnow@0xAfterSnow·
3 things builders avoid admitting that are true: - Your stack won't save a product no one wants - Clean infrastructure starts with cleaning up what you don't need (TG Cleaner does this for Telegram) - Shipping slower than you think is still shipping
English
0
0
5
20
Victor
Victor@echo_vick·
@0xAfterSnow Bruh😂😂😂😂...you hallucinate pass claude
English
1
0
1
13
Victor
Victor@echo_vick·
Claude and Colos, I no come know which one dangerous pass.
English
20
9
89
6.6K
Victor
Victor@echo_vick·
With the increased rate of challenges on this app “I can build your app in 2 weeks” saga What if we have a platform for devs or vibe coders, (as the case may be) where this challenges can happen, be tracked and be judged It will auto create repos for the participants, show progress publicly to everyone. And people can also place bets and vote🤔 Make all this nonsense stop
English
27
5
78
5.9K
AfterSnow
AfterSnow@0xAfterSnow·
@echo_vick Casually tasted it last year I didn't last 2 min 😭😭 They told me things I did. i said, "No way." They showed proof 😭💔
English
1
0
1
9
AfterSnow
AfterSnow@0xAfterSnow·
Someone asked how to write cleaner backend code. The best approach is to strip the logic down to its core responsibility, then ask how broadly that single responsibility can be reused. You have to strip it first, though, or there will be hidden coupling left in it that blocks every refactor.
English
0
1
7
21

Keşfet

@Kyriakos_Pelek @Tgcleaner @echo_vick @AmongFriends_io @elonmusk @BarackObama @taylorswift13 @cristiano