Age | Commit message (Collapse) | Author |
|
other media descriptions
Port c761e7a5ef89afd4ed7ac470ad1155a78d3c4cfa to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port 7fbc17afa246c5cd384123ace51e07622204b67c to glitch-soc
Co-authored-by: Effy Elden <effy@effy.space>
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port ebf1d74e409ece10864a8615691cd80c434c9055 to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port 726c7dea31d2ee60b327afd327e945e3ece09ac4 to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port ff414a5489fd2c6d154b18effca24dde54d92958 to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port cedf1383138b2e58ba6ff9aab46beddeaf1a1354 to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port 059d64a59ea27c40ca6b5b9bf34487169d2a741f to glitch-soc
Co-authored-by: meisam <meisam@noreply.codeberg.org>
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port 38596e49d4ea00b9a538f32fd443afc6aa29824a to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port 72a8af80886f270a27bd686f1fa86ef478748963 to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port 08c0e43b6fca879d7435f63b1b2c718a53c6cacc to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port c50e9d078aa3c353afc140669f1cedcd354ee53e to glitch-soc
Co-authored-by: Effy Elden <effy@effy.space>
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port 58200132d07bc0b641c95af614b9ac02ce48c9fc to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port 3a59ffde8d1600729bf51ff42f1d646062edfc8d to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port 903e5a3f459d28b093438dc4827b2fb976aef406 to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port c3388f4ab151a2603fabd67dadea435f851eaf12 to glitch-soc
Co-authored-by: Riedler <riedler@gelse.eu>
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
non-public posts
Port fe9eab51d140ee0e0343eb07982f0a7ce825398c to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
Port 1f762f4271685e30373b15a2e204f8edff59d349 to glitch-soc
Signed-off-by: Claire <claire.github-309c@sitedethib.com>
|
|
|
|
Conflicts:
- `README.md`:
Discarded upstream changes: we have our own README
- `app/controllers/follower_accounts_controller.rb`:
Port upstream's minor refactoring
|
|
|
|
|
|
|
|
|
|
* Add requested_by to relationship maps
* Display whether an account has requested to follow you on their profile
|
|
Co-authored-by: Effy Elden <effy@effy.space>
|
|
descriptions (#20923)
|
|
standard (#21262)
* Add sme, smj, and sma ISO-639-3 language codes
* Remove sme in ISO-639-3
|
|
Firstly, mailgun.com is now their domain. Secondly they are lots of providers to use; and sysadmins should be able to choose.
|
|
Fixes #17494
|
|
This brings the markup of the MediaItem component on par with the Item component from media_gallery.
Co-authored-by: Effy Elden <effy@effy.space>
|
|
* Update config.yml
* Update config.yml
|
|
|
|
There is an idempotency key generated by clients when authoring a post,
and stored in Redis, to ensure that if a user or client retries posting
the same status, we don't get a duplicate.
Hachyderm.io has been experiencing some filesystem and database
performance issues, causing database writes to be slow. This can mean
that there are successful posts, but the reverse proxy returns 504
Gateway Timeout before the idempotency status has been updated; users or
clients who retry (such as Tusky which retries automatically, see
tuskyapp/Tusky#2951) can re-try the same post with the same idempotency
key before it has actually been recorded in Redis, leading to duplicate
posts.
To address this issue, move all of the database updates after the
initial transaction that creates the status into the
`postprocess_status!` method, so we can insert the idempotency key
immediately after the status has been created, significantly reducing
the window in which the status could be created but the idempotency key
not yet stored.
Note: this has not yet been tested; I'm submitting this PR for
discussion and to offer to the Hachyderm.io admins to try out to fix the
multiple posting problem.
Co-authored-by: Brian Campbell <brcampbell@beta.team>
|
|
|
|
(#22135)
* Fix changing domain block severity not undoing individual account effects
Fixes #22133
* Add tests
|
|
* Update nvmrc to Node.js 16
* Update package.json minimum Node engine to 16
* Update README requirements to Node.js 16
* Update devcontainer Node.js version to 16
* Update devcontainer Dockerfile Node.js choices to LTS versions that are still in support/maintenance
* Pin CircleCI Node image to 16
* Fix YAML type issue
* Update CircleCI Node.js to 16.18 to match #22019
|
|
Fixes #22241
|
|
* Improve devcontainer for running tests
- Pull devcontainer post-create out into its own script
- Add asset precompilation
- Add test-mode asset precompilation (needed to run tests without error)
* Document Gemfile.lock re-checkout in devcontainer
|
|
* Display search popout at fixed screen position
* Attach search popout to search box
|
|
Fixes #18080
This keeps the `ui-base-lighter-color` but adds enough transparency so that text is more easily readable.
Tested in Firefox and Chrome.
|
|
When opening a page such as /web/timelines/home in a desktop browser, the
cursor was automatically placed in the textarea of the compose form.
When using the keyboard for navigation (using a browser plugin like vimium or
vim vixen, or just to hit 'space' to scroll down a page), you have remember to
leave the field before using that.
Since you only visit the page to write a new post some of the time, this PR
attempts to have nothing focused initially (and require the user to click or
e.g. use 'tab' to focus the textarea).
Tested:
* /web/timeslines/home no longer autofocuses the compose box
* pressing the 'n' hotkey still focuses the compose box
* clicking 'reply' for a post still focuses the compose box
* replying to a CW'ed post still focuses the compose box
* introducing the CW field still focuses the CW field
* introducing the CW field for a reply still focuses the CW field
* removing the CW field still focuses the compose box
* /web/statuses/new still autofocuses the compose box
fixes #15862
|
|
|
|
|
|
Co-authored-by: petrokoriakin1 <116151189+petrokoriakin1@users.noreply.github.com>
Co-authored-by: petrokoriakin1 <116151189+petrokoriakin1@users.noreply.github.com>
Co-authored-by: Effy Elden <effy@effy.space>
|
|
* Save avatar or header correctly if other one fails
* Fix test
|
|
|
|
|
|
|
|
Co-authored-by: meisam <meisam@noreply.codeberg.org>
|
|
ALLOWED_PRIVATE_ADDRESSES (#21926)
Fixes #20029
|