I have a story to tell, about the demise of one of the largest internet forums in my language.

About ten years ago, when smartphones just started appearing, the forum did not have a mobile version, and there are various 3rd party clients on the App Store or Android Market.

Later on, one of the largest 3rd party client was blocked, because of they hammering the forum's servers too hard,. Or something about caching and stealing ad revenue.

Then a couple years later, in 2017, the 3rd party client's devs launched its own forum reusing the client's name. It exploded in popularity and quickly took over as the most popular message board among the youth.

The old forum now has a sort of boomer or mentally ill stigma to it.

I hope to see Apollo go down this route.

Oh, and I think both forums in the story did not monetize as hard as reddit going to paid awards and memberships.

One more thought: Keep the Apollo UI or whatever thing the users are most familiar with. Most of them do not care if it is fediverse or open source or backed by web-scale k8s, they only want it to just work (tm) good enough to post things on it. Eat the lunch you prepared yourself.

How is your attitude not equivalent to "I can't trust myself to see things I disagree with, I am so weak-willed that there is the horrific danger that I will start believing them"?

There are reasons someone might want to find those links, even if they disagree with them. When Google hides them from you without your consent or ability to opt out, they're treating you as if you were a child. Or perhaps more like livestock.

Why is this a pretty obvious connection vs. just the pragmatic reality of having access to the Google building?

The factors that play into suicide are numerous, and there is no apparent reason that Google was a causal factor.

This is also not to say that they aren’t, but to point out that speculation about this has zero standing.

Comma.ai is another great example of CANBUS hacking. I'm a bit worried there are a bunch of zero days sitting out there on CAN implementations. It's such a complicated system.

Every single girlfriend I had, I asked her to get off contraceptives because of the medical dangers and I didn't want to be responsible for any problems associated with it. Instead I took responsibility for making sure she wouldn't get pregnant. One of my girlfriends actually got mad at me because I was *too* careful about getting her pregnant, and interpreted that as me not wanting to get married to her (which since we're not together ended up being true I guess).

This doesn't work for everyone but I'm fairly responsible, and no accidental pregnancies, so it worked for everyone I was with. The same way went for my wife as well, and we have 2 kids now, with no accidentals ones. I'm going to teach my son this as well, that the responsibility is on both parties but as the man you need to control what you can control and don't leave things to chance, especially something as life changing/destroying as an accidental pregnancy.

then FutureMotion must equip all onewheels with safety wheels on both sides. Also called as Fangs bumper wheels.

physics is no excuse for lousy engineering from FutureMotion and complete disregard of life threatening diving condition!

Reading this warning, I don't understand why now? Is there a bug with onewheels that are causing this injury/death? Or is it just rider error doing a dangerous activity?

Is the CPSC going to start warning against purchasing Rossignol skis or Santa Cruz mountain bikes because their respective activities are dangerous?

Participation in action sports and high-speed transportation will result in a higher expected mortality rate over the mean. I don't know who in their right mind would think flying down a street at >15mph on a single wheel would be _not_ incredibly dangerous.

Let adults make stupid decisions - whether that's jumping off a building with a parachute, riding a bike down a recklessly steep hill or hurtling my body down Main St. on a sideways unicycle.

Wouldn't there be all sorts of human detection that they could do, similar to how game cheat engines work? A human is going to move the mouse across elements, drag, poke the screen, be slow, etc, and all in fairly predictable ways. Some API calls almost certainly require human interaction, where some interaction graph could be feed as a key to the API. It's cat and mouse, but at some point the mouse is going to get tired.