freelawproject / foresight

Where we discuss and prioritize new features
2 stars 1 forks source link

Add Threads support to the bots #13

Open mlissner opened 7 months ago

mlissner commented 7 months ago

They still don't have an API, but when they do we should get on top of it. Their developers occasionally mention that they're working on an API and I've requested beta access, but they've ignored me.

TheCleric commented 6 months ago

They seem to have released a beta API and documentation: https://developers.facebook.com/docs/threads/

Downside is it seems to be geared more around "I have an app that will post things on behalf of users" and not "I am a user that wants to automate my posts." It definitely looks doable, but there would be extra hoops to jump through (register as an Instagram app, etc.).

mlissner commented 6 months ago

Sounds like Twitter. About time they launch the API. Anything you have to do to join it?

mlissner commented 6 months ago

Looks like there's a sign up on the blog post, so I did it.

mlissner commented 2 months ago

I mentioned to https://github.com/freelawproject/crm/issues/87 that we'd probably do this soon.

TheCleric commented 2 months ago

I can't see that issue, but could be available to help out since it's an area of the bot I'm pretty familiar with now.

mlissner commented 2 months ago

Sorry, yeah, that issue is to our internal CRM, I just wanted these to be cross-linked.

It'd be great if you wanted to take a stab at this!

TheCleric commented 2 months ago

@mlissner do we have some threads credentials to use for testing/development?

mlissner commented 2 months ago

Actually, no, not yet. Do you think you could make a tasting account?

TheCleric commented 2 months ago

Sure let me give that a try.

elisa-a-v commented 2 weeks ago

To do:

mlissner commented 2 weeks ago

Great. We could use S3 for this or if the images are only there for a few seconds or whatever, another idea could be for bots.law to host them temporarily. I wonder if there's a way to just push something into CloudFront so it'd be cached, and then delete it from our servers. Might be tricky, I guess.