Awesome

TootSDK

TootSDK is a framework for Mastodon and the Fediverse, for iOS. It provides a toolkit for authorizing a user with an instance, and interacting with their posts.

TootSDK is a community developed SDK for Mastodon and the Fediverse. It is designed to work with all major servers (Mastodon, Pleroma, PixelFed etc).

You can use TootSDK to build a client for Apple operating systems, or Linux with Vapor.

Why make TootSDK?

When app developers build apps for Mastodon and the Fediverse, every developer ends up having to solve the same set of problems when it comes to the API and data model.

Konstantin and Dave decided to share this effort.

TootSDK is a shared Swift Package that any client app can be built on.

Key Principles ⚙️

• Async/Await based. All asynchronous functions are defined as Async ones that you can use with Async/Await code
• Internal consistency and standardization of model property names
• Standardization across all supported Fediverse APIs
• Platform agnostic (TootSDK shouldn't care if it's on iOS, macOS or Linux!)

Please don't hesitate to open an issue or create a PR for features you need 🙏

Quick start 🏁

It's easy to get started with TootSDK.

• Add TootSDK to your project via Swift Package Manager: https://github.com/TootSDK/TootSDK

• Instantiate with an instanceURL and accessToken:

  let instanceURL = URL(string: "social.yourinstance.com")
  let client = try await TootClient(connect: instanceURL, accessToken: "USERACCESSTOKEN")

Signing in (for macOS and iOS):

When using TootSDK within a macOS target you will need to enable the com.apple.security.network.client entitlement in your entitlements file or within the Signing & Capabilities tab in Xcode.

<key>com.apple.security.network.client</key>
<true/>

• Instantiate your client without a token:

let client = try await TootClient(connect: url)

• Use the sign in helper we've created based on ASWebAuthenticationSession:

let client = try await TootClient(connect: url)

guard let accessToken = try await client.presentSignIn(callbackURI: callbackURI) else {
    // handle failed sign in
    return
}

That's it 🎉!

We recommend keeping the accessToken somewhere secure, for example the Keychain.

Signing in (all platforms):

• Instantiate your client without a token:

let client = try await TootClient(connect: instanceURL)

• Retrieve an authorization URL to present to the user (so they can sign in)

let authURL = client.createAuthorizeURL(callbackURI: "myapp://someurl")

• Present the the authorization URL as a web page
• Let the user sign in, and wait for the callbackURI to be called
• When that callbackURI is called, give it back to the client to collect the token

let accessToken = client.collectToken(returnUrl: url, callbackURI: callbackURI)

We recommend keeping the accessToken somewhere secure, for example the Keychain.

Usage and key concepts

Once you have your client connected, you're going to want to use it. Our example apps and reference docs will help you get into the nitty gritty of it all, but some key concepts are highlighted here.

There are several different types of timeline in TootSDK that you can access, for example their home timeline, the local timeline of their instance, or the federated timeline. These are all enumerated in the Timeline enum.

You can retrieve the latest posts (up to 40 on Mastodon) with a call like so:

let items = try await client.getTimeline(.home)
let posts = items.result

TootSDK returns Posts, Accounts, Lists and DomainBblocks as PagedResult. In our code, items is a PagedResult struct. It contains a property called result which will be the type of data request (in this case an array of Post).

Some requests in TootSDK allow pagination in order to request more information. TootSDK can request a specific page using the PagedInfo struct and handles paginaged server responses using the PagedResult struct.

PagedInfo has the following properties:

• maxId (Return results older than ID)
• minId (Return results immediately newer than ID)
• sinceId (Return results newer than ID)

So for example, if we want all posts from the user's home timeline that are newer than post ID 100, we could write:

let items = try await client.getTimeline(.home, PagedInfo(minId: 100))
let posts = items.result

Paged requests also deliver a PagedInfo struct as a property of the PagedResult returned, which means you can use that for subsequent requests of the same type.

var pagedInfo: PagedInfo?
var posts: [Post] = []

func retrievePosts() async {
    let items = try await client.getTimeline(.home, pagedInfo)
    posts.append(contentsOf: items.result)
    self.pagedInfo = items.pagedInfo
}

TootSDK implements several facilities to make it easier to iterate over multiple pages using the hasPrevious, hasNext, previousPage and nextPage properties of PagedResult:

var pagedInfo: PagedInfo? = nil
var hasMore = true
let query = TootNotificationParams(types: [.mention])

while hasMore {
  let page = try await client.getNotifications(params: query, pagedInfo)
  for notification in page.result {
    print(notification.id)
  }
  hasMore = page.hasPrevious
  pagedInfo = page.previousPage
}

⚠️ Different fediverse servers handle pagination differently and so there is no guarantee that hasPrevious or hasNext can correctly interpret the server response in all cases.

You can learn more about how pagination works for Fediverse servers using a Mastodon compatible API here.

In TootSDK it is possible to subscribe to some types of content with AsyncSequences, a concept we've wrapped up in our TootStream object.

for posts in try await client.data.stream(.home) {
    print(posts)
}

Underneath the hood, this uses our Paging mechanism. This means that when you ask the client to refresh that stream, it will deliver you new results, from after the ones you requested.

client.data.refresh(.home)

You can also pass an initial PagedInfo value to the stream call. For example, to start steaming all posts from the user's home timeline that are newer than post ID 100:

for posts in try await client.data.stream(.home, PagedInfo(minId: 100) {

Some timelines require associated query parameters to configure. Luckily these are associated values that their timeline enumeration require when creating - so you can't miss them!

for posts in try await client.data.stream(HashtagTimelineQuery(tag: "iOSDev") {
    print(posts)
}

• Register the app with the following scopes ["read", "write:accounts"].

• Get instance information and determine the sign up requirements. Some instances may not be open for registration while others may require additional verification.

let instance = try await client.getInstance()
if instance.registrations == false {
  // instance not open for registration
  return
}
// ...

• Use the registerAccount method to create a user account:

let params = RegisterAccountParams(
      username: name, email: email, password: password, agreement: true, locale: "en")
let token = try await client.registerAccount(params: params)

Further Documentation 📖

• Reference documentation is available here
• Example apps:
  • swiftui-toot - a SwiftUI app that shows authorization, a user's feed, posting and account operations
  • swiftyadmin - a command line utility to interact with and control a server using TootSDK
  • vaportoot - a web app in Vapor, that shows how to sign in and view a user's feed

Contributing

Code of Conduct and Contributing rules 🧑‍⚖️

• Our guide to contributing is available here: CONTRIBUTING.md.
• All contributions, pull requests, and issues are expected to adhere to our community code of conduct: CODE_OF_CONDUCT.md.

License 📃

TootSDK is licensed with the BSD-3-Clause license, more information here: LICENSE.MD

This is a permissive license which allows for any type of use, provided the copyright notice is included.

Acknowledgements 🙏

• The Mastodon API documentation https://github.com/mastodon/documentation
• We hat-tip top Metatext's source for some guidance on what's where: https://github.com/metabolist/metatext
• Kris Slazinski for our TootSDK logo 🤩

Built with TootSDK

• Fedicat
• Pipilo
• TootyGraph
• Topiary
• TootLater
• Oxpecker