Hello fediverse! Buffer now officially supports Mastodon scheduling.
The Mastodon community is growing fast, with a set of principles we admire. We’re excited to explore it with you and help you build a consistent and engaging Mastodon presence.
Let’s get tooting!
@BitsByMe the day is here! Time to start using Buffer with Mastodon!
@buffer here we goooo
@buffer GAME CHANGER
@buffer @Netzardfan
@buffer woah. That's big! Great move!
@buffer Mastodon loves it when people use alt texts for image description, so it's bad advertising if you don't write them.
@buffer read the website twice and I can't find the link to the source repo. Where can I find those ?
@buffer Great news!
@buffer but does it allow alt text to be scheduled with image posts as well?
@Artisticdork @buffer yes, this alt text is supported!
@buffer That is really great news. Also, that was quick :)
@buffer I dont have any option for Mastodon in my account channels selection
@buffer niiiiice. Gamechanger and ahead of the curve here. Awesome.
Ouch - 180 bucks for scheduling on 3 channels for a year isn't quite a steal.
Especially as Twitter and Mastodon support scheduling natively.
Maybe I need to give the trial a go to see if there are additional benefits I am missing.
@buffer Tried it while in beta, works well. Further evidence of the progression of Mastodon
@buffer blessssssss
@buffer @aethylred I wonder if my old buffer account still works….
@talios @buffer @aethylred It does! “Legacy account” - I even have Facebook configured still as a target - but I don’t believe that works anymore? Mmm
@buffer nice! Been waiting for it
@buffer I've been on this platforms and I still don't get how it works (the whole open source and other things)
@buffer
This is great news! But, I'm not seeing it in the Android app. I assume support for the Mastodon channel in the Android app is coming?
@buffer this is nice - but I’m worried that you’re going to give corporate sycophants an in to engagement without being present.
@buffer There are three things missing in Buffer for Mastodon:
1. It only supports a maximum of 500 characters. That's the Mastodon default, but many servers allow a higher number.
2. You can't set the posting language.
3. You can't easily insert custom emojis (you only can do it manually using :short_tags:)
@joenepraat @buffer
Thanks for the feedback! We'll definitely be looking into the first two that you mentioned, but the last one I don't believe is possible via the API.
@buffer I've been having a tremendous amount of issues setting up buffer, with buttons on the website not responding to clicks, and other auth issues.
Does buffer not support Firefox?
@buffer @jumar maybe
@avaloniaui could use something like this to manage social networks!
@buffer We are wondering if we can add image descriptions to scheduled posts for Mastodon?
@apache_be @buffer yes, we support alt text! If you click the image once you upload it to the Buffer composer, you'll see an option to add them.
@buffer that’s awesome. Good to see you guys here!
@buffer
Great! Nice to see you guys pioneering #Mastodon support. Used #Buffer to post to the #Fediverse already, and it worked really great so far! Kudos! ;)
@buffer Very good news, thanks you!
Is it possible to schedule a post with a content warning?
Also, any plan for PixelFed support in the future?
@buffer
I don't think my message on my other account went through, but please also consider integrating with Pixelfed as well! Pixelfed is the Fediverse's alternative to Instagram!
@buffer hi! One of my use cases is to prevent spamming my followers when I boost a lot of things in quick succession. If I use “share” in my mastodon client to send an unadorned mastodon link to buffer, I’d expect it to be posted as a boost. Instead it posts a link to the toot with the OP’s name and handle prepended, which is not useful.
Also a co-sign on supporting visibility, and for that matter content warnings too. My instance requires certain subject matter to be CW’d.
@buffer Vaamoooooosss!!!!
Viva el #fediverse
@buffer Love to try this but having some trouble connecting it to an Akkoma instance - looking in the database, it might be because your redirect_uris
on app creation has a space-separated list of URIs instead of just one? Out of 302 apps connected to my instance, it’s the only one that contains a space…
https://account.buffer.com/channels/connect https://account.buffer.com/channels/onboarding https://account.buffer.com/oauth/mastodon/callback