379 commits

Author	SHA1	Message	Date
alemi	84a446b494	fix: answer deletions with 200	2024-05-01 18:43:43 +02:00
alemi	bb4f6e9df0	fix: show follow/by for remote users too ... this is super ugly because there's a ton of duplication but let's see if it works first...	2024-05-01 18:37:26 +02:00
alemi	4527ff884e	feat: show in user queries if follow/by self	2024-05-01 17:47:37 +02:00
alemi	75d03195d9	feat: allow checking if identity is someone	2024-05-01 17:47:21 +02:00
alemi	e8b36cecdf	chore: should move this later	2024-04-30 16:51:30 +02:00
alemi	f2dc3f69f2	chore: refactor, moved cli tasks under directory	2024-04-30 16:48:28 +02:00
alemi	b0ebeb9fff	fix: mastodont sized	2024-04-30 16:48:00 +02:00
alemi	6f033de946	fix: try fetching following/followers, dont fail	2024-04-30 16:47:34 +02:00
alemi	938d219d7d	fix: whoops other way around	2024-04-30 15:33:41 +02:00
alemi	a6c3ef9a3e	feat: increment statuses count ... be it when posting, receiving a Create or fetching an object, increment relevant user statuses count	2024-04-30 14:22:44 +02:00
alemi	a966f7fcb5	fix: fetch remote users following/followers count	2024-04-30 14:17:29 +02:00
alemi	0bfa49fed6	chore: imports	2024-04-30 04:29:03 +02:00
alemi	3237a38d74	fix: insert liked element also in single obj view	2024-04-30 02:57:50 +02:00
alemi	8af2cd2664	fix: maybe don't filter whole queries	2024-04-30 02:05:28 +02:00
alemi	a4cdd2e67b	feat: show followers, following, statuses in users	2024-04-30 01:51:38 +02:00
alemi	45d16fa0a3	feat: query and show objects liked by you ... it shows it in quite a jank way: inside the "audience" collections you find your id as only item. it's weird af but technically valid ap i think? will probably be replaced with a local api extension as soon as i read about those	2024-04-30 01:50:25 +02:00
alemi	63ba54dad9	fix: activity redirects when fetching different id	2024-04-30 01:49:05 +02:00
alemi	3df01b5b0a	chore: helper to reconstruct ids	2024-04-30 01:48:30 +02:00
alemi	f0cdd4bd7a	feat: like and share relations with object	2024-04-30 00:53:57 +02:00
alemi	97ed5d60b1	feat: show users following/followers ... use audience for followers, generator for following and replies for total statuses count. restored followers, following and outbox as bare links. silly AP!!!	2024-04-30 00:53:07 +02:00
alemi	5bdf139ef5	chore: imports	2024-04-29 22:02:18 +02:00
alemi	7f996aa2c1	feat: kinda botched way to ignore relays ... basically relays send us a lot of announce activities to share posts but we don't care about those activities: it's db bloat and it increases the shares count. keep a table keeping track of followed relays and lazily skip activities by them, just fetch. IMPORTANT relays are only loaded at startup, so if you subscribe to a new relay restart your server once it accepts!!!	2024-04-29 21:58:08 +02:00
alemi	a6e12468b7	fix: db fix tasks would get stuck on sqlite ... i think because the db would end up locked, added brackets to be sure to drop the streaming reference. also it could crash when updating records not found, just spit a warn	2024-04-29 21:23:12 +02:00
alemi	e4b92584db	chore: imports, renamed future routes	2024-04-29 21:23:02 +02:00
alemi	3e0e4ff8d3	fix: also update comments count when fetching	2024-04-29 21:22:48 +02:00
alemi	35804730de	fix: temporarily don't set replies ... we don't serve those routes yet	2024-04-29 21:02:41 +02:00
alemi	3129970fb5	feat: added fix task to recalculate stats ... note that won't reset everything to 0, just force set every post which has a count != 0 also this is kind of a bad way to do it. at least we stream objects, but we could have it happen all inside our db with SELECT, DISTINCT and SUM, i just don't know how to represent it in sea_orm. an intermediate optimization may be selecting only certain columns but it's relevant almost only for replies	2024-04-29 20:53:19 +02:00
alemi	4fe53f7011	fix: increment share and like counters for outbox	2024-04-29 20:40:20 +02:00
alemi	5ae9a140b4	feat: show likes and shares and replies in objects ... it's done with anonymous inline collections, which hold a "totalItems" field. for replies it's perfect, for likes it's stretched ("audience", used as a Collection) and for shares it's really stretched ("generator", used as a Collection). also using audience and generator as collections seems weird because they should be objects but collections are objects so it should be fine? i haven't seen these fields used anyway so it should be safe to "claim" it for ourselves?	2024-04-29 20:30:29 +02:00
alemi	95f9d05875	fix: redirect after fetching if id is different ... for example, pleroma servers objects under /notice/abcd... but the object id itself is different, under /objects/<uuid>. when fetching pleroma redirects, but we get unreliable behavior. redirect so that we can force clients to use the proper id	2024-04-29 20:11:19 +02:00
alemi	ab91a4c7bc	fix: your inbox contains posts by you	2024-04-26 13:48:57 +02:00
alemi	ed0a4fd211	fix: always forget about this...	2024-04-24 05:21:04 +02:00
alemi	3156b8d2d2	feat: sensitive field ... this is not part of activitystreams afaik and should not be in apub but it's quite convenient to do it this way sooooooooooo for now will do	2024-04-24 05:19:39 +02:00
alemi	abf4e8b370	fix: always embed specific activities	2024-04-24 05:04:30 +02:00
alemi	2ba96e802e	fix: show own activities/objects	2024-04-24 04:08:07 +02:00
alemi	768081c251	fix: big refactor of timelines querying ... should not be more reliable, consistent and all around less buggy, but it may actually break some things so let's find out	2024-04-24 02:32:23 +02:00
alemi	165bf19f8c	feat: don't add next link when done paginating	2024-04-23 23:37:57 +02:00
alemi	ba07b2cb9d	fix(apb): correct node order when iterating ... use a VecDeque under the hood to be able to pop_front()	2024-04-23 20:58:37 +02:00
alemi	4b4d52ef6f	feat: fetch related things ... fetching an object will get its author fetching an activity will get its object and author	2024-04-23 17:56:46 +02:00
alemi	597dee934d	fix: try hiding locked activities for public objs ... idk if this works but basically when there's a public object from a private activity, the query joins the activity anyway because it uses the object relation, try using the addressing relation and see what comes out	2024-04-23 17:21:32 +02:00
alemi	8a6c05f4fb	fix: relay follow/accept are public	2024-04-23 16:54:03 +02:00
alemi	2a9cf5bcf5	feat: command to also accept relay follow reqs ... this has quite awful UX because you can't really know if relay is following back without checking logs, but whatevvvv works for now	2024-04-23 16:26:19 +02:00
alemi	dfbadf5d11	fix: oops i meant server inbox GET, now it is	2024-04-23 06:29:52 +02:00
alemi	2bf4469270	feat: server timeline is object-based	2024-04-23 06:21:02 +02:00
alemi	70920985cf	fix: use hs2019 instead of rsa-sha256 ... im not sure why but apparently there's some bug somewhere? maybe some instances are picky and want the new thing? should still be fine using sha256 as signing tho	2024-04-23 05:46:48 +02:00
alemi	1731bcb1c6	fix: remove again trailing slash	2024-04-23 05:31:19 +02:00
alemi	2cb6cfd2f1	fix: well-known nodeinfo base url	2024-04-23 05:29:26 +02:00
alemi	8b88d24250	fix: show signature when invalid	2024-04-23 05:19:24 +02:00
alemi	e316e1a840	fix: also change main key name for actor	2024-04-23 05:07:04 +02:00
alemi	4f8132a642	fix: dispatcher check doesn't include trailing	2024-04-23 05:01:59 +02:00