RasmusLindroth / tut

TUI for Mastodon with vim inspired keys
https://tut.anv.nu
MIT License
449 stars 29 forks source link

feature request: Pleroma and Misskey support #117

Open tidux opened 2 years ago

c-nv-s commented 2 years ago

also https://github.com/superseriousbusiness/gotosocial

RasmusLindroth commented 2 years ago

I can understand that people want this, but I think it would be messy. Tut uses mattn/go-mastodon under the hood to make calls to the Mastodon API and relies on the data types provided by that module. So by adding support for Pleroma, Misskey or any other alternative to Mastodon would require a redesign of tut.

But I will leave this issue open, either if someone is up for this task or can tell me that the difference between Mastodon and e.g. Plemora is small and won't require a redesign.

mricon commented 1 year ago

For pleroma, things mostly work just fine out of the box. The only thing I notice is that I have to manually execute ":newer" to get updates -- it never auto-refreshes the feed.

Ashdemai commented 1 year ago

For pleroma, things mostly work just fine out of the box. The only thing I notice is that I have to manually execute ":newer" to get updates -- it never auto-refreshes the feed.

You mean to tell me this was an existing feature all this time?

jalada commented 1 year ago

For pleroma, things mostly work just fine out of the box. The only thing I notice is that I have to manually execute ":newer" to get updates -- it never auto-refreshes the feed.

A few months ago it used to auto-refresh even for Pleroma, I'm guessing something has changed.

nekoedges commented 4 months ago

Some misskey forks support mastodon api (like Firefish and Sharkey), but you can't login because server returns 401

blacklight commented 1 month ago

After using the application for some time on my Akkoma instance, I think that the only feature I miss is the support for multiple content types.

Pleroma/Akkoma (and Misskey AFAIK) also support Markdown, while tut AFAIK provides a text-only compose interface.

It would be nice to detect if the remote supports Markdown and provide that as a compose option.

The character limit is also not displayed correctly for my instance, but that's most likely related to this issue - which is related to this issue, which is apparently a wontfix.