Live data from Hacker News

Twitter is threatening to sue Meta over Threads [pdf]

cdn.sanity.io

111–120 of 200 posts

Re: Twitter is threatening to sue Meta over Threads [pdf]

#111

Earlier quoted context omitted.

[flagged]

> It also claims stolen secrets, codebases and digital assets. Wouldn't put it past The Zucc. You wouldn't put it past Zuck ? Friendly reminder to everyone that Tesla knowledgeably violated GPL for years until they were forced into compliance: https://www.theregister.com/2018/05/21/tesla_inches_toward_g... I don't trust for a second that Elon's team knows what they're talking about here.

Both Zuck and Musk are unreliable people who can't be taken at face value. I wouldn't put any level of shenanigans past either of them.

Re: Twitter is threatening to sue Meta over Threads [pdf]

#112

Isn't Threads just Instagram with optional text posts? Same old proprietary obfuscated mess, locked garden, meh, no thanks.

> locked garden Not to defend Meta, but this isn't true. Meta is embracing the fediverse protocol with Threads.

they claim they will, but haven’t, which probably means they won’t.

Re: Twitter is threatening to sue Meta over Threads [pdf]

#113

Great news for tech workers imo. Part of the tech labor market downturn has been driven by skepticism over the costs: if Twitter can slash its workforce and keep running just fine, why can’t other companies? Well, Threads swooping in to rapidly drain Twitter’s market share might change that reasoning.

Yeah, unfortunately Musk has done so much incompetent stuff that it's not as easy to make the case that the Twitter implosion is due to the staff reduction rather than one of the twenty other boneheaded things that have happened. The narrative could totally settle on: "The massive staff cuts would have worked out just fine if he hadn't also taken on too much debt in the financing and scared off advertisers with his own personal tweeting and gotten rid of verification and started promoting the replies of paying customers and turned off non-logged-in access and search engine visibility." Personally I think it is all of the above.

Re: Twitter is threatening to sue Meta over Threads [pdf]

#115

Maybe the facts will bear out that there’s a case here, but my default position is one of skepticism. I guess one takeaway for me is if you don’t want your competitor to hire a bunch of your former employees, don’t make a bunch of your employees former employees.

[flagged]

The likelihood of "stolen codebases and assets" is zero. Meta has an existing infrastructure that can handle 10x the traffic that Twitter has, and which is completely different than Twitter's stack.

As for the Threads app, that's a job any average web dev can have a rough prototype of in a day. The rest is iteration and refinement.

The entire mail is 100% BS. Also, there's no suit. There's a threat of a suit, which will likely not materialize as there's no chance of winning it.

Re: Twitter is threatening to sue Meta over Threads [pdf]

#116

Earlier quoted context omitted.

It's not really possible to say how many people are "working on" Threads, I bet. Threads is using Meta infrastructure. Should all those employees count towards Threads employees? How about HR? Legal? Internal tools? Building staff? Security? etc etc.

I'm not particularly interested in Twitter itself, I just disagree that many of the products we use today require a large number of developers. Its easy to find many examples of apps that were challenging to build even just 10 years ago, that are somewhat trivial now. That trend will only continue. OpenAI only had ~100 employees at one point. You don't need 100s of operations people if you move from on-prem to server…

I see it as four categories, from least employees to most:

1. Desperately trying to make short term cash, and are trying to do their best with fewer employees than needed to maintain the current product. (Twitter is here).

2. Enough staff to maintain the current product, but not significantly innovate.

3. Significantly more than needed to maintain the current product, leaving room for people to work on non-core products that may end up being the next billion dollar project, even if the vast majority flop (Most big tech companies are here).

4. Way too bloated, with not enough projects to work on or not enough revenue to justify the R&D.

The problem is that outsiders have a really really hard time understanding the product complexity of half a billion+ user services.

Comparing OpenAI to the social media sites that this HN post is talking about is a great example. It's a completely different product with completely different challenges than FB, twitter, threads, youtube, whatever.

Another great example is people citing "day in the life" videos that are actually recruiting videos showing the brighter sides of the job. Or people citing employees who claim that the company hired them to do nothing, when in reality it's a recruiter that was hired shortly before hiring slowed.

Re: Twitter is threatening to sue Meta over Threads [pdf]

#117
post #101

Earlier quoted context omitted.

Didn't Twitter open source a large portion of the code base? Seems like that isn't going to help their case.

I don't know the specifics, but the license included with that code will specify what can and can't be done with it. ~~Not all open source is free to use in your own code base. Sometimes it is open sourced for review purposes.~~ Edited: the last line is incorrect.

> Sometimes it is open sourced for review purposes.

Huh? I'm not aware that it's possible to open source something without, you know, making it OSS. Am I mistaken, or are we talking about two different meanings for "open source"?

Re: Twitter is threatening to sue Meta over Threads [pdf]

#118

Maybe the facts will bear out that there’s a case here, but my default position is one of skepticism. I guess one takeaway for me is if you don’t want your competitor to hire a bunch of your former employees, don’t make a bunch of your employees former employees.

Makes sense. However, I hope no one takes this the wrong way and hire too many people to starve competitors of talent.

Re: Twitter is threatening to sue Meta over Threads [pdf]

#119
post #90

Earlier quoted context omitted.

Doesn’t have to be a mistake. Twitter knows that people who used to work for Twitter now work for Meta. Seems perfectly fine to me.

The next sentence is “With that knowledge, Meta deliberately assigned these employees to develop, in a matter of months, Meta’s copycat Threads app.” This sentence doesn’t follow logically unless it was Meta who had the knowledge in the previous sentence.

I think it's supposed to be saying "With that knowledge, [we are claiming that] Meta deliberately assigned these employees to develop, in a matter of months, Meta’s copycat Threads app."

I wouldn't be surprised if Elon insisted on more aggressive language and it was hastily edited.

Re: Twitter is threatening to sue Meta over Threads [pdf]

#120
post #118

Maybe the facts will bear out that there’s a case here, but my default position is one of skepticism. I guess one takeaway for me is if you don’t want your competitor to hire a bunch of your former employees, don’t make a bunch of your employees former employees.

Makes sense. However, I hope no one takes this the wrong way and hire too many people to starve competitors of talent.

This idea floats around but is not practical. Here's a comment thread about it with some numbers: https://news.ycombinator.com/item?id=32413948
Post reply on HN