Retain standard nodeinfo about instances #225

New issue

Closed

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

floatingghost commented

2022-09-20 14:23:22 +00:00

Owner

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

Oneric commented

2024-02-23 22:19:27 +00:00

Member

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.

floatingghost commented

2024-02-23 22:37:44 +00:00

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

👍 1

floatingghost closed this issue

2024-02-23 22:37:45 +00:00

Oneric commented

2024-02-23 22:51:00 +00:00

Member

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?)

Oneric referenced this issue

2024-02-23 22:56:36 +00:00

Better document database differences for Pleroma migrations #699

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.