1032 commits

Author	SHA1	Message	Date
Johann150	2fde652b4a	server: fix drive quota for remote users ... This deletes as many files as necessary to ensure the drive quota for remote users is kept. Previously only one file would have been deleted for each file added. Changelog: Fixed Co-authored-by: CGsama <CGsama@outlook.com> Co-authored-by: tamaina <tamaina@hotmail.co.jp>	2023-05-23 21:36:35 +02:00
Johann150	efa8305e0b	BREAKING rename environment variables from MK_... to FK_... ... Changelog: Changed	2023-05-23 19:49:55 +02:00
Johann150	e6a8173378	refactor onlyQueue and onlyServer configuration ... Instead of checking this configuration in the respective component (queue) or not at all (server), the configuration can be checked when starting the respective workers.	2023-05-23 19:49:55 +02:00
Johann150	239a52eb99	add "quiet" log level ... This log level replaces the "MK_QUIET" environment variable to unify the interface in a sensible way. This also removes the "MK_VERBOSE" environment variable which was unused.	2023-05-23 19:49:55 +02:00
Johann150	38c2d86983	add log level environment variable ... To avoid a circular dependency this requires moving the log level definitions. Also to avoid a circular dependency the env.ts file cannot use a logger and instead uses plain `console.log`.	2023-05-23 19:49:55 +02:00
Ignas Kiela	6b9a3259f5	fix: log levels order ... Most important messages are the ones with the highest value This is a fixup for commit c5327f74d4.	2023-05-23 18:12:48 +02:00
Ignas Kiela	296c40c5b4	fix: stop sending pings on every pong ... This resulted in endless ping-pong traffic on the websocket, happening every interval of network latency to the server (e.g. for me, with 40ms latency to my server, it was about every 40ms). On my server this ended up taking about 20% of foundkey's CPU usage. Now, just send pings every 30s, and check if we have received any pong's in last 60 seconds to check that the connection is still alive. Changelog: Fixed	2023-05-23 18:08:08 +02:00
Johann150	fe65cba9be	add "nobody" follower visibility ... Adds a new follower/following visibility that hides followers even from yourself. Changelog: Added	2023-05-20 23:18:57 +02:00
Johann150	ef4055840b	BREAKING server: respect ffVisibility on stats endpoint ... This makes the returned values `localFollowingCount`, `remoteFollowingCount`, `followingCount`, `localFollowersCount`, `remotefollowersCount`, `followersCount` optional on the API endpoint `users/stats`. Changelog: Fixed	2023-05-20 23:18:57 +02:00
Johann150	ded48c96d8	server: use foundkey-js definition of ffVisibilities	2023-05-20 23:18:56 +02:00
Johann150	ed9f2f4900	server: refactor ffVisibility checks into function	2023-05-20 23:18:56 +02:00
Johann150	ff66f48ea2	remove syslog ... closes #19 Changelog: Removed	2023-05-19 23:15:24 +02:00
Johann150	2c3f731ae2	remove more default exports	2023-05-19 23:08:06 +02:00
Johann150	b0d8e15796	fixup: remove some default exports ... This is a fixup for commit 410c519953.	2023-05-19 20:07:26 +02:00
Johann150	410c519953	remove some default exports	2023-05-19 00:32:11 +02:00
Johann150	d6452795b0	translate more comments	2023-05-19 00:21:47 +02:00
Johann150	85a392ee33	logger: remove unused structured data ... The `data` field is not used anywhere in the logger. While it would be possible to send structured data through syslog, it seems unnecessary at present and also the way in which this structured data would have to be provided sounds too cumbersome to implement for no real value.	2023-05-18 22:42:30 +02:00
Johann150	c5327f74d4	refactor to check log levels ... This will eventually allow the log level to be configured. For now, the explicit debug flag does not work.	2023-05-18 21:41:32 +02:00
Johann150	1516ddfc9b	refactor: remove CacheableUser & co ... The CacheableUser, CacheableLocalUser and CacheableRemoteUser are identical types to User, ILocalUser and IRemoteUser so it seems nonsensical to have different types for them.	2023-05-18 13:25:57 +02:00
Johann150	9675ced915	translate japanese comment	2023-05-18 02:08:07 +02:00
Johann150	c53486a47c	try to fix tests	2023-05-15 20:14:51 +02:00
Johann150	386d1bbf74	fix: update meta cache between workers	2023-05-12 19:34:08 +02:00
Johann150	e6c7f4b693	refactor: use switch for receiving IPC messages	2023-05-12 19:18:17 +02:00
Johann150	ac81acfe9d	tests: disable timeouts for server setup	2023-05-08 00:07:40 +02:00
Johann150	5a4e300552	tests: fix visibility tests ... removed a duplicate test and fixed another that i messed up when updating tests for the changed visibility	2023-05-07 23:38:29 +02:00
Johann150	d8c2cc2ef0	tests: translate some japanese to english	2023-05-07 23:37:47 +02:00
Johann150	3d4df807b0	tests: refactor ffVisibility tests ... Using some closures to partly generate the tests to achieve better coverage	2023-05-07 23:35:29 +02:00
Johann150	352851f23f	tests: fix error codes and HTTP statuses	2023-05-07 23:34:34 +02:00
Johann150	eecff514c2	tests: use bearer authentication	2023-05-07 23:33:21 +02:00
Johann150	605a55e1d4	tests: fix Resolver import	2023-05-07 23:32:23 +02:00
Johann150	683584fe8f	update mocha	2023-05-07 23:29:55 +02:00
Johann150	34d55e2dda	server: better matching for MFM mentions ... 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	2023-04-28 23:47:48 +02:00
Johann150	9b8438cdfc	server: system accounts cannot be registered ... 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.	2023-04-20 22:10:31 +02:00
Johann150	688deda218	server: dont fail if system user exists ... closes #378 Changelog: Fixed	2023-04-20 22:05:26 +02:00
Johann150	4fbbfff145	activitypub: also check incoming activity host for block	2023-04-16 19:34:15 +02:00
Johann150	5f4aab6d46	translate yet another japanese comment	2023-04-16 19:33:50 +02:00
Johann150	75fd42b070	server: check for valid keyId URL before parse	2023-04-16 19:33:28 +02:00
Johann150	f7bd210316	server: replace Array.find with Array.some	2023-04-16 13:32:36 +02:00
Johann150	ba2b7ef43c	fix including suspended users in getter	2023-04-15 21:10:57 +02:00
Johann150	9a085e9d42	fixup: add missing curly braces ... This is a fixup for commit b14f3e8cdc.	2023-04-15 20:27:42 +02:00
Johann150	b14f3e8cdc	server: properly handle logical deletion ... closes #329	2023-04-15 19:04:07 +02:00
Johann150	71dfd229b0	remove unnecessary code	2023-04-15 18:56:46 +02:00
Johann150	7b8333a21f	server: refactor user getter to throw API error ... 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.	2023-04-15 18:56:42 +02:00
Johann150	ae703cfe4b	server: check that channel id is specified	2023-04-15 18:14:57 +02:00
Johann150	8c47f376dc	server: fix undefined variable in streaming API	2023-04-15 17:52:48 +02:00
Johann150	808ad2a505	server: HTTP signature requires date header ... 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.	2023-04-13 11:04:35 +02:00
Johann150	340874c252	BREAKING server: remove mediaIds parameter ... 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	2023-04-10 15:07:44 +02:00
Johann150	079a9e29ce	server: replace IRC with issue tracker as preferred feedback ... The IRC channel is not a reliable means of communication for feedback because I don't use it (regularly).	2023-04-01 15:10:12 +02:00
Johann150	1472c21cb6	activitypub: properly handle all scopes for renotes ... This was not implemented because of concerns raised in https://github.com/misskey-dev/misskey/issues/8261 about Mastodon incorrectly interpreting the scope on renotes. However this bug seems to be fixed so it can now be implemented. See also https://github.com/misskey-dev/misskey/pull/10291 Co-authored-by: Kagami Sascha Rosylight <saschanaz@outlook.com>	2023-03-31 07:59:20 +02:00
Johann150	e9f68e65b7	server: fix rate limit for adding reactions ... 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	2023-03-28 22:50:04 +02:00