[Feature Request] Support Mastodon

[rodneyrod]

Mastodon is a new server for interacting with StatusNet networks, but it doesn't seem to use a client connection method that is compatible with existing StatusNet clients. Support for this will have to be added.

https://github.com/tootsuite/mastodon/blob/master/docs/Using-Mastodon/FAQ.md

[yvolk]

A long story of this incompatibility is here (without any end though...) andstatus/andstatus#419

[yvolk]

A long story of this incompatibility is here (without any end though...) andstatus/andstatus#419

[Lertsenem]

If I understand well, Mastodon does not offer a StatusNet API by design. But it does offer a twitter-like API that Twidere could probably use with little adjustments.

[Lertsenem]

If I understand well, Mastodon does not offer a StatusNet API by design. But it does offer a twitter-like API that Twidere could probably use with little adjustments.

[yvolk]

"StatusNet API" is the "Twitter compatible API". This is why I advised @Gargron to adopt it, for compatibility with existing clients.

[yvolk]

"StatusNet API" is the "Twitter compatible API". This is why I advised @Gargron to adopt it, for compatibility with existing clients.

[Gargron]

The mastodon client API is only twitter-like in that all REST JSON APIs are like twitter's. The StatusNet API was bad, so I didn't copy it. We had good success creating apps for the Mastodon API, with lots of positive feedback from devs saying it's really straightforward and easy. It's all in the past anyway, don't see how discussing it is productive.

[Gargron]

The mastodon client API is only twitter-like in that all REST JSON APIs are like twitter's. The StatusNet API was bad, so I didn't copy it. We had good success creating apps for the Mastodon API, with lots of positive feedback from devs saying it's really straightforward and easy. It's all in the past anyway, don't see how discussing it is productive.

[Lertsenem]

Nevermind the API, as a user the Twidere app is vastly more mature than what Tusky can offer now, and for quite some time I'm sure. Plus the multi account management is a killer feature for any user willing to migrate from Twitter to Mastodon.

@Gargron, I hear you when you say that the StatusNet API is bad, but would the cost of implementing it alongside your new API that high ? Would you reject PR aiming to do this or are you just not interested enough to do the work yourself ?

Separately, would the implementation of Mastodon API as an alternative in Twidere be doable ? Would it be hard ?

[Lertsenem]

Nevermind the API, as a user the Twidere app is vastly more mature than what Tusky can offer now, and for quite some time I'm sure. Plus the multi account management is a killer feature for any user willing to migrate from Twitter to Mastodon.

@Gargron, I hear you when you say that the StatusNet API is bad, but would the cost of implementing it alongside your new API that high ? Would you reject PR aiming to do this or are you just not interested enough to do the work yourself ?

Separately, would the implementation of Mastodon API as an alternative in Twidere be doable ? Would it be hard ?

[yvolk]

@Gargron I understood your "disappearance" from our discussion at andstatus/andstatus#419 (that you started) as you had no arguments to support your decision on API and you lost interest to implement it yourself... ?!

[yvolk]

@Gargron I understood your "disappearance" from our discussion at andstatus/andstatus#419 (that you started) as you had no arguments to support your decision on API and you lost interest to implement it yourself... ?!

[mariotaku]

Twidere can add support for other social platforms, as long as basic requirements met (users/status objects with unique id). It won't too hard technically speaking, however it would be a rather huge work to do. I'm willing to accept PRs that add Mastodon support.

[mariotaku]

Twidere can add support for other social platforms, as long as basic requirements met (users/status objects with unique id). It won't too hard technically speaking, however it would be a rather huge work to do. I'm willing to accept PRs that add Mastodon support.

[mariotaku]

So here's what we need to support Mastodon:

• OAuth 2 authorization (easy, a header is enough)
• Login flow
• Mastodon specific account info
• Mastodon objects (Posts, Users...)
• Mastodon API (See Twitter API for example, just need to annotate some interfaces)
• Utility classes converts Mastodon object to Twidere's ParcelableXXX object

Guys, since I have something else to do (iOS version and my work and my school works), could anyone help me doing tasks I've mentioned above? This can help this feature finished sooner.

[mariotaku]

So here's what we need to support Mastodon:

• OAuth 2 authorization (easy, a header is enough)
• Login flow
• Mastodon specific account info
• Mastodon objects (Posts, Users...)
• Mastodon API (See Twitter API for example, just need to annotate some interfaces)
• Utility classes converts Mastodon object to Twidere's ParcelableXXX object

