Why do you project 10% growth over the next 6 months? Looking at the other metrics on that page which have history (total unique likers, posters, followers), the numbers are flat or declining.
That shape doesn’t seem great for a social media company.
Modern shareholder law is definitely a strange business. People have successfully brought suits for a variety of bad-but-not-illegal causes. There were a lot of lawsuits about sexual harassment and climate change, I believe the theory being that “bad thing will make the stock go down, and the company didn’t disclose that they might do the bad thing”. Then more recently a lawsuit against target proceeded (I don’t see whether it’s completed yet) despite target having disclosed the risk (in this case of their DEI activity).
The claim in the suit is notably that the company failed to disclose the behavior, not that they did the behavior (Target notwithstanding), which mostly agrees with your line of questioning.
Eh, doorbell cams aren’t that controversial (ad aside). A lot of people have them already, both from ring (with the concomitant privacy issues) or from other providers (with different but similar issues).
They’re controversial on hacker news but I don’t think people in the “real world” care all that much.
How that connects to the meta glasses is certainly up for debate —- the doorbells provide a lot of value to the user (know who is at the door remotely!), the glasses are more of a mixed bag.
The article goes into detail about how this level of morphine in the breastmilk could not have given the baby a lethal (or even clinically effective) dose.
Furthermore, Koren lied about what the tests showed the stomach contents to be: he omitted codeine entirely. Codeine (per the article) would not be expected to be transferred by breastmilk -- it's metabolized into morphine to be effective.
The article clearly lays out that the answer is yes. It points to specific ways the researcher adjusted their reporting to mislead readers. I think the key here is where Koren attempts to specifically account for the stomach content explanation: he misrepresents the lab results and claimed they showed the opposite of what they did.
One of the minigames in the game is "upvote post". Your username is the username of the post. I have no idea what the content of the post is, it went by too quickly for me to read it.
The varroa mite has been pretty effective at removing them so far. Today honeybees are essentially livestock, to the point where any given bee you see is very likely owned by someone.
With a straight shot, latency from one coast to the other is at least 50 ms [0]. A more typical route is on the order of 80 ms.
That's definitely noticeable for latency-sensitive actions. I recently switched a server from Oregon to New Mexico, and I notice the latency increase with mosh.
Moreover, there's not a lot of timezone difference between the east and west coasts of the US. Going someplace like Europe is more like 180 ms.
I've played games with a ping like that, but a lot of the ping was my wifi. Doubling the latency would not make the game a better experience.
This could work well for certain types of game, those that are a little less latency-sensitive. But in general the latency is still a big issue.
[0]: speed of light in fiber is ~ 100e6 m/s, around 3000 miles between coasts
From my experience with Java-style hard module dependencies, this makes it extremely difficult to refactor anything touching external interfaces.
You say this forces you to think ahead, but predicting the future is quite difficult. The result is that you limp along with known-broken code because it would take so much effort to make the breaking changes to clean it up.
For example, lets say you discover that people are frequently misuing a blocking function because they don't realize that it blocks.
Let's say that we have a function `bool doThing()`. We discover that the bool return type is underspecified: there's a number of not-exactly-failure not-exactly-success cases. In a monorepo, it's pretty easy to modify this so that `doThing()` can return a `Result` instead. With multiple repos and artifacts, you either bring up the transitive closure of projects, or you leave it for someone to do later. For a widely used function, this can be prohibitive. That makes people frequently choose the "rename and deprecate" model, which means you get an increasing pile of known-bad functions.
That shape doesn’t seem great for a social media company.