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
e4b92584db
chore: imports, renamed future routes
2024-04-29 21:23:02 +02:00
35804730de
fix: temporarily don't set replies
...
we don't serve those routes yet
2024-04-29 21:02:41 +02:00
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
ab91a4c7bc
fix: your inbox contains posts by you
2024-04-26 13:48:57 +02:00
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
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
dfbadf5d11
fix: oops i meant server inbox GET, now it is
2024-04-23 06:29:52 +02:00
2bf4469270
feat: server timeline is object-based
2024-04-23 06:21:02 +02:00
1731bcb1c6
fix: remove again trailing slash
2024-04-23 05:31:19 +02:00
2cb6cfd2f1
fix: well-known nodeinfo base url
2024-04-23 05:29:26 +02:00
e316e1a840
fix: also change main key name for actor
2024-04-23 05:07:04 +02:00
867740b2e6
fix: actually hook up all outbox actions
2024-04-23 03:45:50 +02:00
8dece0f004
feat: implemented authed inbox
2024-04-22 22:52:05 +02:00
87a5a77e19
chore: imports
2024-04-22 02:52:18 +02:00
f2f7b51fdc
feat: order by publish date, not discovery
...
also centralized ordering inside select_* queries
2024-04-22 02:49:04 +02:00
b6f10e9cc1
fix: webfinger for application returns itself
2024-04-22 01:51:37 +02:00
dfec715594
chore: comments, clearer code
2024-04-22 01:01:42 +02:00
d575ef0bef
fix: add endpoints and preferred username to app
2024-04-22 00:37:21 +02:00
e8dd15f8bd
fix: also context gives full objects
...
would clear local cached image oof
2024-04-22 00:16:40 +02:00
96524dbd6f
fix: cheap fix for mastodon contexts
2024-04-22 00:01:09 +02:00
cc287d3aa4
feat: show attachments in inbox, outbox and /object
...
attachments are lazy loaded, so it may be efficient if not all posts
have media, but it should probably be eager loaded anyway eventually
2024-04-21 23:22:55 +02:00
624492bcfb
feat: introduced arbitrary fetch route for users
2024-04-21 19:15:47 +02:00
48bba8af40
feat: root url redirects browsers to /web
2024-04-21 19:01:51 +02:00
4e5e8f8532
fix: use WrappedObject type for context query
2024-04-21 17:11:50 +02:00
46a2e53da0
fix: use wrapped object since we ask for more cols
2024-04-21 16:14:47 +02:00
5d501a3018
fix: renamed methods
2024-04-21 15:42:15 +02:00
fa74c3dd0a
chore: imports
2024-04-20 04:34:47 +02:00
6c3aead68b
feat: handle announces
2024-04-20 04:33:23 +02:00
2d10f29b56
fix: restore federation, remove embedded follow___
...
it was so good, why make **just these** only links?????
2024-04-19 18:31:20 +02:00
b338a7191f
fix: jfc mastodon stop sending me deletions!!!!!!!
2024-04-19 16:15:05 +02:00
01d0e4df85
fix: context and replies and follow___ /page
2024-04-19 06:57:01 +02:00
bccf1f3a26
fix: ensure viewer has perms even for fetches
...
before, the first fetch would bypass addressing checks. now we always do
2 trips to db when viewing+fetching remote stuff: 1st to make sure we
have it, second to make sure we can view it
2024-04-19 05:26:51 +02:00
d7ff6014c4
fix: select_object doesnt return embeddedactivity
2024-04-19 05:05:26 +02:00
629990fee8
fix: find objects not activities
2024-04-19 04:57:06 +02:00
ab5d0cb61a
fix: replies only in object view, page uris
2024-04-19 04:42:43 +02:00
39add30876
chore: merge branch 'dev' of alemi.dev into dev
2024-04-19 03:32:56 +02:00
b3460690d9
feat: added /objects/.../replies collections
...
really not optimized, same with context, but may work?
2024-04-19 03:32:21 +02:00
b51f013138
feat: added context collections and endpoints
2024-04-19 03:29:28 +02:00
dfe116506a
chore: refactor
...
moved into models converters to ap objects, single conditions are now
direct column checks
2024-04-19 03:28:39 +02:00
fc6aedbca1
fix: track deletions and rejected activities
2024-04-18 14:01:55 +02:00
2073015b7f
feat: mock oauth login wellknown
...
looks like we will need oauth soon to be able to use even andstatus
2024-04-18 05:49:17 +02:00
f4252a2fbf
fix: insert addressings after fetching
...
also refactored fetcher into a trait of context
2024-04-18 05:25:56 +02:00
93b5c0cd4a
fix: only fetch remote objects to avoid recursion
2024-04-18 04:50:06 +02:00
3a79ca05a2
feat: local users can request to fetch remote stuff
2024-04-18 04:48:49 +02:00
5f8d8be05a
fix: show in_reply_to and statuses count
2024-04-18 04:14:16 +02:00
45a69f0332
feat: show following/followers counts for users
2024-04-18 03:06:56 +02:00
dab4550d08
fix: show outbox for remote users with url trick
2024-04-16 08:04:08 +02:00
3cf401467e
feat: login tells you who you are
2024-04-15 22:29:55 +02:00
ee26596568
feat: allow to resolve local views of remote things
...
basically any id prefixed with + will be:
* prefixed with 'https://'
* have all '@' replaced with '/'
* not be normalized with local domain patterns
thus allowing to look up kind of any url in our db
this is kinda reinventing the wheel, but i really don't want to have
local-only ids and would much rather have a local-only way to display
them, because at least everyone can understand it and look up anything
remote easily
2024-04-15 21:36:31 +02:00
