Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Silo: Threads #1507

Open
vandie opened this issue Jul 7, 2023 · 13 comments
Open

New Silo: Threads #1507

vandie opened this issue Jul 7, 2023 · 13 comments
Labels

Comments

@vandie
Copy link

vandie commented Jul 7, 2023

Given how quickly Threads.net has gained users, I feel like this is probably a good call to file. They seem to be using the same protocol as mastodon under the hood so hopefully that should make this easier but there's no official API yet as far as I can see.

@snarfed
Copy link
Owner

snarfed commented Jul 7, 2023

Yes! Absolutely, thanks for filing.

They're using Meta's internal infrastructure under the hood as far as we know. AP is more about how servers communicate between each other, and they sound at least a quarter or two away from shipping that federation. I'm looking forward to testing interop with Bridgy Fed when they do.

Regardless, if/when they have a traditional API, Bridgy classic support for POSSE and backfeed would be good too!

@snarfed snarfed changed the title New Silo: Threads.net New Silo: Threads.net [blocked on API] Jul 7, 2023
@spcbfr
Copy link

spcbfr commented Jul 9, 2023

@vandie since they'll be adding activityPub support soon, maybe we'll get a threads support for free?

@snarfed
Copy link
Owner

snarfed commented Jul 9, 2023

In Bridgy Fed, yes! Not here in Bridgy classic though.

@vandie
Copy link
Author

vandie commented Jul 9, 2023

While obviously an official API is preferred, the unofficial API has been reverse engineered already.

https://github.com/junhoyeo/threads-py

@snarfed
Copy link
Owner

snarfed commented Jul 9, 2023

Also, given the current state of Facebook's and Instagram's APIs - ie, woefully inadequate for Bridgy - I don't know if we have much reason to expect much more from an official Threads API. cc @tantek @Timothyjchambers (others?)

@snarfed
Copy link
Owner

snarfed commented Nov 2, 2023

@JoelOtter
Copy link
Contributor

They’re asking for feedback here https://www.threads.net/@0xjessel/post/CzJoc1GRQpC

@markcellus
Copy link

Do you have a cool idea for how you would use an API to produce content on Threads? Comment below with your idea and if it’s a good fit, we will reach out via IG DM or here.

What an odd thing to ask. Dont see why they need this sort of feedback other than to try to gatekeep how people use the API.

The internet has been and always should be free and open and public content shouldn't be restricted to a single platform. That alone should be all the feedback they need to just do this.

@snarfed snarfed changed the title New Silo: Threads.net [blocked on API] New Silo: Threads [blocked on API] Mar 1, 2024
@snarfed
Copy link
Owner

snarfed commented Mar 1, 2024

ETA sounds like June: https://techcrunch.com/2024/03/01/threads-says-it-will-make-its-api-broadly-available-by-june/

@vandie
Copy link
Author

vandie commented Apr 9, 2024

Can't wait. I ended up signing up for bluesky in the meantime while I wait but I just use threads so much more.

@snarfed
Copy link
Owner

snarfed commented Apr 9, 2024

Ok!

I don't personally use Threads much, so I doubt I'll prioritize building this myself, but I'd love to have someone else jump in and contribute! We've had a good track record of contributors adding silos here over the last few years, notably Reddit and Bluesky.

@snarfed
Copy link
Owner

snarfed commented Jun 18, 2024

Threads API is finally out!

@snarfed snarfed changed the title New Silo: Threads [blocked on API] New Silo: Threads Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants