How meta built the infrastructure for Threads • Hacker News Board

Re: How meta built the infrastructure for Threads

#81

Post by edgyquant » Mon, Jan 08, 2024, 4:32 PM UTC

threeseed wrote: post #28

wayfinder wrote: post #20

Earlier quoted context omitted.

Instagram has like 2 billion users and I got spammed the shit out of to open a Threads account. That’s like saying it’s impressive I made a million dollar company after my dad gave me 2 billion.

Threads reached 100M users well before they turned on Instagram promotions. And now they have reached 100M MAU which shows that people are coming and staying.

I don’t about instagram, but it was all over the internet. It was Bloomberg and the economist as a twitter killer and was definitely on the front page here as well. It was advertised as only needing an instagram account and as an extension of that

Re: How meta built the infrastructure for Threads

#82

Post by edgyquant » Mon, Jan 08, 2024, 4:34 PM UTC

o10449366 wrote: post #18

[flagged]

You mean after their stock tanked last year? FYI it’s still not back to where it was in August 2021, though it’s finally getting close to that.

Re: How meta built the infrastructure for Threads

#83

Post by itslennysfault » Mon, Jan 08, 2024, 4:38 PM UTC

I'm kinda loving the obvious "X" shills in the comments coming just to declare Threads dead. It is literally the 2nd most downloaded app in the AppStore (was #1 for a bit, but Temu is seemingly unstoppable).

Personally, it has become my preferred social media platform. It's overflowing with content and I check in on it several times a day, and have been really enjoying the community that is emerging.

It DOES however have a big porn bot problem, but I don't think that is unique to Threads. Hopefully, they can come up with a way to minimize it soon.

Re: How meta built the infrastructure for Threads

#84

Post by cdelsolar » Mon, Jan 08, 2024, 4:39 PM UTC

itslennysfault wrote: post #83

I'm kinda loving the obvious "X" shills in the comments coming just to declare Threads dead. It is literally the 2nd most downloaded app in the AppStore (was #1 for a bit, but Temu is seemingly unstoppable). Personally, it has become my preferred social media platform. It's overflowing with content and I check in on it several times a day, and have been really enjoying the community that is emerging. It DOES however…

I kinda stopped using Threads and then they started putting controversial posts on it all over my Facebook feed. Pretty clever. Now I check it often again

Re: How meta built the infrastructure for Threads

#85

Post by lapcat » Mon, Jan 08, 2024, 4:39 PM UTC

Nextgrid wrote: post #80

lapcat wrote: post #77

Earlier quoted context omitted.

You are blaming the victim: > there's something about your software stack and/or behavior that makes you "naughty" in the eyes of Facebook. https://news.ycombinator.com/item?id=38913992 In any case, your assumptions come with zero empirical evidence. It's just wild speculation, grasping at straws, looking for a "good reason" for Instagram to charge me with a completely unwarranted ToS violation. We all know that is a…

I'm just explaining the truth. I'm not saying it should be considered OK - we should absolutely look down on the behavior and look for solutions to discourage it. Obviously without looking at the code behind it I can only speculate, but I think my speculation agrees pretty well with their business model and why they might choose to ban people whose analytics data (or lack thereof) matches yours. In fact, it's indeed…

> I'm just explaining the truth.

> Obviously without looking at the code behind it I can only speculate

It's funny how you can say these two contradictory things right next to each other.

> the concept of "bullshit ban -> provide personal info for security -> automatic unban" procedure is routine nowadays, pioneered by Twitter.

I already said this in my original comment: "Twitter used to auto-ban me too in order to extract my phone number, and we know that Twitter illegitimately used phone numbers for advertising purposes." So there's no need to speculate about my "software stack and/or behavior" that somehow makes me "naughty". The only naughty one is Meta itself, attempting to extract my personal information.

Re: How meta built the infrastructure for Threads

#86

Post by r14c » Mon, Jan 08, 2024, 4:45 PM UTC

verdverm wrote: post #14

DeathArrow wrote: post #4

What is Threads?