Guys, since I have something else to do (iOS version and my work and my school works), could anyone help me doing tasks I've mentioned above? This can help this feature finished sooner.

[vanita5]

I'm currently working with the Mastodon API and I'd love to implement this, but I'm afraid I won't have time 'till next weekend.

If anyone else is interested in helping out in the meantime, you can take a look at my node library regarding the login flow and how to get an access token: https://github.com/vanita5/mastodon-api

[vanita5]

I'm currently working with the Mastodon API and I'd love to implement this, but I'm afraid I won't have time 'till next weekend.

If anyone else is interested in helping out in the meantime, you can take a look at my node library regarding the login flow and how to get an access token: https://github.com/vanita5/mastodon-api

[mariotaku]

I really should've give up any hope that anyone will help me with this feature. Is arguing about API more productive than implementing some features that can be done within 3 days?

[mariotaku]

I really should've give up any hope that anyone will help me with this feature. Is arguing about API more productive than implementing some features that can be done within 3 days?

[Lertsenem]

Sorry, I would help but unfortunately I don't speak neither Java nor Kotlin. :/

[Lertsenem]

Sorry, I would help but unfortunately I don't speak neither Java nor Kotlin. :/

[cyphar]

Another thing to note that Twidere has above Tusky is that Twidere is actually available in FDroid. Tusky recently added proprietary requirements which made it non-free -- making it impossible to have a Mastodon app on your phone if you don't have the Play Store. I'm not a great Java developer (if I was I definitely would be helping out). 😢

[cyphar]

Another thing to note that Twidere has above Tusky is that Twidere is actually available in FDroid. Tusky recently added proprietary requirements which made it non-free -- making it impossible to have a Mastodon app on your phone if you don't have the Play Store. I'm not a great Java developer (if I was I definitely would be helping out). 😢

[mariotaku]

What still needs to be done:

• Edit profile
• Follow/block/mute
• Set visibility for status
• Ensure account color set (by adding toParcelable(AccountDetails) maybe?)

[mariotaku]

What still needs to be done:

• Edit profile
• Follow/block/mute
• Set visibility for status
• Ensure account color set (by adding toParcelable(AccountDetails) maybe?)

[mariotaku]

I guess this can be marked as done. Please test 3.5.23 version and help me to make sure every function is working properly.

[mariotaku]

I guess this can be marked as done. Please test 3.5.23 version and help me to make sure every function is working properly.

[Lertsenem]

Nice! Thank you so much!

[Lertsenem]

Nice! Thank you so much!

[MightyPork]

Some bugs I found while testing it:

