* origin/develop: (330 commits)
Translated using Weblate (Chinese (Simplified))
Minor refactoring of the logic for hiding followers/following counts.
changelog
Fix for dropping posts/notifs in WS when mix task is executed
Fixed Rich Media Previews
Majic: specify commit so source users do not get surprise updates
Switch to a fork of Hackney 1.15.2 for now so we can have our URL normalization bugfix
instance.gen: Warn that stripping exif requires exiftool
instance.gen task: Only show files which will be actually overwritten
Translated using Weblate (Ukrainian)
Added translation using Weblate (Ukrainian)
Tweaks to OAuth entities expiration: changed default to 30 days, removed hardcoded values usage, fixed OAuthView (expires_in).
Changed default OAuth token expiration time to 30 days.
[#3112] .gitattributes fix.
Update CHANGELOG
ApplicationRequirements: Add test, more text for pool size.
Apply 1 suggestion(s) to 1 file(s)
Add a startup error for modified Repo pool_size
instance.reachable?: Limit to binary input
instance: Do not fetch unreachable instances
...
Current FedSocket implementation has a bunch of problems. It doesn't
have proper error handling (in case of an error the server just doesn't
respond until the connection is closed, while the client doesn't match
any error messages and just assumes there has been an error after 15s)
and the code is full of bad descisions (see: fetch registry which uses
uuids for no reason and waits for a response by recursively querying a
ets table until the value changes, or double JSON encoding).
Sometime ago I almost completed rewriting fedsockets from scrach to
adress these issues. However, while doing so, I realized that fedsockets
are just too overkill for what they were trying to accomplish, which is
reduce the overhead of federation by not signing every message.
This could be done without reimplementing failure states and endpoint
logic we already have with HTTP by, for example, using TLS cert auth,
or switching to a more performant signature algorithm. I opened
https://git.pleroma.social/pleroma/pleroma/-/issues/2262 for further
discussion on alternatives to fedsockets.
From discussions I had with other Pleroma developers it seems like they
would approve the descision to remove them as well,
therefore I am submitting this patch.
* origin/develop: (162 commits)
Improve Keyword descriptions for AdminFE
Fixed User.is_discoverable attribute rendering in Admin API User view.
@doc fix.
FrontStatic plug: excluded invalid url
phoenix_controller_render_duration is no longer available in telemetry of Phoenix 1.5+
ActivityPub: Add back debug call + explanation.
clients.md: Add AndStatus, note supported protocols
Fix link reference
NoNewPrivileges breaks ability to send email via sendmail because it restricts ability to run setuid/setgid binaries
Changelog: Add info about whitespace name remote users.
User: Correctly handle whitespace names.
Translated using Weblate (Chinese (Simplified))
[#3059] Used forked prometheus-phx to remove log spam.
[#3059] Formatting fix.
[#3059] Fixed Phoenix 1.5 telemetry processing.
Changelog: Add information about self-chats
SideEffects: Correctly handle chat messages sent to yourself
fix module name
update changelog
update docs
...
* origin/develop: (180 commits)
Deep link to the user account in AdminFE in account confirmation emails
Spelling
Ask user to use matching values for database setup
Syntax error
Don't always need to drop
Improve backup/restore documentation
Lint
Apply 1 suggestion(s) to 1 file(s)
Apply 1 suggestion(s) to 1 file(s)
Apply 2 suggestion(s) to 2 file(s)
Improve description yet again
Don't leak internal variables in the docs. They're useless to users.
Credo
Improve descriptions for reserved and proxies
Add test for an entry without CIDR format
Move hardcoded default configuration into config.exs
Fix docs for default headers used by RemoteIp. We only use X-Forwarded-For by default.
Document the NSFW link preview change
Add helper function to convert single IPs into CIDR format if they were not provided that way
Docs: Modify docs so the postgres config is harder to get wrong.
...
* origin/develop: (566 commits)
Fix MRF reject for ChatMessage
Create MRF.filter_pipeline to inject :object_data when present
KeywordPolicy: Still match when fields are absent
pleroma-fe bundle: bump to b225c3578f3c89af5ed3a0be3f8f3a6bbcedcc7d
CHANGELOG.md: Add 2.1.2 entry
mix.exs: bump version to 2.1.2
Merge branch '2130-mfa-users-oauth-login-fix' into 'develop'
Merge branch 'fix/streaming-termination-errors' into 'develop'
Merge branch 'fix/mrf-simple-welcome-chats' into 'develop'
Merge branch 'reply-visibility-user-guard' into 'develop'
Merge branch 'bugfix/mrf-ingestion' into 'develop'
adapt to new user factory behavior
add test and changelog entry
User search respect discoverable flag
Merge branch 'hotfix/rich-media-compile-error' into 'develop'
Merge branch 'feat/rich-media-head' into 'develop'
Deny ConfigDB migration when deprecated settings found
RichMedia: Fix log spam on failures and resetting TTL on cached errors
Return the file content for `GET /api/pleroma/admin/instance_document/:document_name`
add description to changelog
...
In practice, it was already removed half a year ago, but the description
and cheatsheet entries were still there.
The migration intentionally does not use ConfigDB.get_by_params, since
this will break migration code as soon as we add a new field is added
to ConfigDB.
Closes#2086
