The distinction for "DetailedInstanceMetadata" does no longer exist
since commit 9022ab9f2a.
The `DetailedInstanceMetadata` and `LiteInstanceMetadata` have
therefore been removed, leaving only `InstanceMetadata`.
Changelog: Removed
Currently translated at 96.1% (1161 of 1208 strings)
Translated using Weblate (Russian)
Currently translated at 90.5% (1094 of 1208 strings)
Co-authored-by: ogur4ik <abrew1330@gmail.com>
Translate-URL: http://translate.akkoma.dev/projects/foundkey/foundkey/ru/
Translation: Foundkey/foundkey
When rendering the HTML for outgoing activities, the mentions are now
matched case insensitive and should also work properly for IDNs. The
username is also compared case insensitive. Mentions of local users
are also handled properly independed of whether the hostname was given
or omitted.
The query to get mentions is now also only executed once instead of
for each mention individually.
Changelog: Fixed
Currently translated at 99.8% (1206 of 1208 strings)
Co-authored-by: kazari <6c577a54-aac9-482a-955e-745c858445e3@simplelogin.com>
Translate-URL: http://translate.akkoma.dev/projects/foundkey/foundkey/ja/
Translation: Foundkey/foundkey
Currently translated at 99.8% (1206 of 1208 strings)
Co-authored-by: kazari <6c577a54-aac9-482a-955e-745c858445e3@simplelogin.com>
Translate-URL: http://translate.akkoma.dev/projects/foundkey/foundkey/ja/
Translation: Foundkey/foundkey
Currently translated at 100.0% (1208 of 1208 strings)
Translated using Weblate (Polish)
Currently translated at 100.0% (1205 of 1205 strings)
Co-authored-by: Jeder <jeder@jeder.pl>
Translate-URL: http://translate.akkoma.dev/projects/foundkey/foundkey/pl/
Translation: Foundkey/foundkey
While refactoring the previous commit, it seemed like the previous
authors expected that a system account could be registered somehow
and that this would be an error condition. However, as now made
explicit with this, it is not possible to register a system account.
This means that any account by that name could only ever have been
created by the system itself so fetching them should be fine and not
an error condition.
Instead of throwing an IdentifiableError which then just always gets
converted into an ApiError, the getter can just throw the same ApiError
directly. This makes it more convenient to use and thus more endpoints
have been refactored to use it to reduce code repetition.
Currently translated at 99.6% (1201 of 1205 strings)
Co-authored-by: kazari <6c577a54-aac9-482a-955e-745c858445e3@simplelogin.com>
Translate-URL: http://translate.akkoma.dev/projects/foundkey/foundkey/ja/
Translation: Foundkey/foundkey
Currently translated at 100.0% (1205 of 1205 strings)
Translated using Weblate (German)
Currently translated at 100.0% (1203 of 1203 strings)
Co-authored-by: Johann <johann@qwertqwefsday.eu>
Co-authored-by: Johann150 <johann.galle@protonmail.com>
Translate-URL: http://translate.akkoma.dev/projects/foundkey/foundkey/de/
Translation: Foundkey/foundkey
Currently translated at 99.8% (1201 of 1203 strings)
Translated using Weblate (Japanese)
Currently translated at 99.6% (1199 of 1203 strings)
Translated using Weblate (Japanese)
Currently translated at 97.5% (1174 of 1203 strings)
Co-authored-by: digny <newymroo@tutamail.com>
Translate-URL: http://translate.akkoma.dev/projects/foundkey/foundkey/ja/
Translation: Foundkey/foundkey
Currently translated at 100.0% (1203 of 1203 strings)
Translated using Weblate (German)
Currently translated at 99.7% (1201 of 1204 strings)
Co-authored-by: Johann <johann@qwertqwefsday.eu>
Co-authored-by: Johann150 <johann.galle@protonmail.com>
Translate-URL: http://translate.akkoma.dev/projects/foundkey/foundkey/de/
Translation: Foundkey/foundkey
Currently translated at 93.4% (1124 of 1203 strings)
Translated using Weblate (Spanish)
Currently translated at 93.2% (1123 of 1204 strings)
Translated using Weblate (Spanish)
Currently translated at 92.9% (1119 of 1204 strings)
Co-authored-by: Kimberly <kimisaes@gmail.com>
Translate-URL: http://translate.akkoma.dev/projects/foundkey/foundkey/es/
Translation: Foundkey/foundkey
Currently translated at 100.0% (1205 of 1205 strings)
Translated using Weblate (Polish)
Currently translated at 100.0% (1205 of 1205 strings)
Translated using Weblate (Polish)
Currently translated at 100.0% (1200 of 1200 strings)
Co-authored-by: Jeder <jeder@jeder.pl>
Translate-URL: http://translate.akkoma.dev/projects/foundkey/foundkey/pl/
Translation: Foundkey/foundkey
Currently translated at 99.6% (1201 of 1205 strings)
Translated using Weblate (Japanese)
Currently translated at 99.8% (1201 of 1203 strings)
Translated using Weblate (Japanese)
Currently translated at 99.6% (1199 of 1203 strings)
Translated using Weblate (Japanese)
Currently translated at 97.5% (1174 of 1203 strings)
Translated using Weblate (Japanese)
Currently translated at 97.0% (1167 of 1203 strings)
Translated using Weblate (Japanese)
Currently translated at 96.6% (1163 of 1203 strings)
Translated using Weblate (Japanese)
Currently translated at 95.5% (1150 of 1204 strings)
Translated using Weblate (Japanese)
Currently translated at 94.7% (1137 of 1200 strings)
Co-authored-by: kazari <6c577a54-aac9-482a-955e-745c858445e3@simplelogin.com>
Translate-URL: http://translate.akkoma.dev/projects/foundkey/foundkey/ja/
Translation: Foundkey/foundkey
The default of the library used is to require either of the "date" or
"x-date" headers. It does not seem sensible to pass on this default.
It may be to fix federation with another software but that software
should be considered broken, and it does not seem reasonable to
potentially get an outdated signature just to fix federation with some
buggy software.
This parameter is a duplicate of fileIds and was marked as deprecated
before. This removes that parameter and therefore simplifies the API
endpoint's schema.
Changelog: Removed
The issue was that the detection in the drive component did not see the
contents of `paginationElem.items` because the ref was not properly
exposed. The value of the exposed property was a Proxy of an empty
array that was not a reference to the actual items array. Thus, when
checking if the item already exists or not, it never saw the item and
added it as if new.
closes #367
closes #368
Changelog: Fixed
Adding a reaction may delete a previous reaction to the same note,
thus consequently this needs to be in the rate limiting group if this
happens. Otherwise the rate limit can be circumvented.
Changelog: Fixed
