home.social

#mastodonapi — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #mastodonapi, aggregated by home.social.

  1. Today I unfollowed about 120 accounts that hadn't posted in more than ~8 months.

    It's a bummer to see so many gone and I hope they return, but my feed has been more active than ever. Plus, I'll likely be more liberal in following new folks for a while.

    What do ya'll do for user management? I cobbled together some JS for the MastoAPI to sort out the >8mo old accounts. I really didn't find any existing apps / repos for that type of thing.

    #mastodon #fediverse #userManagement #mastodonAPI

  2. @silverpill @Connected Places The problem with the Mastodon client API is still that it's a Mastodon API. As in, geared towards only one Fediverse server application. In fact, as in, geared towards a very lack-lustre server application that lacks features which have been present in many other places in the Fediverse for years.

    This means that you can use a whole lot of microblogging server applications with Mastodon clients. You can even use Friendica with some Mastodon clients. But then you're limited to the features which Mastodon has as well because the Mastodon client API doesn't support any features that Mastodon doesn't have. Why should it, after all?

    At the end of the day, the Mastodon client API is designed and maintained by the Mastodon developers. It's them who decide what it can do and what it can't do. For one, they won't waste their time adding features to it that Mastodon itself doesn't have. Besides, if they did, they'd support Mastodon's direct competition and strengthen their advantages over Mastodon when they could throw rocks into their paths instead like they've always done.

    This, by the way, is also one reason why both the developers of Hubzilla and the developer of (streams) and Forte refuse to implement the Mastodon client API. It simply wouldn't cover at least 90% of the features of these server applications, including features which you'll need all the time, everyday. That, and they don't want their software to end up at the mercy of Mastodon's developers and Mastodon's product politics by making it depend on Mastodon's technology. They'd rather have no native mobile app at all (and currently they do).

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #Streams #(streams) #Forte #MastodonAPI #MastodonClientAPI
  3. 🆕 blog! “Adding "Log In With Mastodon" to Auth0”

    I use Auth0 to provide social logins for the OpenBenches website. I don't want to deal with creating user accounts, managing passwords, or anything like that, so Auth0 is perfect for my needs.

    There are a wide range of social media logins provided by Auth0 - including the usual suspects like…

    👀 Read more: shkspr.mobi/blog/2026/03/addin

    #Auth0 #HowTo #mastodon #MastodonAPI #SocialMedia

  4. 🆕 blog! “Adding "Log In With Mastodon" to Auth0”

    I use Auth0 to provide social logins for the OpenBenches website. I don't want to deal with creating user accounts, managing passwords, or anything like that, so Auth0 is perfect for my needs.

    There are a wide range of social media logins provided by Auth0 - including the usual suspects like…

    👀 Read more: shkspr.mobi/blog/2026/03/addin

    #Auth0 #HowTo #mastodon #MastodonAPI #SocialMedia

  5. 🆕 blog! “Adding "Log In With Mastodon" to Auth0”

    I use Auth0 to provide social logins for the OpenBenches website. I don't want to deal with creating user accounts, managing passwords, or anything like that, so Auth0 is perfect for my needs.

    There are a wide range of social media logins provided by Auth0 - including the usual suspects like…

    👀 Read more: shkspr.mobi/blog/2026/03/addin

    #Auth0 #HowTo #mastodon #MastodonAPI #SocialMedia

  6. 🆕 blog! “Adding "Log In With Mastodon" to Auth0”

    I use Auth0 to provide social logins for the OpenBenches website. I don't want to deal with creating user accounts, managing passwords, or anything like that, so Auth0 is perfect for my needs.

    There are a wide range of social media logins provided by Auth0 - including the usual suspects like…

    👀 Read more: shkspr.mobi/blog/2026/03/addin

    #Auth0 #HowTo #mastodon #MastodonAPI #SocialMedia

  7. 🆕 blog! “Adding "Log In With Mastodon" to Auth0”

    I use Auth0 to provide social logins for the OpenBenches website. I don't want to deal with creating user accounts, managing passwords, or anything like that, so Auth0 is perfect for my needs.

    There are a wide range of social media logins provided by Auth0 - including the usual suspects like…

    👀 Read more: shkspr.mobi/blog/2026/03/addin

    #Auth0 #HowTo #mastodon #MastodonAPI #SocialMedia

  8. Adding "Log In With Mastodon" to Auth0

    shkspr.mobi/blog/2026/03/addin

    I use Auth0 to provide social logins for the OpenBenches website. I don't want to deal with creating user accounts, managing passwords, or anything like that, so Auth0 is perfect for my needs.

    There are a wide range of social media logins provided by Auth0 - including the usual suspects like Facebook, Twitter, WordPress, Discord, etc. Sadly, there's no support for Mastodon0.

    All is not lost though. The Auth0 documentation says:

    However, you can use Auth0’s Connections API to add any OAuth2 Authorization Server as an identity provider.

    You can manually add a single Mastodon instance, but that doesn't work with the decentralised nature of the Fediverse. Instead, I've come up with a manual solution which works with any Mastodon server!

    Background

    Every Mastodon1 server is independent. I have an account on mastodon.social you have an account on whatever.chaos. They are separate servers, albeit running similar software. A generic authenticator needs to work with all these servers. There's no point only allowing log ins from a single server.

    Fortuitously, Mastodon allows app developers to automatically create new apps. A few simple lines of code and you will have an API key suitable for read-only access to that server. You can read how to instantly create Mastodon API keys or you can steal my PHP code.

    User Experience

    The user clicks the sign-in button on OpenBenches. They're taken to the Auth0 social login screen:

    The user clicks on Mastodon. This is where Auth0's involvement ends!

    The user is asked to provide the URl of their instance:

    In the background, my server contacts the Mastodon instance and creates a read-only API key.

    The user is asked to sign in to Mastodon.

    The user is asked to authorise read-only access.

    The user is now signed in and OpenBenches can retrieve their name, avatar image, and other useful information. Hurrah!

    Auth0

    Once you have created a service to generate API keys, it will need to run on a publicly accessible web server. For example https://example.com/mastodon_login.

    Here's what you need to do within your Auth0 tennant:

    • Authentication → Social → Create Connection
    • At the bottom, choose "Create Custom".
    • Choose "Authentication" only.
    • Give your connection a name. This will be visible to users.
    • "Authorization URL" and "Token URL" have the same value - the URl of your service.
    • "Client ID" is only visible to you.
    • "Client Secret" any random password; it won't be used for anything.
    • Leave everything else in the default state.

    It should look something like this:

    Click the "Create" button and you're (almost) done.

    Auth0 Icon

    You will need to add a custom icon to the social integration. Annoyingly, there's no way to do it through the web interface, so follow that guide to use the command line.

    Done!

    I'll admit, this isn't the most straightforward thing to implement. Auth0 could make this easier - but it would still rely on users knowing the URl of their home instance.

    That said, the Mastodon API is a delight to work with and the read-only permissions reduce risk for all parties.

    1. Auth0 did blog about Mastodon a few years ago but never bothered implementing it! ↩︎

    2. I do mean Mastodon; not the wider Fediverse. This only works with sites which have implemented Mastodon's APIs. ↩︎

    #Auth0 #HowTo #mastodon #MastodonAPI #SocialMedia
  9. Adding "Log In With Mastodon" to Auth0

    shkspr.mobi/blog/2026/03/addin

    I use Auth0 to provide social logins for the OpenBenches website. I don't want to deal with creating user accounts, managing passwords, or anything like that, so Auth0 is perfect for my needs.

    There are a wide range of social media logins provided by Auth0 - including the usual suspects like Facebook, Twitter, WordPress, Discord, etc. Sadly, there's no support for Mastodon0.

    All is not lost though. The Auth0 documentation says:

    However, you can use Auth0’s Connections API to add any OAuth2 Authorization Server as an identity provider.

    You can manually add a single Mastodon instance, but that doesn't work with the decentralised nature of the Fediverse. Instead, I've come up with a manual solution which works with any Mastodon server!

    Background

    Every Mastodon1 server is independent. I have an account on mastodon.social you have an account on whatever.chaos. They are separate servers, albeit running similar software. A generic authenticator needs to work with all these servers. There's no point only allowing log ins from a single server.

    Fortuitously, Mastodon allows app developers to automatically create new apps. A few simple lines of code and you will have an API key suitable for read-only access to that server. You can read how to instantly create Mastodon API keys or you can steal my PHP code.

    User Experience

    The user clicks the sign-in button on OpenBenches. They're taken to the Auth0 social login screen:

    The user clicks on Mastodon. This is where Auth0's involvement ends!

    The user is asked to provide the URl of their instance:

    In the background, my server contacts the Mastodon instance and creates a read-only API key.

    The user is asked to sign in to Mastodon.

    The user is asked to authorise read-only access.

    The user is now signed in and OpenBenches can retrieve their name, avatar image, and other useful information. Hurrah!

    Auth0

    Once you have created a service to generate API keys, it will need to run on a publicly accessible web server. For example https://example.com/mastodon_login.

    Here's what you need to do within your Auth0 tennant:

    • Authentication → Social → Create Connection
    • At the bottom, choose "Create Custom".
    • Choose "Authentication" only.
    • Give your connection a name. This will be visible to users.
    • "Authorization URL" and "Token URL" have the same value - the URl of your service.
    • "Client ID" is only visible to you.
    • "Client Secret" any random password; it won't be used for anything.
    • Leave everything else in the default state.

    It should look something like this:

    Click the "Create" button and you're (almost) done.

    Auth0 Icon

    You will need to add a custom icon to the social integration. Annoyingly, there's no way to do it through the web interface, so follow that guide to use the command line.

    Done!

    I'll admit, this isn't the most straightforward thing to implement. Auth0 could make this easier - but it would still rely on users knowing the URl of their home instance.

    That said, the Mastodon API is a delight to work with and the read-only permissions reduce risk for all parties.

    1. Auth0 did blog about Mastodon a few years ago but never bothered implementing it! ↩︎

    2. I do mean Mastodon; not the wider Fediverse. This only works with sites which have implemented Mastodon's APIs. ↩︎

    #Auth0 #HowTo #mastodon #MastodonAPI #SocialMedia
  10. Adding "Log In With Mastodon" to Auth0

    shkspr.mobi/blog/2026/03/addin

    I use Auth0 to provide social logins for the OpenBenches website. I don't want to deal with creating user accounts, managing passwords, or anything like that, so Auth0 is perfect for my needs.

    There are a wide range of social media logins provided by Auth0 - including the usual suspects like Facebook, Twitter, WordPress, Discord, etc. Sadly, there's no support for Mastodon0.

    All is not lost though. The Auth0 documentation says:

    However, you can use Auth0’s Connections API to add any OAuth2 Authorization Server as an identity provider.

    You can manually add a single Mastodon instance, but that doesn't work with the decentralised nature of the Fediverse. Instead, I've come up with a manual solution which works with any Mastodon server!

    Background

    Every Mastodon1 server is independent. I have an account on mastodon.social you have an account on whatever.chaos. They are separate servers, albeit running similar software. A generic authenticator needs to work with all these servers. There's no point only allowing log ins from a single server.

    Fortuitously, Mastodon allows app developers to automatically create new apps. A few simple lines of code and you will have an API key suitable for read-only access to that server. You can read how to instantly create Mastodon API keys or you can steal my PHP code.

    User Experience

    The user clicks the sign-in button on OpenBenches. They're taken to the Auth0 social login screen:

    The user clicks on Mastodon. This is where Auth0's involvement ends!

    The user is asked to provide the URl of their instance:

    In the background, my server contacts the Mastodon instance and creates a read-only API key.

    The user is asked to sign in to Mastodon.

    The user is asked to authorise read-only access.

    The user is now signed in and OpenBenches can retrieve their name, avatar image, and other useful information. Hurrah!

    Auth0

    Once you have created a service to generate API keys, it will need to run on a publicly accessible web server. For example https://example.com/mastodon_login.

    Here's what you need to do within your Auth0 tennant:

    • Authentication → Social → Create Connection
    • At the bottom, choose "Create Custom".
    • Choose "Authentication" only.
    • Give your connection a name. This will be visible to users.
    • "Authorization URL" and "Token URL" have the same value - the URl of your service.
    • "Client ID" is only visible to you.
    • "Client Secret" any random password; it won't be used for anything.
    • Leave everything else in the default state.

    It should look something like this:

    Click the "Create" button and you're (almost) done.

    Auth0 Icon

    You will need to add a custom icon to the social integration. Annoyingly, there's no way to do it through the web interface, so follow that guide to use the command line.

    Done!

    I'll admit, this isn't the most straightforward thing to implement. Auth0 could make this easier - but it would still rely on users knowing the URl of their home instance.

    That said, the Mastodon API is a delight to work with and the read-only permissions reduce risk for all parties.

    1. Auth0 did blog about Mastodon a few years ago but never bothered implementing it! ↩︎

    2. I do mean Mastodon; not the wider Fediverse. This only works with sites which have implemented Mastodon's APIs. ↩︎

    #Auth0 #HowTo #mastodon #MastodonAPI #SocialMedia
  11. Adding "Log In With Mastodon" to Auth0

    shkspr.mobi/blog/2026/03/addin

    I use Auth0 to provide social logins for the OpenBenches website. I don't want to deal with creating user accounts, managing passwords, or anything like that, so Auth0 is perfect for my needs.

    There are a wide range of social media logins provided by Auth0 - including the usual suspects like Facebook, Twitter, WordPress, Discord, etc. Sadly, there's no support for Mastodon0.

    All is not lost though. The Auth0 documentation says:

    However, you can use Auth0’s Connections API to add any OAuth2 Authorization Server as an identity provider.

    You can manually add a single Mastodon instance, but that doesn't work with the decentralised nature of the Fediverse. Instead, I've come up with a manual solution which works with any Mastodon server!

    Background

    Every Mastodon1 server is independent. I have an account on mastodon.social you have an account on whatever.chaos. They are separate servers, albeit running similar software. A generic authenticator needs to work with all these servers. There's no point only allowing log ins from a single server.

    Fortuitously, Mastodon allows app developers to automatically create new apps. A few simple lines of code and you will have an API key suitable for read-only access to that server. You can read how to instantly create Mastodon API keys or you can steal my PHP code.

    User Experience

    The user clicks the sign-in button on OpenBenches. They're taken to the Auth0 social login screen:

    The user clicks on Mastodon. This is where Auth0's involvement ends!

    The user is asked to provide the URl of their instance:

    In the background, my server contacts the Mastodon instance and creates a read-only API key.

    The user is asked to sign in to Mastodon.

    The user is asked to authorise read-only access.

    The user is now signed in and OpenBenches can retrieve their name, avatar image, and other useful information. Hurrah!

    Auth0

    Once you have created a service to generate API keys, it will need to run on a publicly accessible web server. For example https://example.com/mastodon_login.

    Here's what you need to do within your Auth0 tennant:

    • Authentication → Social → Create Connection
    • At the bottom, choose "Create Custom".
    • Choose "Authentication" only.
    • Give your connection a name. This will be visible to users.
    • "Authorization URL" and "Token URL" have the same value - the URl of your service.
    • "Client ID" is only visible to you.
    • "Client Secret" any random password; it won't be used for anything.
    • Leave everything else in the default state.

    It should look something like this:

    Click the "Create" button and you're (almost) done.

    Auth0 Icon

    You will need to add a custom icon to the social integration. Annoyingly, there's no way to do it through the web interface, so follow that guide to use the command line.

    Done!

    I'll admit, this isn't the most straightforward thing to implement. Auth0 could make this easier - but it would still rely on users knowing the URl of their home instance.

    That said, the Mastodon API is a delight to work with and the read-only permissions reduce risk for all parties.

    1. Auth0 did blog about Mastodon a few years ago but never bothered implementing it! ↩︎

    2. I do mean Mastodon; not the wider Fediverse. This only works with sites which have implemented Mastodon's APIs. ↩︎

    #Auth0 #HowTo #mastodon #MastodonAPI #SocialMedia
  12. Adding "Log In With Mastodon" to Auth0

    shkspr.mobi/blog/2026/03/addin

    I use Auth0 to provide social logins for the OpenBenches website. I don't want to deal with creating user accounts, managing passwords, or anything like that, so Auth0 is perfect for my needs.

    There are a wide range of social media logins provided by Auth0 - including the usual suspects like Facebook, Twitter, WordPress, Discord, etc. Sadly, there's no support for Mastodon0.

    All is not lost though. The Auth0 documentation says:

    However, you can use Auth0’s Connections API to add any OAuth2 Authorization Server as an identity provider.

    You can manually add a single Mastodon instance, but that doesn't work with the decentralised nature of the Fediverse. Instead, I've come up with a manual solution which works with any Mastodon server!

    Background

    Every Mastodon1 server is independent. I have an account on mastodon.social you have an account on whatever.chaos. They are separate servers, albeit running similar software. A generic authenticator needs to work with all these servers. There's no point only allowing log ins from a single server.

    Fortuitously, Mastodon allows app developers to automatically create new apps. A few simple lines of code and you will have an API key suitable for read-only access to that server. You can read how to instantly create Mastodon API keys or you can steal my PHP code.

    User Experience

    The user clicks the sign-in button on OpenBenches. They're taken to the Auth0 social login screen:

    The user clicks on Mastodon. This is where Auth0's involvement ends!

    The user is asked to provide the URl of their instance:

    In the background, my server contacts the Mastodon instance and creates a read-only API key.

    The user is asked to sign in to Mastodon.

    The user is asked to authorise read-only access.

    The user is now signed in and OpenBenches can retrieve their name, avatar image, and other useful information. Hurrah!

    Auth0

    Once you have created a service to generate API keys, it will need to run on a publicly accessible web server. For example https://example.com/mastodon_login.

    Here's what you need to do within your Auth0 tennant:

    • Authentication → Social → Create Connection
    • At the bottom, choose "Create Custom".
    • Choose "Authentication" only.
    • Give your connection a name. This will be visible to users.
    • "Authorization URL" and "Token URL" have the same value - the URl of your service.
    • "Client ID" is only visible to you.
    • "Client Secret" any random password; it won't be used for anything.
    • Leave everything else in the default state.

    It should look something like this:

    Click the "Create" button and you're (almost) done.

    Auth0 Icon

    You will need to add a custom icon to the social integration. Annoyingly, there's no way to do it through the web interface, so follow that guide to use the command line.

    Done!

    I'll admit, this isn't the most straightforward thing to implement. Auth0 could make this easier - but it would still rely on users knowing the URl of their home instance.

    That said, the Mastodon API is a delight to work with and the read-only permissions reduce risk for all parties.

    1. Auth0 did blog about Mastodon a few years ago but never bothered implementing it! ↩︎

    2. I do mean Mastodon; not the wider Fediverse. This only works with sites which have implemented Mastodon's APIs. ↩︎

    #Auth0 #HowTo #mastodon #MastodonAPI #SocialMedia
  13. I started refactoring @meow to use ID objects for resources encoding the string ID, the resource type (account/status), and server the resource is from together.

    The idea being that a status URL could be parsed from text into an ID and the status details page knows if it's a local status or remote status.

    It's enough work that I'm somewhat regretting it.

    #mastodon #mastodonapi

  14. 🆕 blog! “Getting started with Mastodon's Quote Posts - technical implementation details for servers”

    Quoting posts on Mastodon is slightly complex. Because of the privacy conscious nature of the platform and its users, reposting isn't merely a case of sharing a URl.

    A user writes a status. The user…

    👀 Read more: shkspr.mobi/blog/2025/10/getti

    #ActivityPub #fediverse #mastodon #MastodonAPI

  15. Getting started with Mastodon's Quote Posts - technical implementation details for servers

    shkspr.mobi/blog/2025/10/getti

    Quoting posts on Mastodon is slightly complex. Because of the privacy conscious nature of the platform and its users, reposting isn't merely a case of sharing a URl.

    A user writes a status. The user can choose to make their statuses quotable or not. What happens when a quoter quotes that post?

    I've read through the specification and tried to simplify it. Quoting is a multi-step process:

    1. The status must opt-in to being shared.
    2. The quoter quotes the status.
    3. The quoter's server sends a request to the status's server.
    4. The status's server sends an accept message back to the quoter's server.
    5. When other servers see the quote, they check with the status's server to see if it is allowed.

    I'm going to walk you through each stage as best as I understand them.

    Opting In

    An ActivityPub status message is JSON. In order to opt-in, it needs this additional field.

    "interactionPolicy": {  "canQuote": {    "automaticApproval": "https://www.w3.org/ns/activitystreams#Public"  }}

    That tells ActivityPub clients that anyone is allowed to quote this post. It is also possible to say that only specific users, or only followers, or no-one is allowed.

    The QuoteRequest

    Someone has hit the quote post button, typed their own message, and shared their wisdom. Their server sends the following message to the server which hosts the quoted status. This has been edited for brevity.

    {  "@context": [    "https://www.w3.org/ns/activitystreams",    {      "QuoteRequest":   "https://w3id.org/fep/044f#QuoteRequest"    }  ],  "type": "QuoteRequest",  "id":     "https://mastodon.test/users/Edent/quote_requests/1234-5678-9101",  "actor":  "https://mastodon.test/users/Edent",  "object": "https://example.com/posts/987654321.json",  "instrument": {    "id":           "https://mastodon.test/users/Edent/statuses/123456789",    "url":          "https://mastodon.test/@Edent/123456789",    "attributedTo": "https://mastodon.test/users/Edent",    "quote":          "https://example.com/posts/987654321.json",    "_misskey_quote": "https://example.com/posts/987654321.json",    "quoteUri":       "https://example.com/posts/987654321.json"  }}

    All this says is "I would like permission to quote you."

    The Stamp

    The quoted server needs to approve this quote. First, it generates a "stamp".

    This is a file which lives on the quoted server. It is proof that the quote is allowed. If it is deleted, the quote permission is revoked. When the stamp's ID is requested the stamp must be returned.

    {  "@context": [    "https://www.w3.org/ns/activitystreams",    {      "gts": "https://gotosocial.org/ns#",      "QuoteAuthorization": {        "@id": "https://w3id.org/fep/044f#QuoteAuthorization",        "@type": "@id"      },      "interactingObject": {        "@id": "gts:interactingObject"      },      "interactionTarget": {        "@id": "gts:interactionTarget"      }    }  ],  "type": "QuoteAuthorization",  "id":                "https://example.com/quote-987654321.json",  "attributedTo":      "https://example.com/users/username",  "interactionTarget": "https://example.com/posts/987654321.json",  "interactingObject": "https://mastodon.test/users/Edent/statuses/123456789"}

    If the quoted status is viewed from a different server, that server will query the stamp to make sure the share is allowed.

    The Accept

    This is the message that the quoted server sends to the quoting server. It references the request and the stamp.

    {  "@context": [    "https://www.w3.org/ns/activitystreams",    {      "QuoteRequest": "https://w3id.org/fep/044f#QuoteRequest"    }  ],  "type": "Accept",  "to":    "https://mastodon.test/users/Edent",  "id":    "https://example.com/posts/987654321.json",  "actor": "https://example.com/account",  "object": {    "type": "QuoteRequest",    "id":         "https://mastodon.test/users/Edent/quote_requests/1234-5678-9101",    "actor":      "https://mastodon.test/users/Edent",    "instrument": "https://mastodon.test/users/Edent/statuses/123456789",    "object":     "https://example.com/posts/987654321.json"  },  "result": "https://example.com/quote-987654321.json"}

    The "result" must be the same as the stamp's URl.

    And then?

    You can follow and quote @[email protected] on your favourite Fediverse platform.

    I've written an ActivityPub server in a single file which is designed to teach you have the protocol works. Have a play with ActivityBot.

    #ActivityPub #fediverse #mastodon #MastodonAPI

  16. Another curious #ActivityPub / #MastodonAPI issue.

    A Mastodon server is sending me a DELETE message.

    The delete is because a user has been deleted.

    My server tries to validate the HTTP Signature.

    My server looks up the deleted user's main-key.

    The user has been deleted so the public key 404s.

    My server never acknowledges the delete, so the other server keeps sending me the same request.

    So… How do I validate the signature of a deleted user?

  17. Here's the Quote Request Mastodon sends me.
    colours.bots.edent.tel/data/in

    This is the Stamp my bot generates.
    colours.bots.edent.tel/quotes/

    This is the Accept my bot sends Mastodon.
    colours.bots.edent.tel/quotes/

    The Mastodon.Social server shows the quote toot. External servers don't.

    Please, someone explain what bone-headed mistake I've made.

    (Edit: Updated the links)
    #ActivityPub #MastodonAPI

  18. RE: colours.bots.edent.tel/posts/6

    Ok, I need some #ActivityPub help, please.

    The reply to this will have links to the QuoteRequest the bot received, the QuoteAuthorization which it saves, and the Accept message it returns.

    Can anyone figure out why the Quote permissions aren't showing on external servers?

    #MastodonAPI

  19. 🤖 Test post from Mastodon API client at 2025-09-27 17:15:20 #MastodonAPI #Python

  20. 📚 Example post from Mastodon API client at 2025-09-27 17:13:23 #MastodonAPI #Python #Example

  21. 🤖 Test post from Mastodon API client at 2025-09-27 17:12:45 #MastodonAPI #Python

  22. OK gang, I'm stumped (and a little drunk).

    I'm trying to get Quote posts working ActivityBot.

    ✅ Quote posts are an available option.

    ❓ This Accept message is sent - colours.bots.edent.tel/quotes/

    ❓ Which references this stamp - colours.bots.edent.tel/quotes/

    But the quote never gets approved. Can you spot any obvious mistakes with my JSON?

    #MastodonAPI

    EDIT! Solved. Turns out, you actually have to post the message to the right server. Who knew?!?!

  23. I want to allow my bots' posts to be quoted.

    Do I need all these interaction policies - or can I just have the simplified interactionPolicy?

    #MastodonAPI #QuoteToot

  24. Ω🪬Ω
    #FediAlgo (the customizable timeline algorithm / filtering system for your Mastodon feed) v1.2.2 is deployed now. Has a switch that makes sure any #hashtags / users / etc. that you follow are displayed as filter options even if they don't meet the minimum number of recent toots threshold.

    Also a bunch of bug fixes and small improvements.

    * Try it here: michelcrypt4d4mus.github.io/fe
    * Code: github.com/michelcrypt4d4mus/f
    * Video of FediAlgo in action (slightly outdated): universeodon.com/@cryptadamist

    #activitypub #algorithm #algorithmicFeed #algorithmicTimeline #Fedi #FediTips #FediTools #Fediverse #Feed #FOSS #GoToSocial #hashtag #hashtags #javascript #MastoAdmin #Mastodon #MastodonApi #mastohelp #mastojs #node #nodejs #opensource #socialmedia #SocialWeb #timeline #TL #typescript #webdev

  25. Finally made that tool I've been planning for a while: A configurable batch deleter of #Mastodon #bookmarks, supporting a threshold date (i.e. only older bookmarks considered) and lists of accounts and hashtags to always keep.

    gist.github.com/postspectacula

    After editing the script to fill in your own details and preferences at the top, you can run it via command line `node delete-bookmarks.js` or paste it in the browser console to execute.

    The script outputs details of each bookmark being removed, supports retrying with exponential back-off (5x) and is configured to use quite generous pauses between requests to not trigger rate limiting.

    The script also prints out `max_id` values, used for pagination purposes by the Mastodon API. Should you interrupt the script to make some changes and then re-run, you can also find the latest `max_id` and set `MAX_ID` to that value in the script to save time (bookmarks are processed in batches of 40)

    (FWIW I've been ferociously bookmarking posts for almost 3 years (had ~13500) and my media storage became over 100GB. So it's urgent time for some serious pruning...)

    #OpenSource #JavaScript #MastodonAPI #Utilities

  26. Learning about bridging older model Samsung WiFi cameras to #MastodonAPI #FrOSCon

  27. I wrote a script for finding what I need among my Mastodon bookmarks: it's a CLI client-side search of the bookmark collection, but without a display of statuses and without a search term entry.

    It can show top ten lists of things about the post (domains of URLs within, authors, media attachment types, etc) and move the bookmarks onto the start of the collection.

    codeberg.org/mtjm/fedi-scripts

    #MastodonAPI

  28. If you're interested in making #Mastodon search a little better - I think I have a good first issue for you 🙂

    github.com/mastodon/mastodon/i

    This would enable you to search for posts made *only* by those you follow.

    #MastodonAPI