Retain standard nodeinfo about instances #225

Closed
opened 2022-09-20 14:23:22 +00:00 by floatingghost · 3 comments

Ref AkkomaGang/pleroma-fe#146

to do this, and also to do things like capability testing (can we react to this post?), we'll need to pull nodeinfo about instances, maybe once every few days?

just have a trigger on inbound AP which dispatches an oban job that checks if it should pull info

Ref https://akkoma.dev/AkkomaGang/pleroma-fe/issues/146 to do this, and also to do things like capability testing (can we react to this post?), we'll need to pull nodeinfo about instances, maybe once every few days? just have a trigger on inbound AP which dispatches an oban job that checks if it should pull info
Contributor

Wort noting, Pleroma started storing nodeinfo metadata in the DB with this MR.
If the same schema fits us, porting this would make things easier for migrations. If it doesn’t fit, avoiding the same table name as Pleroma might be a good idea to at least not introduce migration conflicts.

Wort noting, Pleroma started storing nodeinfo metadata in the DB with [this MR](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3853). If the same schema fits us, porting this would make things easier for migrations. If it doesn’t fit, avoiding the same table name as Pleroma might be a good idea to at least not introduce migration conflicts.
Author
Owner

oh idk why this issue is still open

I implemented this way back b7e8ce2350

oh idk why this issue is still open I implemented this way back https://akkoma.dev/AkkomaGang/akkoma/commit/b7e8ce235073ab45db24dfc6c27bc6998b43a200
Contributor

heh, the actual data keys have different names, but the metadata_updated_at overlaps but using :naive_datetime here but when Pleroma also implemented this it used :utc_datetime.

Wonder if/what effects this has on migrations *(will there be errors when accessing the timestamps in one migration direction?)

heh, the actual data keys have different names, but the `metadata_updated_at` overlaps but using `:naive_datetime` here but when Pleroma also implemented this it used `:utc_datetime`. Wonder if/what effects this has on migrations *(will there be errors when accessing the timestamps in one migration direction?)
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#225
No description provided.