flymasterv

I'd build my own NTFY client to enable two-way chat. It's not something I'm seriously considering, because it's obviously a bad idea, but that's about where I am.

I'm searching for a simple, self-hosted chat system that allows me to host unlimited bots and send messages (with notifications) to my iPhone easily.

I currently have an XMPP server running, which is fine, I guess. I've looked into chatMail. I have considered hosting an IRC server.

At this point, I'm considering just setting up my own NTFY server and writing a chat client for it.

Does anyone have any ideas for what the lightest weight, simplest solution might be?

Well, you also point it at Japan.

I was a summer intern for about 3 months. All I really remember was lunch on the Groof and my first experience with Free Tech Soda. I handled a lot of the i18n on the demo stuff, like the chess game.

Huh. I somehow missed that 24 years ago. Joel’s right.

I worked for Ray Ozzie at Groove, and I still mourn what that could have become. It was, in many ways, a modern reimagining of Notes, but that meant it had the same problem: customers and users thought they were using a product, but they had actually bought a PLATFORM. It was a digital choose your own adventure, but people really wanted a better chat room.

Same thing with Google Wave, really.

Boston to Bingham, Maine in about 4 hours. I was in my car and headed home about 10 seconds after totality ended and made it home in 5 hours. Totally worth it.

Means the same thing here.

React? Lucky. I wrote Closure (with an S) at GOOG in anger 5 years ago, and only stopped because I switched teams.

Thank you!

Google’s tooling was, hands down, the worst I have ever encountered. I did 10 years at GOOG, 3 at AMZN, 4 in research, and another 5 at companies you have heard of but wouldn’t be impressed by, and every day GOOG infuriated me.

Cool project, but my question is: what are those buttons?

“Line of work”? I’m fascinated by this. Diner waitress? Cop? Carnie? Cockney bingo caller?

On the other hand, while I completely agree about the C codebase, the Javascript is at least comprehensible. I've toyed around with adding a feature or two, and almost got there.

The problem here is that limited overs cricket has been modified from regular test cricket in a way that fundamentally alters the strategy and flow of the game to increase the action and decrease how long it takes to play.

Because of those concessions to speed and entertainment, some rules that worked ok in test cricket break the game in limited overs. In this case, NZ was down to their “final over”, a concept that doesn’t exist in test cricket. Underarm bowling basically removes overs from the game and can guarantee a win for the bowlers, but in test cricket, would lead to a draw.