Bump Mastodon API to 2.7.2 #734

Closed
opened 2019-03-17 11:56:18 +00:00 by lanodan · 14 comments
Contributor

Current advertised Mastodon API version: 2.5.0

From mastodon release notes, may have missed some, may have got non-applicable ones or one we do not want to add, some might already be resolved:

2.7.2

2.7.0

2.6.5

2.6.2

2.6.0

I’m assigning this issue to me but feel free to ask to add some of them or help verify the presence of some in pleroma, I’ll start on 2.6.0 and end on 2.7.2.

Current advertised Mastodon API version: `2.5.0` From mastodon release notes, may have missed some, may have got non-applicable ones or one we do not want to add, some might already be resolved: ## 2.7.2 - [X] (https://git.pleroma.social/pleroma/pleroma/pulls/4365) Add `registrations` attribute to `GET /api/v1/instance` https://github.com/tootsuite/mastodon/pull/10060 - [x] (https://git.pleroma.social/pleroma/pleroma/pulls/4367) Add `vapid_key` to `POST /api/v1/apps` and `GET /api/v1/apps/verify_credentials` https://github.com/tootsuite/mastodon/pull/10058 ## 2.7.0 - [x] Add joining several hashtags in a single column https://github.com/tootsuite/mastodon/pull/8904 - [x] (https://git.pleroma.social/pleroma/pleroma/pulls/4391) Add REST API for creating an account https://github.com/tootsuite/mastodon/pull/9572 - [x] Add exclude_reblogs option to account statuses API https://github.com/tootsuite/mastodon/pull/9640 - [x] (https://git.pleroma.social/pleroma/pleroma/pulls/4375) Add scheduled statuses https://github.com/tootsuite/mastodon/pull/9706 - [x] Allow unauthenticated REST API access to GET /api/v1/accounts/:id/statuses https://github.com/tootsuite/mastodon/pull/9573 - [x] (https://git.pleroma.social/pleroma/pleroma/pulls/4364) Change API error message for unconfirmed accounts https://github.com/tootsuite/mastodon/pull/9625 ## 2.6.5 - [x] Change lists to display replies to others on the list and list owner https://github.com/tootsuite/mastodon/pull/9324 ## 2.6.2 - [x] Fix filter ID not being a string in REST API https://github.com/tootsuite/mastodon/pull/9303 ## 2.6.0 - [x] (<del>https://git.pleroma.social/pleroma/pleroma/pulls/4333</del> https://git.pleroma.social/pleroma/pleroma/pulls/4427) Conversations API https://github.com/tootsuite/mastodon/pull/8832 / Revamped direct messages column https://github.com/tootsuite/mastodon/pull/9022 - [x] (https://git.pleroma.social/pleroma/pleroma/pulls/4362) Support backwards pagination https://github.com/tootsuite/mastodon/pull/8736 https://git.pleroma.social/pleroma/pleroma/issues/351 - [x] (https://git.pleroma.social/pleroma/pleroma/pulls/4385) Support different accounts on OAuth authorize page https://github.com/tootsuite/mastodon/pull/8655 - [x] Add `card` attribute to statuses returned from REST API https://github.com/tootsuite/mastodon/pull/9120 I’m assigning this issue to me but feel free to ask to add some of them or help verify the presence of some in pleroma, I’ll start on 2.6.0 and end on 2.7.2.
Member
> Fix filter ID not being a string in REST API already fixed https://git.pleroma.social/pleroma/pleroma/blob/develop/lib/pleroma/web/mastodon_api/views/filter_view.ex#L23
Author
Contributor

Add exclude_reblogs option to account statuses API https://github.com/tootsuite/mastodon/pull/9640

Done in #3991

> Add exclude_reblogs option to account statuses API https://github.com/tootsuite/mastodon/pull/9640 Done in https://git.pleroma.social/pleroma/pleroma/pulls/3991
Author
Contributor

Allow unauthenticated REST API access to GET /api/v1/accounts/:id/statuses https://github.com/tootsuite/mastodon/pull/9573

Confirmed to be currently working (used it to verify exclude_reblogs with a simple curl | jq).

> Allow unauthenticated REST API access to GET /api/v1/accounts/:id/statuses https://github.com/tootsuite/mastodon/pull/9573 Confirmed to be currently working (used it to verify `exclude_reblogs` with a simple `curl | jq`).
Author
Contributor

Add vapid_key to POST /api/v1/apps and GET /api/v1/apps/verify_credentials

