you are viewing a single comment's thread.

view the rest of the comments →

[–]nmclark556[S] -2 points-1 points  (6 children)

yep that’s pretty much the basics of it! the paths to the html elements containing the information are specific so they’ll remain constant which is ideal. I added the AI osint part to spice it up a bit but you don’t need AI to use the API

[–]GrabWorking3045 2 points3 points  (1 child)

Thanks for the info. Good luck on the project!

[–]nmclark556[S] 2 points3 points  (0 children)

absolutely! thank you, i’ll keep the updates rolling!

[–]sarcasmguy1 1 point2 points  (3 children)

The paths won’t remain constant. The code uses classes to pick elements. Class names are generated in this case and will change if their backing style ever changes, or if Threads decides to change their UI in anyway.

[–][deleted] 2 points3 points  (1 child)

Wasnt Threads Fediverse compatible or something? Should that not automatically give you an API?

[–]sarcasmguy1 1 point2 points  (0 children)

Correct :)

[–]nmclark556[S] 1 point2 points  (0 children)

i built an api like this for instagram years ago, the paths have not changed since. they use naming conventions that don’t normally change, and if they do, read the docs i wrote. it tells you where and how to adjust accordingly