It's ActivityPub based, Twitter like, social media from Meta It's been pretty chill over there, lacks the crazy that is Twitter For me, it opens the potential for a federated social media protocol. Having a big player like Meta means everyone will likely benefit. Federated means we can move between servers without losing the network, allowing for competition in moderation, algorithms, and monetization

I'm not sure this tracks. "having a big player like Walmart in town means everyone will likely benefit" sounds plausible, but in practice they suck all the oxygen out of the room, play dirty, and make it difficult for small operators to "compete" once they gain the advantage. The fediverse is honestly not prepared for this scenario, but I do hope that the communities will rally and give Meta a run for their money. I don't have any ill will against them, but its boring to see the same few entities doing everything. Despite its flaws, portions of the fediverse are vibrant and I really want to see them trive.

Re: How meta built the infrastructure for Threads

#87

Post by Nextgrid » Mon, Jan 08, 2024, 4:46 PM UTC

lapcat wrote: post #85

Nextgrid wrote: post #80

Earlier quoted context omitted.

I'm just explaining the truth. I'm not saying it should be considered OK - we should absolutely look down on the behavior and look for solutions to discourage it. Obviously without looking at the code behind it I can only speculate, but I think my speculation agrees pretty well with their business model and why they might choose to ban people whose analytics data (or lack thereof) matches yours. In fact, it's indeed…

> I'm just explaining the truth. > Obviously without looking at the code behind it I can only speculate It's funny how you can say these two contradictory things right next to each other. > the concept of "bullshit ban -> provide personal info for security -> automatic unban" procedure is routine nowadays, pioneered by Twitter. I already said this in my original comment: "Twitter used to auto-ban me too in order to e…

> It's funny how you can say these two contradictory things right next to each other.

Fair enough, we'll agree to disagree on that one. I will happily eat crow if it turns out not to be the truth should there be an eventual source code/internal email leak. Keep in mind that a lot of leaks have already confirmed tech company malicious behaviors that was endlessly speculated on in the past and that it felt too blatant to be true and yet ended up true.

> my "software stack and/or behavior" that somehow makes me "naughty"

Not everyone gets these bans though. If your software stack or behavior allowed them to correlate you with the existing shadow profile they have on you they'll most likely let you pass and not need to bullshit-ban you since they already got your data.

> The only naughty one is Meta itself

Oh yeah absolutely - I always meant naughty in the eyes of Facebook, which is true. In fact you are the opposite of naughty - getting one of these bullshit bans actually suggests your online behavior is on point since Facebook couldn't just infer your personal data from tracking and instead has to force you to provide it.

Re: How meta built the infrastructure for Threads

#88

Post by erulabs » Mon, Jan 08, 2024, 4:51 PM UTC

Gotta love how far MySQL + k/v store can get ya. I have no experience with zippyDB, but MySQL and ScyllaDB certainly feels like having an M1 Abrams and a B2 Spirit in my back pocket. I’m constantly pushing the “relationships from MySQL, data from Cassandra” narrative. It sounds like Facebook has a similar approach - although this post doesn’t make it clear where message data actually resides.

MySQL, ScyllaDB, and RabbitMQ. A stack made in pragmatist heaven by devops angels. Now to find some developers who don’t hate it ;)

Re: How meta built the infrastructure for Threads

#89

Post by laweijfmvo » Mon, Jan 08, 2024, 4:53 PM UTC

(This is performance evaluation week at Meta)

I can only dream of being able to cite an article like this on my impacc...

Re: How meta built the infrastructure for Threads

#90

Post by neon_electro » Mon, Jan 08, 2024, 5:01 PM UTC

erulabs wrote: post #88

Gotta love how far MySQL + k/v store can get ya. I have no experience with zippyDB, but MySQL and ScyllaDB certainly feels like having an M1 Abrams and a B2 Spirit in my back pocket. I’m constantly pushing the “relationships from MySQL, data from Cassandra” narrative. It sounds like Facebook has a similar approach - although this post doesn’t make it clear where message data actually resides. MySQL, ScyllaDB, and Rab…

Can you share your take on why MySQL and not Postgres?