#threadsapi — Public Fediverse posts

Meta introduces new search and analytics features to Threads API platform: Meta enhances Threads API with advanced search capabilities and new metrics for developers to build improved integrations and tools. https://ppc.land/meta-introduces-new-search-and-analytics-features-to-threads-api-platform/?utm_source=dlvr.it&utm_medium=mastodon #Meta #ThreadsAPI #SearchFeatures #Analytics #Developers

Ahh finally after writing the library I get to play with the Threads API Library I wrote for F# and dotnet there's still rough edges but I'm able to fetch and post threads with it, I still need to play a bit more to figure out issues.
The project and the sample live here https://github.com/AngelMunoz/Threads.Lib
the sample is still quite dirty I haven't cleaned up anything yet so take a look with a grain of salt
#fsharp #dotnet #threads #threadsapi #avalonia #desktop #library

Playing a bit with my Threads API wrapper written in F# and the sample app with @[email protected]

Mostly I'm just testing that the requests are well encoded and are somewhat ergonomic to use, the Avalonia bits are just for fun!

Code over here

https://github.com/AngelMunoz/Threads.Lib

Particularly in the samples directory

#dotnet #fsharp #avaloniaui #desktop #threads #threadsapi #buildintheopen

Playing a bit with my Threads API wrapper written in F# and the sample app with @[email protected]

Mostly I'm just testing that the requests are well encoded and are somewhat ergonomic to use, the Avalonia bits are just for fun!

Code over here

https://github.com/AngelMunoz/Threads.Lib

Particularly in the samples directory

#dotnet #fsharp #avaloniaui #desktop #threads #threadsapi #buildintheopen

Playing a bit with my Threads API wrapper written in F# and the sample app with @[email protected]

Mostly I'm just testing that the requests are well encoded and are somewhat ergonomic to use, the Avalonia bits are just for fun!

Code over here

https://github.com/AngelMunoz/Threads.Lib

Particularly in the samples directory

#dotnet #fsharp #avaloniaui #desktop #threads #threadsapi #buildintheopen

Playing a bit with my Threads API wrapper written in F# and the sample app with @[email protected]

Mostly I'm just testing that the requests are well encoded and are somewhat ergonomic to use, the Avalonia bits are just for fun!

Code over here

https://github.com/AngelMunoz/Threads.Lib

Particularly in the samples directory

#dotnet #fsharp #avaloniaui #desktop #threads #threadsapi #buildintheopen

Playing a bit with my Threads API wrapper written in F# and the sample app with @[email protected]

Mostly I'm just testing that the requests are well encoded and are somewhat ergonomic to use, the Avalonia bits are just for fun!

Code over here

https://github.com/AngelMunoz/Threads.Lib

Particularly in the samples directory

#dotnet #fsharp #avaloniaui #desktop #threads #threadsapi #buildintheopen

🚀 Ready to bring your social media posts to the next level? Check out my latest blog on automating #Threads posts with #PowerAutomate!
Save time and let the Power Platform do the heavy lifting. 💪✨ #ProductivityHacks #SocialMediaAutomation #ThreadsAPI
https://www.menzel.it/post/2024/07/automating-threads-posts-power-automate/

🚀 Ready to bring your social media posts to the next level? Check out my latest blog on automating #Threads posts with #PowerAutomate!
Save time and let the Power Platform do the heavy lifting. 💪✨ #ProductivityHacks #SocialMediaAutomation #ThreadsAPI
https://www.menzel.it/post/2024/07/automating-threads-posts-power-automate/

Re-centring the Fediverse: how a footnote tells the bigger story

There is a potential of moving the #Fediverse towards long-form content, podcasts, forums, and curation, rather than just #microblogging. It highlights recent developments like the #Threads API launch and Mastodon's new fediverse:creator tag, suggesting a shift towards more in-depth, curated content.

#LongFormContent #Podcasts #Curation #SocialMedia #ThreadsAPI #Mastodon

https://www.blog-pat.ch/re-centring-the-fediverse/

@0xjessel

"the wait is over, threads API is finally here!"

Here: https://developers.facebook.com/docs/threads

Where we find:

"The Threads API enables businesses to create and publish content on a person’s behalf on Threads and to display those posts within an app solely to the person who created it."

Let's parse this:

"The Threads API enables businesses to create and publish content..."

"on a person’s behalf on Threads..."

"and to display those posts within an app... "

solely to the person who created it."

Businesses create content, publish to Threads on one person's behalf, and those post are only available to that one person through one app

Where does the app come from?

And who runs that app, on what platform?

So this API does *not* involve publishing content directly into the Threads stream for general consumption?

And why will my reply not propagate back over to your original post on #Threads, and why will you never see this reply on #Mastodon?

#ThreadsAPI #API #Meta #Facebook