It looks like it’s /api/v1/accounts/verify_credentials instead of /api/v1/apps/verify_credentials, changing the description. Also the entity documentation is missing, so I’ll check against a real mastodon to see if I’m right and I’m not missing anything.

EDIT: Scratch that, we are missing the whole of /api/v1/apps/verify_credentials, which is mentionned in the documentation, only the returned entity isn’t described.

> Add vapid_key to POST /api/v1/apps and GET /api/v1/apps/verify_credentials It looks like it’s `/api/v1/accounts/verify_credentials` instead of `/api/v1/apps/verify_credentials`, changing the description. Also the entity documentation is missing, so I’ll check against a real mastodon to see if I’m right and I’m not missing anything. EDIT: Scratch that, we are missing the whole of `/api/v1/apps/verify_credentials`, which is mentionned in the documentation, only the returned entity isn’t described.
Member

@lanodan, 2.7.0 feature (Change API error message for unconfirmed accounts): #4364

@lanodan, 2.7.0 feature (Change API error message for unconfirmed accounts): https://git.pleroma.social/pleroma/pleroma/pulls/4364
Member

@lanodan, 2.7.2 feature (Add registrations attribute to GET /api/v1/instance): #4365

@lanodan, 2.7.2 feature (Add `registrations` attribute to `GET /api/v1/instance`): https://git.pleroma.social/pleroma/pleroma/pulls/4365
Member

Going to take Pleroma implementation of 2.6.0's "Support different accounts on OAuth authorize page" https://github.com/tootsuite/mastodon/pull/8655

Going to take Pleroma implementation of 2.6.0's "Support different accounts on OAuth authorize page" https://github.com/tootsuite/mastodon/pull/8655
Author
Contributor

Change lists to display replies to others on the list and list owner https://github.com/tootsuite/mastodon/pull/9324

I’ll set this one as valid, we show replies in it like for the other timelines, the exact behaviour is probably not the same but I think it’s close enough.

> Change lists to display replies to others on the list and list owner https://github.com/tootsuite/mastodon/pull/9324 I’ll set this one as valid, we show replies in it like for the other timelines, the exact behaviour is probably not the same but I think it’s close enough.
Author
Contributor

Add REST API for creating an account https://github.com/tootsuite/mastodon/pull/9572

I’m taking this one btw.

EDIT: MR is #4391

> Add REST API for creating an account https://github.com/tootsuite/mastodon/pull/9572 I’m taking this one btw. EDIT: MR is https://git.pleroma.social/pleroma/pleroma/pulls/4391
Member

@lanodan, see #773 (seems to duplicate the above; recently assigned to @satchinjoshi but I suppose the work wasn't yet started).

@lanodan, see https://git.pleroma.social/pleroma/pleroma/issues/773 (seems to duplicate the above; recently assigned to @satchinjoshi but I suppose the work wasn't yet started).
Member

(#4385) Support different accounts on OAuth authorize page https://github.com/tootsuite/mastodon/pull/8655

Implemented in #4385. CC @lanodan

> (https://git.pleroma.social/pleroma/pleroma/pulls/4385) Support different accounts on OAuth authorize page https://github.com/tootsuite/mastodon/pull/8655 Implemented in https://git.pleroma.social/pleroma/pleroma/pulls/4385. CC @lanodan
Author
Contributor

Haelwenn @lanodan marked the task (#4364 (merged)) Change API error message for unconfirmed accounts https://github.com/tootsuite/mastodon/pull/9625 as incomplete just now

This is because the error messages doesn’t match, it’s not a huge blocker and I think we could still bump the version but it would be nice if it would be fixed.

> Haelwenn @lanodan marked the task (#4364 (merged)) Change API error message for unconfirmed accounts https://github.com/tootsuite/mastodon/pull/9625 as incomplete just now This is because the error messages doesn’t match, it’s not a huge blocker and I think we could still bump the version but it would be nice if it would be fixed.
Member

@lanodan pl. refer to the latest Mastodon version. They already changed the message (which #4364 did match at the time of creation and likely still matches; upd.: it does) — what is the reason to mimic an already obsolete message??

@lanodan pl. refer to the latest Mastodon version. They already changed the message (which https://git.pleroma.social/pleroma/pleroma/pulls/4364 _did_ match at the time of creation and likely still matches; upd.: it does) — what is the reason to mimic an already obsolete message??
Owner

This should be completed now.

This should be completed now.
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
pleroma/pleroma#734
No description provided.