I play Roblox with my son and his friends a lot. Some kids use how much Robux you have as a status thing, but I've been surprised how little griefing and bullying I've seen. I do get called "bacon hair" because my avatar has the default skin (which has hair that looks like strips of bacon).

Noobskin is a phrase used in a similar situation. If you didn't pay for your avatar people notice.

We've moved from Teams, to Slack, and back to Teams over the last 2 years. Teams has come a long way since 2017, but the basic chat functionality is still pretty far behind Slack.

Next time, I'll stick with Slack.

It says a lot that you consider folks you're having a conversation with "opponents".

Anybody who is arguing with you is your opponent. It's not so dramatic word :)

Having an external motivator is often a helpful way to develop a new habit.

Motivation: I had better solve this issue myself or I will need an external motivator which will inconvenience me in some way.

I first parsed this as an app to help you message Kevin Rose quickly.

This particular collection of koans was assembled and published in 1919, so I guess copyright has expired.

I wouldn't say "solved", as it's still pretty easy to accidentally overwrite old versions, but it was a step in the right direction. VMS is full of good ideas that never went anywhere.

From the context, it seems like mame was trying to say that Ruby is not a security-focused project, so the core team has not attracted many volunteers who are familiar with SSL/TLS.

I inferred from this not that Ruby team doesn't care about security, but that they lack the expertise to handle it properly. They're aware of that, and choose to leave these decisions up to the experts.

It's a reasonable position, but, as a user, "We don't know how" doesn't help me any more than "We don't care".

Merb was never a fork of Rails. It was a separate project, initially created to address a particular shortcoming of Rails (file uploads, IIRC), and grew into a competing implementation that solved a lot of the same problems that Rails did in a simpler, more elegant way. The Rails core team realized that Merb did a lot of things better and absorbed most of that goodness.

SlimGems isn't Merb. It's not new, it's not doing anything better. The only thing it has going for it is "Hey, it's not being run by these same assholes." Well, that doesn't help me much. SlimGems isn't going to ship with Ruby 1.9.3, and it doesn't solve any problems that RubyGems doesn't solve. Loren could be making a better RubyGems, but instead he's making an older RubyGems.

Well, the other thing it has going for it is that it works. So far I've had no problems with SlimGems on the half dozen or so projects I've tried it with. The same cannot be said for RubyGems 1.8 and most of the releases since 1.3.7.