Age | Commit message (Collapse) | Author |
|
|
|
Merge upstream changes
|
|
Follow-up to e45a6edd6574c86409333cc64f9fb87e1b0a196e, fixes inconsistencies
in glitch-soc behavior.
|
|
|
|
Bumps [parallel_tests](https://github.com/grosser/parallel_tests) from 2.23.0 to 2.24.0.
- [Release notes](https://github.com/grosser/parallel_tests/releases)
- [Commits](https://github.com/grosser/parallel_tests/compare/v2.23.0...v2.24.0)
Signed-off-by: dependabot[bot] <support@dependabot.com>
|
|
|
|
Fix #9034
|
|
Reminder: Suggestions were added in #7918 and are based on who you
interact with who you do not follow. E.g. if you boost someone a lot
from seeing other people's boosts of that person, it makes sense you
might be interested in following the original source; or if you reply
to someone a lot, maybe you'd want to follow them
Each suggestion can be dismissed
|
|
Too many databases were lost to this
|
|
This reverts commit c7e9f9ff1ed1def7f14f6ca4ac2836005eeefa47.
|
|
Port 7861c5f108a8f8cb0450f3b1ef865b1177c706fc to glitch-soc
|
|
Port bebe8ec887ba67c51353e09d7758819b117bf62d to glitch-soc
|
|
Port c73864c1373330f2ef75006d639f90a1debcce6d to glitch-soc
|
|
Port 3a157210c87e6fe034f70d922cf7fc70fb533ad1 to glitch-soc
|
|
Port bf58461d365b5cee0d8a80a019a64e84c841f32f to glitch-soc
|
|
Port 25f9ead041a3087993059a1398f37dfa21a62610 to glitch-soc
|
|
Port 029943d59b222e96a2f7839390a5628888249bf6 to glitch-soc
|
|
Port 065b39e7a460e088fd5afcd48dfc425d0006fee9 to glitch-soc
|
|
Port 301cbcc9802ed85c519e67a01133968bc074c8af to glitch-soc
|
|
Port 65b3804a6ccd40d359616b6157682ff88f85462f to glitch-soc
|
|
Port d35801aaa2ad9d06345efa45cf524113469fdd02 to glitch-soc
|
|
Port f8c1b325410369806eb77a5c8d259971a87a6852 to glitch-soc
|
|
Port efd09e2ebba7e9f0135bd47c44a77e2fc421aa67 to glitch-soc
|
|
Port b972478812316da2f5c0d24c60386d408e027424 to glitch-soc
|
|
Revert server-side part of 87fdd139b890e60f752bf71e3b09d79eaefcf7b5
|
|
Conflicts:
- .github/ISSUE_TEMPLATE/bug_report.md
Took our version.
- CONTRIBUTING.md
Updated the embedded copy of upstream's version.
- README.md
Took our version.
- app/policies/status_policy.rb
Not a real conflict, took code from both.
- app/views/layouts/embedded.html.haml
Added upstream's changes (dns-prefetch) and fixed
`%body.embed`
- app/views/settings/preferences/show.html.haml
Reverted some of upstream changes, as we have a
page dedicated for flavours and skins.
- config/initializers/content_security_policy.rb
Kept our version of the CSP.
- config/initializers/doorkeeper.rb
Not a real conflict, took code from both.
|
|
Fix #8889
|
|
Fix #8741
|
|
* RTL: remove blank character inside bdi
* Update app/javascript/mastodon/components/display_name.js
Co-Authored-By: mabkenar <ampbox@gmail.com>
|
|
* Delete first 9 accounts on dead servers
* Clean up code by moving dead server culling to the end
|
|
Fixes #9045
|
|
|
|
* RTL: fix admin account avatar margin in about page
* fix code style
|
|
|
|
|
|
This uses the same logic as the status icons in the glitch flavor.
|
|
Fixes #395
Instead of leaving the toot body blank, it replaces it with a single “.” in
order for the fold/unfold CW behavior to not look *too* weird on upstream
Mastodon. Note that this does not fix upstream's CW-dropping behavior, as
that is decided at the time the toot is posted, not received.
|
|
|
|
|
|
|
|
* Fix position of the domain label
* Fix position of the domain label for RTL
- Fix color mismatch of linear gradient which assigned to "::after" pseudo class
|
|
* Bump version to 2.6.0rc1
* Update AUTHORS.md
* Update CHANGELOG.md
|
|
and use 'if' option of context block
|
|
Indeed, when the “Always enable the Content Warning field” setting is enabled,
sending a content-less toot with a CW would move the CW to the toot's content
and leave the toot not marked as sensitive.
|
|
|
|
|
|
* Do not test PAM authentication by default
* Disable PAM tests if PAM is not enabled
|
|
* Add "disable" button to report screen
* i18n-tasks remove-unused
|
|
Previously, the server would attempt taking port/socket in worker
process, and if it was taken, fail, which made the master process
create a new worker. This led to really high CPU usage if the
streaming API was started when the port or socket were not
available.
Now, before clustering (forking) into worker processes, a test
server is created and then removed to check if it can be done.
|
|
|