six years running online communities. now writing about who your technology actually works for. funny about tech, serious about the deal.

Joined July 2021
people in a community i ran were convinced i wasn't a real person. a bot, or a company account with staff taking shifts. you can't moderate your way out of that one. i went on the livestream and said hello. that fixed it. nothing else had.
1
6
572
the loudest person in a community is almost never the one you want handling something. the one you do want rarely puts their hand up. but every time i asked, they said yes straight away. the bottleneck was never willingness. it was noticing.
3
289
"this might kill everyone" is now something you can say about your own product on a tuesday and still have a normal wednesday.
3
346
steam tells you at checkout that you're buying a license, not a game. it's in the cart, right before you pay. it took a california law to get that sentence written down. the arrangement never changed. it just got printed.
1
4
578
the law is california's ab 2426, in force since 2025. it's why the wording changed on a lot of storefronts at once. worth checking what your own library actually says you own. most people have never read it and it's two clicks away.
1
125
52% of game developers now say generative AI is making their industry worse. two years ago it was 18%. the support that's left is concentrated in executives, not in the people actually shipping. that gap isn't a games story.
3
412
fogo's chain is back up and 237m of the stolen tokens are gone for good. on how the foundation was compromised: "we'll share further information as the investigation continues." that isn't a date. they just spent three days learning what fills that gap.
1
3
516
the argument against me: an investigation with law enforcement in it can't be scheduled, and a missed date is worse than a vague one. fair. my answer is a next-update time isn't a deadline for answers. it's a promise to show up, and you can keep that one either way.
2
132
certik puts august at around $215m in confirmed losses. $41.5m of that was phishing. that part isn't a contract problem. it lands on whoever runs the discord. the exploit gets a postmortem. the phishing wave gets a pinned message nobody reads.
1
3
458
there's a fake foundation account running a compensation vote for a chain that can't produce blocks. fogo has been halted since saturday and the halt notice is still the last word from the project. silence during a halt isn't neutral. somebody fills it.
1
8
619
the checks, for any chain that goes quiet on you. the real account existed before the incident, so scroll its history. a bought checkmark is not verification. and compensation announced before a restart date is the wrong order, which is usually the tell.
126
update: cronos is back online. validators rolled the chain back to before the exploit. that answers today. it also hands every user on that chain a new question: who can rewind this, and what has to happen before they do it again. the postmortem is the easy part.
cronos is halted. crypto.com says its app and exchange are running normally. people are mixing those two up. everything on the chain is frozen right now, including positions that never went near tectonic. no restart time has been given yet.
1
8
989
the argument for it: the rollback kept most of the proceeds away from the attacker, and a validator set coordinating that fast is a functioning emergency response, not a failure. fair. my answer is it works once. what matters is what the community expects the second time.
2
172
cronos is halted. crypto.com says its app and exchange are running normally. people are mixing those two up. everything on the chain is frozen right now, including positions that never went near tectonic. no restart time has been given yet.
1
1
1
1,430
three things worth doing while it's down. screenshot your open positions and balances as they stand at the last block. check pending transactions on the explorer so you know what actually went through. ignore anyone who dms you a recovery link. no support team dms you first.
168
Update to my post on Wednesday: I'm no longer community lead at @veilboundgg. I looked at things more closely after announcing and concluded it isn't the right fit for me. For clarity, since I disclosed the arrangement when I announced it: I received no compensation from the role. No criticism of anyone intended and nothing more to add. Leaving the original post up rather than deleting it.
Twelve days ago I posted that I was starting a new chapter and open to what's next. This is it. I'm community lead at @veilboundgg as of today. Part time, paid, and I'm disclosing that here and in my bio so you can weigh anything I say about them accordingly. Here's the part I like: I'd already been playing for about a week before any of this was announced. Quietly, on an account nobody was paying attention to, and I'm nearly level 50. I didn't want to walk into a community and ask what the thing is like. I wanted to have opinions about it first. Five years at Holochain and Holo taught me the shape of the job. Before that a Web3 poker platform Coinpoker, which is where I actually learned it, because nothing teaches you about people faster than someone who has just lost something and wants to tell you about it. The scope is community, events, support, in game, all of it. My first job is the same as it always is. Find out what's genuinely broken before touching anything, and get people telling me the annoying stuff early rather than politely. To everyone who replied to those leaving posts and said find something good: I think I did.
2
3
966
Twelve days ago I posted that I was starting a new chapter and open to what's next. This is it. I'm community lead at @veilboundgg as of today. Part time, paid, and I'm disclosing that here and in my bio so you can weigh anything I say about them accordingly. Here's the part I like: I'd already been playing for about a week before any of this was announced. Quietly, on an account nobody was paying attention to, and I'm nearly level 50. I didn't want to walk into a community and ask what the thing is like. I wanted to have opinions about it first. Five years at Holochain and Holo taught me the shape of the job. Before that a Web3 poker platform Coinpoker, which is where I actually learned it, because nothing teaches you about people faster than someone who has just lost something and wants to tell you about it. The scope is community, events, support, in game, all of it. My first job is the same as it always is. Find out what's genuinely broken before touching anything, and get people telling me the annoying stuff early rather than politely. To everyone who replied to those leaving posts and said find something good: I think I did.
Welcome @NathanLenae as our community lead. Formerly ex-lead of @Holochain. You will see him around shortly. Some might say he's been here for a minute.
8
6
3
33
4,703
cosmos labs isn't naming the bug, the chains, or a restart time. correct call, it protects everyone still unpatched. it also leaves every community manager on a cosmos evm chain announcing an incident they can't describe. hardest post in this job and nobody trains you for it.
1
1
10
710
the version that works: state the fact, state the boundary, state the next update time. "we've halted. we can't share the vulnerability yet because other chains are still patching. next update 09:00 UTC whether or not we have news." the third line is the one people skip and it's the only one that buys you quiet.
1
182
The coldcard hackers are sitting on a pile of bitcoin they can't move. so people started messaging them on-chain. one offered to launder it for 7%. cold outreach has reached the point where you're pitching your services, inside a bitcoin transaction, to somebody who is definitely never going to reply.
1
8
787