Add identity proofs API on GET /api/v1/accounts/$id/identity_proofs

Hello :)

Thanks for maintaining this module so frequently to keep up with Mastodon's evolution.

I guess this is related to #60 but not sure how.

I'm trying to build a small bot to post images on a Mastodon account. I'm using version 2.4.0 of the module, and when trying to build my script with typescript, I get the error above in clients/masto/params.d.ts

Here's my tsconfig :

{
	"compilerOptions": {
		// Target latest version of ECMAScript.
		"target": "esNext",
		"module": "commonjs",
		// Search under node_modules for non-relative imports.
		"moduleResolution": "node",
		// Enable strictest settings like strictNullChecks & noImplicitAny.
		// true is better but requires a global refactoring.
		"strict": false,
		// Disallow features that require cross-file information for emit.
		"isolatedModules": true,
		// Import non-ES modules as default imports.
		"esModuleInterop": true,
		// Import constants from JSON (locales).
		"resolveJsonModule": true,
		"sourceMap": true,
		"outDir": "dist/",
		"pretty": true,
		"removeComments": true,
		"downlevelIteration": true,
		"listFiles": true,
		"listEmittedFiles": true,
		"noUnusedParameters": true,
		"noUnusedLocals": true
	},
	"include": [
		"src"
	],
}

Did I do something wrong? Hope you can help.

For some reason it's trying to import Conversation from src/entities/Conversation instead of via relative path, ../entities/Conversation;

It appears that uploading media attachments is broken. I get the below error with both my own code and the original example form inside the project.

(node:19274) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'name' of null
    at FormData._getContentDisposition (/mnt/dev/bot/node_modules/form-data/lib/form_data.js:226:40)
    at FormData._multiPartHeader (/mnt/dev/bot/node_modules/form-data/lib/form_data.js:177:33)
    at FormData.append (/mnt/dev/bot/node_modules/form-data/lib/form_data.js:70:21)
    at createFormData (/mnt/dev/bot/node_modules/masto/dist/index.js:1:4494)
    at /mnt/dev/bot/node_modules/masto/dist/index.js:1:4447
    at Array.forEach (<anonymous>)
    at createFormData (/mnt/dev/bot/node_modules/masto/dist/index.js:1:4409)
    at /mnt/dev/bot/node_modules/masto/dist/index.js:1:4447
    at Array.forEach (<anonymous>)
    at createFormData (/mnt/dev/bot/node_modules/masto/dist/index.js:1:4409)
(node:19274) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:19274) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.```

With current stream method there is no way to know about underlying websocket connection errors and handle them when necessary.

Returning an event emitter decorating WebSocketConnection (or directly the WebSocketConnection event emitter) would allow to do that.

What do you think about something like (stream: string, recieved: (message: {event: string, payload: any}) => void): Promise<WebSocketConnection> instead of current stream: string, recieved: (message: {event: string, payload: any}) => void) ?

https://github.com/tootsuite/mastodon/releases/tag/v2.9.0rc1

• blurhash key of Attachment

e.g.

new Mastodon({
  token:        `my token`,
  url:          `https://example.com`,
  streamingUrl: `wss://example.com`
});

related to the 2.6.0 rc-3 release

• conversations endpoints
• pagination with min_id

Type of Filter[‘id’] requires update since it has been outdated

FetchAccessTokenParamsWithPassword?

e.g.

async () => {
  for await (statuses of fetchTimeline('public')) {
    statuses // Mastodon.Status[]
  }
}

import Mastodon from '@lagunehq/core'

const masto = new Mastodon({
    url: 'https://eldritch.cafe',
    streamingUrl: 'wss://eldritch.cafe',
    token: 'xxx',
})

fetch()

async function fetch() {
    for await (const stats of masto.fetchHomeTimeline()) {
        console.log(stats)
    }
}

UnhandledPromiseRejectionWarning: TypeError: Symbol.asyncIterator is not defined.
at __asyncGenerator (xxx/node_modules/@lagunehq/core/dist/client/Mastodon.js:63:38)

Note: Streams works well

POST /api/v1/notifications/dismiss?id=:id is deprecated since 2.6 and removed since 3.0 (see mastodon/mastodon#11214)

I didn't make a PR because I don't know if you want your lib to be compatible with mastodon before 2.6.

Other methods in Masto that request POST are prefixed by create-, so it should be the same for uploadMediaAttachment for consistency.

I use Axios as an HTTP client on this project, but I feel it's not well-maintained, and obsolete since it's implemented by XMLHttpRequest not Fetch API.

So I'm planning to try some other HTTP wrapper such as Gaxios which is a package that is compatible with Axios written in TypeScript, maintained by Google.

I'm also having a look at ky, node-fetch (or just window.fetch on browsers), but both are written in pure JS and I can't say they both are strictly typed.

Refs

• https://github.com/axios/axios/issues
• https://github.com/neet/masto.js/blob/master/src/gateway/is-axios-error.ts

• Add vapid_key mastodon/mastodon#10058
• Add registrations mastodon/mastodon#10060

should be an array of FilterContexts

Disable "exports: named" in rollup.config.js to make default importing with require possible

According to this, client.search() does a POST against the search endpoint, when it needs to be a GET.

Also, for us over in TypeScript-land, the V argument doesn't seem to be filling properly.

Currently, some of the TypeDoc comments are outdated/incorrect, so they need be updated.

When constructing the class, fetch /instance and set uri.streaming_api as the url

Remove simplytyped's Omit and use builtin one that has been added in the newer version.

Advanced ts types such as params.ts is getting complex and it would be better to add unit tests for making the behaviour clear.
Ref: https://kgtkr.net/blog/2018/09/10/typescript-unit-test-type

Cannot update source of credential by Masto.updateCredential because it is impossible to send nested object through multipart/form-data.
So keys have to be encoded like a[b][c]

Change the linting tool to ESlint instead of TSLint, since TSLint has been deprecated

Edit I've also noticed some of the extended rules are warning errors but I would change linter to ESLint rather than fix the errors.

• Trends /api/v1/trends mastodon/mastodon/pull/11490
• Markers /api/v1/markers mastodon/mastodon/pull/11762
• Featured tags /api/v1/featured_tags mastodon/mastodon/pull/11778
• Profile Directory mastodon/mastodon/pull/11688
• Return type of follow request mastodon/mastodon/pull/11800
• Custom emoji category

Contains creating an account feature.
Ref: https://github.com/tootsuite/mastodon/releases/tag/v2.7.0rc1

Mastodon (rails) doesn’t have a difference between null and undefined in rest api, in other words, there’s 2 ways of returning “None” value. So the entities have to check null and undefined strictly with union operators.