squeegily/pleroma
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
f168a1cbdc
pleroma/CHANGELOG.md

125 lines
7.0 KiB
Markdown
Raw Normal View History

Add a changelog
2019-04-12 17:31:18 -04:00
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
## [unreleased]
### Added
- LDAP authentication
- External OAuth provider authentication
- A [job queue](https://git.pleroma.social/pleroma/pleroma_job_queue) for federation, emails, web push, etc.
- [Prometheus](https://prometheus.io/) metrics
- Support for Mastodon's remote interaction
Add a changelog entry for removing embded objects mix task
2019-04-18 17:26:46 -04:00
- Mix Tasks: `mix pleroma.database remove_embedded_objects`
Add a changelog
2019-04-12 17:31:18 -04:00
- Federation: Support for reports
- Configuration: `safe_dm_mentions` option
- Configuration: `link_name` option
- Configuration: `fetch_initial_posts` option
changes
2019-04-17 03:27:51 -04:00
- Configuration: `notify_email` option
update Changelog
2019-04-25 19:27:38 -04:00
- Configuration: Media proxy `whitelist` option
Extend Mastodon API with public endpoint for getting Favorites timeline of any user (#789)
2019-04-22 22:47:43 -04:00
- Pleroma API: User subscriptions
Feature/826 healthcheck endpoint
2019-04-22 03:19:53 -04:00
- Pleroma API: Healthcheck endpoint
Add a changelog
2019-04-12 17:31:18 -04:00
- Admin API: Endpoints for listing/revoking invite tokens
- Admin API: Endpoints for making users follow/unfollow each other
Merge develop Merge conflict in lib/pleroma/activity.ex
2019-05-08 10:34:36 -04:00
- Admin API: added filters (role, tags, email, name) for users endpoint
Make rate limiting for Mastodon Registration API less agressive and enable it by default. As discussed on irc. Unlike Mastodon our web interface for registrations is using the same APIs regular apps would be using, so 5 requests per 30 minutes per IP could hurt valid use-cases when Pleroma-FE switches to it. Also enable the endpoint by default, it makes no sense to have it disabled when 1. TwitterAPI endpoint is there and always enabled 2. Unlike Mastodon, there is no way to get an account without using the APIs (makes me wonder why the setting is even there) Also in this commit: minor changelog improvements.
2019-05-14 15:47:23 -04:00
- AdminFE: initial release with basic user management accessible at /pleroma/admin/
Add a changelog
2019-04-12 17:31:18 -04:00
- Mastodon API: [Scheduled statuses](https://docs.joinmastodon.org/api/rest/scheduled-statuses/)
- Mastodon API: `/api/v1/notifications/destroy_multiple` (glitch-soc extension)
Extend Mastodon API with public endpoint for getting Favorites timeline of any user (#789)
2019-04-22 22:47:43 -04:00
- Mastodon API: `/api/v1/pleroma/accounts/:id/favourites` (API extension)
Add a changelog
2019-04-12 17:31:18 -04:00
- Mastodon API: [Reports](https://docs.joinmastodon.org/api/rest/reports/)
Make rate limiting for Mastodon Registration API less agressive and enable it by default. As discussed on irc. Unlike Mastodon our web interface for registrations is using the same APIs regular apps would be using, so 5 requests per 30 minutes per IP could hurt valid use-cases when Pleroma-FE switches to it. Also enable the endpoint by default, it makes no sense to have it disabled when 1. TwitterAPI endpoint is there and always enabled 2. Unlike Mastodon, there is no way to get an account without using the APIs (makes me wonder why the setting is even there) Also in this commit: minor changelog improvements.
2019-05-14 15:47:23 -04:00
- Mastodon API: `POST /api/v1/accounts` (account creation API)
Add a changelog
2019-04-12 17:31:18 -04:00
- ActivityPub C2S: OAuth endpoints
Make rate limiting for Mastodon Registration API less agressive and enable it by default. As discussed on irc. Unlike Mastodon our web interface for registrations is using the same APIs regular apps would be using, so 5 requests per 30 minutes per IP could hurt valid use-cases when Pleroma-FE switches to it. Also enable the endpoint by default, it makes no sense to have it disabled when 1. TwitterAPI endpoint is there and always enabled 2. Unlike Mastodon, there is no way to get an account without using the APIs (makes me wonder why the setting is even there) Also in this commit: minor changelog improvements.
2019-05-14 15:47:23 -04:00
- Metadata: RelMe provider
fix format Modified-by: Maksim Pechnikov <parallel588@gmail.com>
2019-05-06 13:51:03 -04:00
- OAuth: added support for refresh tokens
Add the emoji packs & finmoji removal to the changelog
2019-04-20 08:17:21 -04:00
- Emoji packs and emoji pack manager
Add a changelog
2019-04-12 17:31:18 -04:00
### Changed
Put an actual description of the vulnerability and add **Breaking:** to breaking changes
2019-04-13 14:17:10 -04:00
- **Breaking:** Configuration: move from Pleroma.Mailer to Pleroma.Emails.Mailer
Add a changelog
2019-04-12 17:31:18 -04:00
- Enforcement of OAuth scopes
- Add multiple use/time expiring invite token
- Restyled OAuth pages to fit with Pleroma's default theme
- Link/mention/hashtag detection is now handled by [auto_linker](https://git.pleroma.social/pleroma/auto_linker)
- NodeInfo: Return `safe_dm_mentions` feature flag
- Federation: Expand the audience of delete activities to all recipients of the deleted object
Remove inReplyToStatusId
2019-04-15 04:50:36 -04:00
- Federation: Removed `inReplyToStatusId` from objects
Add a changelog
2019-04-12 17:31:18 -04:00
- Configuration: Dedupe enabled by default
Add extra_cookie_attrs to changelog
2019-04-16 10:24:24 -04:00
- Configuration: Added `extra_cookie_attrs` for setting non-standard cookie attributes. Defaults to ["SameSite=Lax"] so that remote follows work.
update Changelog
2019-04-25 19:27:38 -04:00
- Timelines: Messages involving people you have blocked will be excluded from the timeline in all cases instead of just repeats.
Make rate limiting for Mastodon Registration API less agressive and enable it by default. As discussed on irc. Unlike Mastodon our web interface for registrations is using the same APIs regular apps would be using, so 5 requests per 30 minutes per IP could hurt valid use-cases when Pleroma-FE switches to it. Also enable the endpoint by default, it makes no sense to have it disabled when 1. TwitterAPI endpoint is there and always enabled 2. Unlike Mastodon, there is no way to get an account without using the APIs (makes me wonder why the setting is even there) Also in this commit: minor changelog improvements.
2019-05-14 15:47:23 -04:00
- Admin API: Move the user related API to `api/pleroma/admin/users`
- Pleroma API: Support for emoji tags in `/api/pleroma/emoji` resulting in a breaking API change
Add a changelog
2019-04-12 17:31:18 -04:00
- Mastodon API: Support for `exclude_types`, `limit` and `min_id` in `/api/v1/notifications`
- Mastodon API: Add `languages` and `registrations` to `/api/v1/instance`
- Mastodon API: Provide plaintext versions of cw/content in the Status entity
Add a changelog entry for `pleroma.in_reply_to_account_acct`
2019-04-22 05:02:41 -04:00
- Mastodon API: Add `pleroma.conversation_id`, `pleroma.in_reply_to_account_acct` fields to the Status entity
Fix leaking private configuration parameters in Mastodon and Twitter APIs, 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-24 13:01:42 -04:00
- Mastodon API: Add `pleroma.tags`, `pleroma.relationship{}`, `pleroma.is_moderator`, `pleroma.is_admin`, `pleroma.confirmation_pending`, `pleroma.hide_followers`, `pleroma.hide_follows`, `pleroma.hide_favorites` fields to the User entity
Move settings to Source subentity
2019-04-25 02:14:35 -04:00
- Mastodon API: Add `pleroma.show_role`, `pleroma.no_rich_text` fields to the Source subentity
Fix leaking private configuration parameters in Mastodon and Twitter APIs, 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-24 13:01:42 -04:00
- Mastodon API: Add support for updating `no_rich_text`, `hide_followers`, `hide_follows`, `hide_favorites`, `show_role` in `PATCH /api/v1/update_credentials`
Add a changelog
2019-04-12 17:31:18 -04:00
- Mastodon API: Add `pleroma.is_seen` to the Notification entity
- Mastodon API: Add `pleroma.local` to the Status entity
- Mastodon API: Add `preview` parameter to `POST /api/v1/statuses`
- Mastodon API: Add `with_muted` parameter to timeline endpoints
- Mastodon API: Actual reblog hiding instead of a dummy
- Mastodon API: Remove attachment limit in the Status entity
differences_in_mastoapi_responses.md: fullname & bio are optionnal [ci skip]
2019-05-13 14:35:45 -04:00
- Mastodon API: Added support max_id & since_id for bookmark timeline endpoints.
Add a changelog
2019-04-12 17:31:18 -04:00
- Deps: Updated Cowboy to 2.6
- Deps: Updated Ecto to 3.0.7
Add the emoji packs & finmoji removal to the changelog
2019-04-20 08:17:21 -04:00
- Don't ship finmoji by default, they can be installed as an emoji pack
Update CHANGELOG
2019-05-14 07:40:21 -04:00
- Hide deactivated users and their statuses
Add a changelog
2019-04-12 17:31:18 -04:00
### Fixed
Search: Add fts index on objects table.
2019-05-03 13:15:55 -04:00
- Added an FTS index on objects. Running `vacuum analyze` and setting a larger `work_mem` is recommended.
Add a changelog
2019-04-12 17:31:18 -04:00
- Followers counter not being updated when a follower is blocked
- Deactivated users being able to request an access token
- Limit on request body in rich media/relme parsers being ignored resulting in a possible memory leak
Make rate limiting for Mastodon Registration API less agressive and enable it by default. As discussed on irc. Unlike Mastodon our web interface for registrations is using the same APIs regular apps would be using, so 5 requests per 30 minutes per IP could hurt valid use-cases when Pleroma-FE switches to it. Also enable the endpoint by default, it makes no sense to have it disabled when 1. TwitterAPI endpoint is there and always enabled 2. Unlike Mastodon, there is no way to get an account without using the APIs (makes me wonder why the setting is even there) Also in this commit: minor changelog improvements.
2019-05-14 15:47:23 -04:00
- Proper Twitter Card generation instead of a dummy
Merge branch 'develop' of https://git.pleroma.social/pleroma/pleroma into feature/845-improve-status-deletion
2019-05-06 12:45:22 -04:00
- Deletions failing for users with a large number of posts
Add a changelog
2019-04-12 17:31:18 -04:00
- NodeInfo: Include admins in `staffAccounts`
- ActivityPub: Crashing when requesting empty local user's outbox
- Federation: Handling of objects without `summary` property
- Federation: Add a language tag to activities as required by ActivityStreams 2.0
- Federation: Do not federate avatar/banner if set to default allowing other servers/clients to use their defaults
- Federation: Cope with missing or explicitly nulled address lists
- Federation: Explicitly ensure activities addressed to `as:Public` become addressed to the followers collection
- Federation: Better cope with actors which do not declare a followers collection and use `as:Public` with these semantics
update Changelog
2019-04-25 19:27:38 -04:00
- Federation: Follow requests from remote users who have been blocked will be automatically rejected if appropriate
Add a changelog
2019-04-12 17:31:18 -04:00
- MediaProxy: Parse name from content disposition headers even for non-whitelisted types
- MediaProxy: S3 link encoding
- Rich Media: Reject any data which cannot be explicitly encoded into JSON
Mention Mastodon 2.8+ follow import fix in changelog
2019-04-20 14:28:08 -04:00
- Pleroma API: Importing follows from Mastodon 2.8+
Fix leaking private configuration parameters in Mastodon and Twitter APIs, 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-24 13:01:42 -04:00
- Twitter API: Exposing default scope, `no_rich_text` of the user to anyone
- Twitter API: Returning the `role` object in user entity despite `show_role = false`
Add a changelog
2019-04-12 17:31:18 -04:00
- Mastodon API: `/api/v1/favourites` serving only public activities
- Mastodon API: Reblogs having `in_reply_to_id` - `null` even when they are replies
- Mastodon API: Streaming API broadcasting wrong activity id
- Mastodon API: 500 errors when requesting a card for a private conversation
Handle `reblogs` on the first follow request in MastoAPI
2019-04-19 01:35:05 -04:00
- Mastodon API: Handling of `reblogs` in `/api/v1/accounts/:id/follow`
Set correct values in the MastoAPI reblog status view
2019-04-15 13:32:14 -04:00
- Mastodon API: Correct `reblogged`, `favourited`, and `bookmarked` values in the reblog status JSON
Fix leaking private configuration parameters in Mastodon and Twitter APIs, 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-24 13:01:42 -04:00
- Mastodon API: Exposing default scope of the user to anyone
Make irreversible field default to false in filters
2019-05-13 14:05:33 -04:00
- Mastodon API: Make `irreversible` field default to `false` [`POST /api/v1/filters`]
Add a changelog
2019-04-12 17:31:18 -04:00
remove deprecated PleromaFE configuration
2019-05-14 13:52:08 -04:00
## Removed
- Configuration: `config :pleroma, :fe` in favor of the more flexible `config :pleroma, :frontend_configurations`
Add a changelog
2019-04-12 17:31:18 -04:00
## [0.9.9999] - 2019-04-05
### Security
Put an actual description of the vulnerability and add **Breaking:** to breaking changes
2019-04-13 14:17:10 -04:00
- Mastodon API: Fix content warnings skipping HTML sanitization
Add a changelog
2019-04-12 17:31:18 -04:00
## [0.9.999] - 2019-03-13
Frontend changes only.
### Added
- Added floating action button for posting status on mobile
### Changed
- Changed user-settings icon to a pencil
### Fixed
- Keyboard shortcuts activating when typing a message
- Gaps when scrolling down on a timeline after showing new
## [0.9.99] - 2019-03-08
### Changed
- Update the frontend to the 0.9.99 tag
### Fixed
- Sign the date header in federation to fix Mastodon federation.
## [0.9.9] - 2019-02-22
This is our first stable release.
Reference in New Issue Copy Permalink