Discussion: remove / deprecate Misskey client API #222

Open
opened 2023-09-15 12:03:03 +02:00 by aylamz · 5 comments
Member

Is there anything the Mastodon API can't do that Misskey API can? If there is, I feel like Mastodon and Iceshrimp are similar enough in functionality (both are microblogging focused) that we could just extend Mastodon API instead of maintaining an entire separate API. Also Mastodon API is way more popular and has become a de facto standard, so it would make sense to focus on that. Don't think we need two different ways of basically doing the same thing.

Is there anything the Mastodon API can't do that Misskey API can? If there is, I feel like Mastodon and Iceshrimp are similar enough in functionality (both are microblogging focused) that we could just extend Mastodon API instead of maintaining an entire separate API. Also Mastodon API is way more popular and has become a de facto standard, so it would make sense to focus on that. Don't think we need two different ways of basically doing the same thing.
aylamz added the
discussion
label 2023-09-15 12:03:03 +02:00
Member

I agree that Mastodon's API has become a standard for activitypub microblogging, and this is reflected in the range of third-party applications and services on offer.

But how would it look for Misskey's own features like pages, antennas and channels, clip?

I agree that Mastodon's API has become a standard for activitypub microblogging, and this is reflected in the range of third-party applications and services on offer. But how would it look for Misskey's own features like pages, antennas and channels, clip?
Member

Pleroma and Akkoma have it's own API on top of Mastodon API which is used as a base. For clips i think it would be good to make mastodon api bookmark endpoints work for only one pre-defined private clip list, and then expand that in that separate API

Pleroma and Akkoma have it's own API on top of Mastodon API which is used as a base. For clips i think it would be good to make mastodon api bookmark endpoints work for only one pre-defined private clip list, and then expand that in that separate API
Author
Member

@zotan what do you think of this?

@zotan what do you think of this?
Owner

As a long term goal, maybe. For now, iterative improvements of the mastodon API are necessary before we can consider this

As a long term goal, maybe. For now, iterative improvements of the mastodon API are necessary before we can consider this
Author
Member

As a long term goal, maybe. For now, iterative improvements of the mastodon API are necessary before we can consider this

Agreed. But we can still decide now without immediately removing it. This would mean essentially deprecating it and shifting focus to improving Mastodon API (which I understand you are already working on). And only having Mastodon API would make the Rust rewrite be less work as well, assuming there's still interest in doing that.

> As a long term goal, maybe. For now, iterative improvements of the mastodon API are necessary before we can consider this Agreed. But we can still decide now without immediately removing it. This would mean essentially deprecating it and shifting focus to improving Mastodon API (which I understand you are already working on). And only having Mastodon API would make the Rust rewrite be less work as well, assuming there's still interest in doing that.
Sign in to join this conversation.
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: iceshrimp/iceshrimp#222
No description provided.