Missing Endpoints

[schochastics]

The most important endpoints are covered (see #27) but we may still miss some smaller ones

• some more list endpoints: https://docs.joinmastodon.org/methods/timelines/lists/ (see add support for lists #136 )
• https://docs.joinmastodon.org/methods/announcements/
  - https://docs.joinmastodon.org/methods/timelines/streaming/ (see Enable streaming #84)
  - https://docs.joinmastodon.org/methods/instance/#domain_blocks (see fix #117 #118)
  - https://docs.joinmastodon.org/methods/instance/#rules (see fix #117 #118)
• https://docs.joinmastodon.org/methods/search/#v2 (not needed atm)

[noamross]

I'd add /api/v1/followed_tags, which lists followed hashtags.

It may be worthwhile to export a general API interface along the lines of gh::gh(), like rtoot::masto_api(endpoint, prefix = "/api/v1", verb = "GET", token = NULL, instance = NULL, parse = TRUE, retryonratelimit = TRUE, verbose = TRUE, ...). This would allow users to access more of the API, and new API endpoints would be accessible even before the package updates with new functions. But rtoot would still play the helpful role of dealing with auth, rate limits, etc.

[chainsawriot]

@noamross There is a helper function doing just that. Maybe @schochastics can decide whether it should be exported.

rtoot:::process_request(token = NULL, path = "api/v1/followed_tags", params = list(), parse = FALSE)

[schochastics]

I think we can export this in the next version.

[schochastics]

not supported endpoints can now be accessed via rtoot::rtoot(endpoint = "/path/to/endpoint")