Live data from Hacker News

Backend of Meta Threads is built with Python 3.10

twitter.com

51–60 of 458 posts

Re: Backend of Meta Threads is built with Python 3.10

#51

Earlier quoted context omitted.

It is on Mastodon as well, actually: https://mastodon.social/@ambv/110665808046065754

Could we get the mastodon link as the main link, please? Can actually view that one.

The tweet is currently viewable while logged out. Have you tried?

Re: Backend of Meta Threads is built with Python 3.10

#52
post #16

Ironic that a post about Threads backend is hosted on twitter.

Threads is a mobile-only app, like Instagram. You can't actually use Threads on a desktop browser, so that's probably why this is shared as a Twitter post. Even if it were a Threads post, it would not be submittable to HN.

Chill it's been in development for like 6 months and they wanted it to scale to 10M users. I'm sure a web interface is on the roadmap.

Re: Backend of Meta Threads is built with Python 3.10

#53

Earlier quoted context omitted.

A fair point that it's stupid to implement a mostly plain text publishing site that doesn't support linking to any of the text published there. Edit: Someone kindly pointed out that you can see the content in the browser without an account from following a direct link. (You just can't have the app installed or it will open that and drop you on the login page.) This makes me a lot happier with the product!

You can’t link to threads? By design? I was seriously considering trying it out, but if there’s no search engine visibility, there’s no point. Most of the searches for my real name pull up tweets. Hopefully it’s just a missing feature that will be added later. Even TikToks are linkable, and those have very little google visibility.

It seems like you can generate links, but they don't do anything for people who don't have the app (except direct you to install the app). I haven't fiddled with it to see if they've implemented something to make the content visible to search engines. (Which presumably would mean I could see it too with some effort.) But I haven't seen such a thing yet.

Edit: Someone kindly pointed out that you can see the content in the browser without an account from following a direct link. (You just can't have the app installed or it will open that and drop you on the login page.) This makes me a lot happier with the product!

Re: Backend of Meta Threads is built with Python 3.10

#54

Earlier quoted context omitted.

A fair point about what? Threads is out for less than a day, I have 8 followers there so far. I originally posted this information on Mastodon, actually: https://mastodon.social/@ambv/110665808046065754 However, I have a much larger following on Twitter, so it was the tweet that got picked up by someone here on HN. We'll see how this looks like in twelve months.

A fair point that it's stupid to implement a mostly plain text publishing site that doesn't support linking to any of the text published there. Edit: Someone kindly pointed out that you can see the content in the browser without an account from following a direct link. (You just can't have the app installed or it will open that and drop you on the login page.) This makes me a lot happier with the product!

You can link to it, what are you talking about? An example fetched from a verge article -> https://www.threads.net/t/CuVaOg1PgU4/

Re: Backend of Meta Threads is built with Python 3.10

#56

Earlier quoted context omitted.

> Threads is a mobile-only app, like Instagram Instagram can be used in a desktop browser just fine.

Let's imagine that I don't have an Instagram account because I don't. (I never really understood it because it just felt like a slightly differently flavored Facebook and I already had a Facebook account.) Up until this weekend, I could simply view a Twitter post regardless of whether I had an account. And while I've never been much of a Twitter user, I did find that useful as a lot of local news and weather type stu…

You can view single IG posts without an account.

Re: Backend of Meta Threads is built with Python 3.10

#57
post #16

Earlier quoted context omitted.

Threads is a mobile-only app, like Instagram. You can't actually use Threads on a desktop browser, so that's probably why this is shared as a Twitter post. Even if it were a Threads post, it would not be submittable to HN.

Not exactly true. They have a read-only browser view. In fact a Thread thread has already been on the front of HN. https://news.ycombinator.com/item?id=36609632

> Not exactly true.

Still, mostly true.. read-only is just dumb. Nice to be back in 2008, when mobile-first turned into mobile-only.

The entire point of this thread was that this is a Python/Django web app, but it's not actually a web app at all, so what's the point of pointing out any of this?

Re: Backend of Meta Threads is built with Python 3.10

#58
post #11
post #5

Always the same people that get their names in the news. I would say that the amount of tweaks that prop up Python is no cause for celebration.

Yet here it is ... powering a global scale app. Too weak for someones hobby project, strong enough for global scale.

Off-topic: it is not yet [global scale] because it is only available in US. Here in EU, I still get “not available in your country”.

Re: Backend of Meta Threads is built with Python 3.10

#59
post #16

Earlier quoted context omitted.

Threads is a mobile-only app, like Instagram. You can't actually use Threads on a desktop browser, so that's probably why this is shared as a Twitter post. Even if it were a Threads post, it would not be submittable to HN.

Chill it's been in development for like 6 months and they wanted it to scale to 10M users. I'm sure a web interface is on the roadmap.

Six months and it still doesn't have a basic and open web interface. Not impressive. Many apps, including HN, operate for years with only a web interface.

Re: Backend of Meta Threads is built with Python 3.10

#60
post #55

Really, all the performance intensive parts are in various c++ aggregator and recommendation type services. But the webserver is Django, yes.

Thanks for your comment. I'm really interested in this topic. How do you know the web server is Django? I searched but couldn't find this.

Why would they use Django? I did some small projects in it but I assumed it wasn't very fast and wouldn't be suitable for a big app like this. I would like to know the pros and cons. Why didn't they build up something in C++ or Rust? Won't python limit the speed of responses despite being build the hard stuff in compiled languages? Sorry for being so naive, I am an amateur.

Post reply on HN