erramenos :verifiedpedophile: (npub1awh…4ll9)
> do you know where pleroma stores notification feeds?
If you mean the database, it's in the notifications table; the web endpoint, is /api/v1/notifications.
> after i reciev about 20 or so notifications (enough to form a new 'page'), notifications start working again
You'll wanna look at that in the browser console. If it couldn't parse the JSON, usually it's because there was an error page and sometimes this is because your server is shitting itself. Sometimes it's a timeout, sometimes something has caused some weird error trying to render the notification (I think this used to happen with users that were deactivated), sometimes you've muted a giant thread that has several pages of your notifications in it.
One thing you can do to avoid the notification endpoint timing out is to do a full vacuum. If you combine that with clearing out old ones (say likes/reposts/reactions where seen = 't' and (CURRENT_TIMESTAMP-inserted_at)>'1 month'::interval), it has a noticeable impact on the table. Could also be a timeout due to DB congestion.
pistolero /
npub1ch…ysw60
2023-03-16 17:35:47
in reply to nevent1q…cq5g
Author Public Key
npub1ch8nj9yu4676fnwkzacu28mt4y002ezeryqyuhzfnzjw560sq5fqaysw60Published at
2023-03-16 17:35:47Event JSON
{
"id": "effe6723b09a5b2af2800e3b65e2681adea642f8bf9844015b4d7fa007a85ab7",
"pubkey": "c5cf39149caebda4cdd61771c51f6ba91ef5645919004e5c4998a4ea69f00512",
"created_at": 1678988147,
"kind": 1,
"tags": [
[
"p",
"ebae7d823eb57c17ea0bfd5cb4db54077d7a435d6d0dc4e586e7ee608d2b293f",
"wss://relay.mostr.pub"
],
[
"e",
"136ecab93a8ce98deeb3d93b028011fb3d6194282c5aa964926d51aebe9548ea",
"wss://relay.mostr.pub",
"reply"
],
[
"mostr",
"https://freespeechextremist.com/objects/2cfc9211-278a-4cae-9ee4-69159173f296"
]
],
"content": "#[0] \n\n\u003e do you know where pleroma stores notification feeds?\n\nIf you mean the database, it's in the notifications table; the web endpoint, is /api/v1/notifications.\n\n\u003e after i reciev about 20 or so notifications (enough to form a new 'page'), notifications start working again\n\nYou'll wanna look at that in the browser console. If it couldn't parse the JSON, usually it's because there was an error page and sometimes this is because your server is shitting itself. Sometimes it's a timeout, sometimes something has caused some weird error trying to render the notification (I think this used to happen with users that were deactivated), sometimes you've muted a giant thread that has several pages of your notifications in it.\n\nOne thing you can do to avoid the notification endpoint timing out is to do a full vacuum. If you combine that with clearing out old ones (say likes/reposts/reactions where seen = 't' and (CURRENT_TIMESTAMP-inserted_at)\u003e'1 month'::interval), it has a noticeable impact on the table. Could also be a timeout due to DB congestion.",
"sig": "ad4f1983ead9d1e5cecb2ea6ed9e9f0876fa6eff2d91376246bd51b8b5b460a84daf982b97a9048b3586fe0837914f62f9b31a937518b3d499ca7b64e3ada3fa"
}