• notifications and the like say 'tweet' instead of 'toot'
• the reply box has a 140 char limit (click 'reply' on a toot) Apparently this is because it somehow posted my test toot also to twitter and the mention I was trying to reply to was a tweet. Really confusing (especially when both accounts have the same avatar)
• "network public" timeline is not federated, but also local - so you get it twice
• apostrophes and maybe other things show as HTML entities
• getting lots of duplicate notifications (already dismissed)
• timelines don't seem to want to update unless I pull down
• the hashtag tab is always empty (maybe it shouldn't be added when the user creates a mastodon account?)
• the DMs tab for some reason shows DMs from Twitter

[MightyPork]

Some bugs I found while testing it:

• notifications and the like say 'tweet' instead of 'toot'
• the reply box has a 140 char limit (click 'reply' on a toot) Apparently this is because it somehow posted my test toot also to twitter and the mention I was trying to reply to was a tweet. Really confusing (especially when both accounts have the same avatar)
• "network public" timeline is not federated, but also local - so you get it twice
• apostrophes and maybe other things show as HTML entities
• getting lots of duplicate notifications (already dismissed)
• timelines don't seem to want to update unless I pull down
• the hashtag tab is always empty (maybe it shouldn't be added when the user creates a mastodon account?)
• the DMs tab for some reason shows DMs from Twitter

[Lertsenem]

I found some others (testing 3.5.25). Should we write them here for the time being, or should we open new issues right now?

• not only apostrophes, but line breaks are not properly rendered too
• replying to a toot does not use the user full handle (only the username, not the instance), so the mentions cannot work out of the box for external users
• when you use both a twitter and a mastodon account, modifying the interactions tab to print only the mastodon account notifs makes it unable to show follows/favs/RTs (only mentions)

timelines don't seem to want to update unless I pull down

I couldn't reproduce this. Auto-refresh is working on my device.

[Lertsenem]

I found some others (testing 3.5.25). Should we write them here for the time being, or should we open new issues right now?

• not only apostrophes, but line breaks are not properly rendered too
• replying to a toot does not use the user full handle (only the username, not the instance), so the mentions cannot work out of the box for external users
• when you use both a twitter and a mastodon account, modifying the interactions tab to print only the mastodon account notifs makes it unable to show follows/favs/RTs (only mentions)

timelines don't seem to want to update unless I pull down

I couldn't reproduce this. Auto-refresh is working on my device.

[picsi]

@mariotaku can you let us know when you push this update to F-Droid? Thanks.

[picsi]

@mariotaku can you let us know when you push this update to F-Droid? Thanks.

[Hund]

@picsi The guys over at F-Droid compiles the packages themselves.

[Hund]

@picsi The guys over at F-Droid compiles the packages themselves.

[mariotaku]

@Lertsenem

not only apostrophes, but line breaks are not properly rendered too

#779

replying to a toot does not use the user full handle (only the username, not the instance), so the mentions cannot work out of the box for external users

#776

[mariotaku]

@Lertsenem

not only apostrophes, but line breaks are not properly rendered too

#779

replying to a toot does not use the user full handle (only the username, not the instance), so the mentions cannot work out of the box for external users

#776

[mariotaku]

@MightyPork

notifications and the like say 'tweet' instead of 'toot'

Yes, this is because Twidere still uses Twitter's writing style, it will make text needed to translate multiplied if we add text for platforms respectively

the reply box has a 140 char limit (click 'reply' on a toot)

You can set account color in 'Accounts' list.

"network public" timeline is not federated, but also local

#777

apostrophes and maybe other things show as HTML entities

#773

getting lots of duplicate notifications

#770

timelines don't seem to want to update unless I pull down

#753

the hashtag tab is always empty

OK, I'll consider making this tab not added by default when a user login to mastodon instances

the DMs tab for some reason shows DMs from Twitter

Mastodon doesn't have DM feature yet.

[mariotaku]

@MightyPork

notifications and the like say 'tweet' instead of 'toot'

Yes, this is because Twidere still uses Twitter's writing style, it will make text needed to translate multiplied if we add text for platforms respectively

the reply box has a 140 char limit (click 'reply' on a toot)

You can set account color in 'Accounts' list.

"network public" timeline is not federated, but also local

#777

apostrophes and maybe other things show as HTML entities

#773

getting lots of duplicate notifications

#770

timelines don't seem to want to update unless I pull down

#753

the hashtag tab is always empty

OK, I'll consider making this tab not added by default when a user login to mastodon instances

the DMs tab for some reason shows DMs from Twitter

Mastodon doesn't have DM feature yet.

[mariotaku]

Please, open separate issues rather than commenting here to make sure they get tracked respectively

[mariotaku]

Please, open separate issues rather than commenting here to make sure they get tracked respectively

[cyphar]

@mariotaku

the DMs tab for some reason shows DMs from Twitter

Mastodon doesn't have DM feature yet.

OStatus (Mastodon) has different privacy preferences for messages, so "DMs" are supported, they're just not a separate communication method (you can send a message to someone that only you and they can read).

[cyphar]

@mariotaku

the DMs tab for some reason shows DMs from Twitter

Mastodon doesn't have DM feature yet.

OStatus (Mastodon) has different privacy preferences for messages, so "DMs" are supported, they're just not a separate communication method (you can send a message to someone that only you and they can read).

[mariotaku]

@cyphar 'Direct' statuses in Mastodon still should be treated as status, because they mixed in notifications timeline. I'll make this DM conversation style only when it have related API to do that.

[mariotaku]

@cyphar 'Direct' statuses in Mastodon still should be treated as status, because they mixed in notifications timeline. I'll make this DM conversation style only when it have related API to do that.

[cyphar]

Fair enough, I was just pointing out that in OStatus I don't believe there is any plan to have "DMs" because privacy options fulfill that need in a more generic way.

[cyphar]

Fair enough, I was just pointing out that in OStatus I don't believe there is any plan to have "DMs" because privacy options fulfill that need in a more generic way.

[mariotaku]

@cyphar Yeah, Mastodon's 'Direct' mentions are still not private enough since recipients may not respect this visibility.

[mariotaku]

@cyphar Yeah, Mastodon's 'Direct' mentions are still not private enough since recipients may not respect this visibility.