Technical Support

You can use the S3 plugin. However, the underlying problem is that you are using some sort of service with an ephemeral virtual drive. It gets cleared every time the service restarts. If you don't want to use s3, you will have to set up a volume and mount it to the /public/uploads folder.

ska correct, since web-push relies on more modern browser supported technology and doesn't require a third-party service (in this case, ntfy.sh)

phoenix you can always test with ActivityPub.academy, live Mastodon servers can sometimes be delayed.

AMAARETS I think all you really need to do is have your plugin change req.session.uid and req.uid to the target uid. Although in practice there might be some cases I did not consider.

eugene_thedev are you referring to specifically the oauth2-multiple plugin? I'm not exactly sure whether that is supported in the current iteration of the plugin.

Rp1 if the session sharing token ends they would just log in again using the SSO handler. There is no refresh token support in the session sharing plugin at this time.

Ashutosh-Verma have you tried adding a widget container to the widget? Widgets normally aren't set up with any containers so there won't be any space between them.

With the Lemmy developers' help, we figured it out! It was NodeBB's spam protection mechanism. One of our configurable options is to limit the number of upvotes one can make per day. Someone (or someones) on Lemmy communities was sending lots of upvotes and running into this limitation when those activities were propagated to NodeBB. NodeBB dutifully noted this and sent back an HTTP 500. Lemmy dutifully noted this and retried sending the activity using an exponential backoff algorithm Eventually enough 500s were recorded that Lemmy decided that our server needed a time-out of sorts I updated the code to handle this case better, and now the activities are coming in at full speed. It'll take awhile to get back up to sync though

phenomlab ah good to hear, thanks, and sorry about that! We're not quite sure what happened with the eslint update that caused existing installs to complain so loudly.

ScrapBlox hi, sorry about the delay. Sometimes it's hard to think of what to debug next. Can you screen shot the settings on both sides? Feel free to blur out the client id and secret

Okay, so disabling HSTS and flushing my browser cache again brought remote images back. It's obvious that I need to crack into the ideal way to configure these things for the Fediverse, might have to replicate how some of my other Fediverse platforms are set up on the Nginx side.

Kichae re: > so giving registered-users privilege back to -1 worked? can you let me know if the registered-users bug is still occurring? I am wondering if I patched it in the course of regular development.

M1hono you can create a new category and check the box to treat it as a section.

M1hono also check that cookieDomain is not set to anything in ACP Can you share your nginx config?