This setting is unnecessary because DeepL free keys can be detected
easily according to <https://www.deepl.com/docs-api/api-access/authentication/>:
> DeepL API Free authentication keys can be identified easily by the suffix ":fx"
Changelog: Removed
Some distros might not have the latest 18.x minor version in their repos, so lower it to one that's reasonably expected to be available on most distros that ship Node 18.
There are now separate web and queue workers.
The configuration entry `clusterLimit` has been replaced by
`clusterLimits` which allows separate configuration of web and
queue workers.
Changelog: Changed
Now that Node 18 is the new LTS version of Node, it should be safe to
support ES2022 features. The install docs have already been updated to
recommend Node 18.x in 41a710854e.
This will break support on Node 16.x and earlier.
Also update TypeScript to 4.9 which contains various typechecking
improvements: https://devblogs.microsoft.com/typescript/announcing-typescript-4-9/
Ref: FoundKeyGang/FoundKey#238
Changelog: Changed
The thing that previously presumably hindered this was that the VAPID
keys had to be set up. Previously admins had to do this, but this is a bad
idea for multiple reasons:
1) The meaning of "public key" and "private key" was not well documented
in the settings.
2) Giving out a private key over the API, even just for admins, sounds
like a bad idea.
Co-authored-by: Francis Dinh <normandy@biribiri.dev>
* Fixed association between dropEffect and effectAllowed as well as the submission form
* Fixed that strings can be dropped
Reviewed-on: https://github.com/misskey-dev/misskey/pull/9114
Changelog: Fixed
Since the move to Yarn workspaces in
10caf861e8, the package.json scripts rely
on Yarn being available to function properly due to the use of
workspaces.
Because of this, Yarn has basically been required to be able to properly
set up and run FoundKey. Using `npx yarn` probably won't work anymore
with modern yarn versions.
This adds a new "Translation Settings" page to the admin interface where
the admin can configure the instance's translation settings. The
existing settigns for DeepL translation settings will now be located in
that page alongside the new LibreTranslate stuff.
Also made the translation service settings localizable, which funnily
enough was not already the case.