aboutsummaryrefslogtreecommitdiff
path: root/docs/api/differences_in_mastoapi_responses.md
AgeCommit message (Collapse)Author
2019-10-02Rename some directories because MkDocs uses them for categoriesrinpatch
2019-09-19API Docs: Document conversation ids.lain
2019-09-17Mastodon API: Add a setting to hide follow/follower count from the user view ↵eugenijm
(`hide_follows_count` and `hide_followers_count`)
2019-09-10Add note about limit to the docEgor Kislitsyn
2019-09-10Add an endpoint to get multiple statuses by IDsEgor Kislitsyn
2019-09-04Mastodon API: Add `pleroma.thread_muted` to Status entityrinpatch
Needed for pleroma-fe!941
2019-08-24Activity expiration: Fix docs.lain
2019-08-24Merge remote-tracking branch 'origin/develop' into ↵lain
sixohsix/pleroma-post_expiration
2019-08-05Pleroma Conversations: Document differences.lain
2019-07-24Revert "squash! Expose expires_at datetime in mastoAPI only for the activity ↵Mike Verdone
actor" This reverts commit 2981821db834448bf9b2ba26590314e36201664c.
2019-07-24squash! Expose expires_at datetime in mastoAPI only for the activity actorMike Verdone
NOTE: rewrite the commit msg
2019-07-24Expose expires_at datetime in mastoAPI only for the activity actorMike Verdone
In the "pleroma" section of the MastoAPI for status activities you can see an expires_at item that states when the activity will expire, or nothing if the activity will not expire. The expires_at date is only visible to the person who posted the activity. This is the conservative approach in case some attacker decides to write a logger for expiring posts. However, in the future of OCAP, signed requests, and all that stuff, this attack might not be that likely. Some other pleroma dev should remove the restriction in the code at that time, if they're satisfied with the security implications of doing so.
2019-07-24Add support for activity expiration to common and Masto APIMike Verdone
The "expires_at" parameter accepts an ISO8601-formatted date which defines when the activity will expire. At this point the API will not give you any feedback about if your post will expire or not.
2019-07-19Merge branch 'develop' into feature/matstodon-statuses-by-nameMark Felder
2019-07-16Add `pleroma.deactivated` to the Account entity (Mastodon API)Eugenij
2019-07-15Merge branch 'develop' into feature/matstodon-statuses-by-nameMark Felder
2019-07-15Update documentationEgor Kislitsyn
2019-07-15Merge remote-tracking branch 'pleroma/develop' into feature/addressable-listsEgor Kislitsyn
2019-07-12Move these to pleroma namespace in Mastodon APIMark Felder
2019-07-11Merge branch 'develop' into feature/addressable-listsEgor Kislitsyn
2019-07-09Docs/more mastodon apifeld
2019-06-15Documentation: Document chat token response.lain
2019-06-14Mastodon API: Document changes.lain
2019-06-05Merge remote-tracking branch 'pleroma/develop' into feature/addressable-listsEgor Kislitsyn
2019-06-05Merge branch 'explicit-addressing' into 'develop'kaniini
Explicit addressing See merge request pleroma/pleroma!1239
2019-06-05Merge remote-tracking branch 'pleroma/develop' into feature/addressable-listsEgor Kislitsyn
2019-06-04fix mergeMaksim Pechnikov
2019-06-04Merge remote-tracking branch 'pleroma/develop' into feature/addressable-listsEgor Kislitsyn
2019-06-04Merge remote-tracking branch 'origin/develop' into explicit-addressinglain
2019-06-04Docs: Add Explicit addressing to Readme and changelog.lain
2019-06-04Merge branch 'develop' into issue/941Maksim Pechnikov
2019-06-03update api to set skip_thread_containmentMaksim Pechnikov
2019-05-31Documentation: Document Settings store mechanism.lain
2019-05-29Update docs to reflect we accept nickname for id for both of these endpointsMark Felder
2019-05-14Add documentationEgor Kislitsyn
2019-05-13differences_in_mastoapi_responses.md: fullname & bio are optionnalAlexander Strizhakov
[ci skip]
2019-05-06fix formatMaksim
Modified-by: Maksim Pechnikov <parallel588@gmail.com>
2019-04-27Add default_scope to /api/v1/update_credentialsrinpatch
2019-04-25Move settings to Source subentityrinpatch
2019-04-24Fix leaking private configuration parameters in Mastodon and Twitter APIs, ↵rinpatch
and add new configuration parameters to Mastodon API This patch: - Fixes `rights` in twitterapi ignoring `show_role` - Fixes exposing default scope of the user to anyone in Mastodon API - Extends Mastodon API to be able to show and set `no_rich_text`, `default_scope`, `hide_follows`, `hide_followers`, `hide_favorites` (requested by the FE in #674) Sorry in advance for 500 line one commit diff, I should have split it up to separate MRs
2019-04-22Add `pleroma.in_reply_to_account_acct` to MastoAPI status entityrinpatch
2019-04-21differences_in_mastoapi_responses.md: `content_type` parameter of post ↵Haelwenn (lanodan) Monnier
submission
2019-04-18Do not require authentication for user search in MastoAPIMark Felder
2017-01-01Provide plaintext representations of content/cw in MastoAPIrinpatch
2019-04-02Fix preview not being usable in form datarinpatch
2019-04-02Rename fake param to preview and make the tests check that the object was ↵rinpatch
not inserted to the db
2019-03-29document fake optionrinpatch
2019-03-28Move out of Gitlab Wikirinpatch
I understand that this change is quite unreadable and hard to review, sorry for forgetting to do atomic commits. This patch does not change too much content wise, it just * Gets everything from gitlab wiki * Removes some specific gitlab hacks * Formats all documentation file names to be in snake case so they look the same way as our code does
generated by cgit v1.2.3 (git 2.26.2) at 2025-04-27 08:02:15 +0000