bh4-tech

D1re_W0lf Although I don't have an iOS device, but according to docs,on iOS web push notifications work on only those sites which have been added to home screen. So, add this site to home screen and check after few hours.

@baris Not related to this, but I am also facing a problem due to csrf token. I earlier used cloudflare SSL on my nodebb instance but now have turned it off because it was giving issues with loading media for federated accounts. My account was auto logged off and now I cannot login. Everytime I try to login, I get the error "Login Unsuccessful We were unable to log you in, likely due to an expired session. Please try again" and the url bar shows

/login?error=csrf-invalid

This happens both for admin as well as non-admin user. I have turned on-off-on as well as restarted both nodebb and nginx but the problem remains. Any suggested solution?

@bh4-tech Also, noticed that in some cases image preview is displayed properly beside the topic headline, but in the actual topic, instead of the image we see the link.

@bh4-tech I realised that a part of the issue was due to the fact that I was using cloudflare proxy. Disabling that improved the situation. Now, my instance does not crash on viewing threads media. Also, for every 3-4 media , 1 media file loads properly(link is not displayed, actual media is displayed). Maybe, admins should have the ability to set a custom timeout for the link preview plugin so that the success rate for viewing remote media becomes 100% as compared to current 25-33 %. @julian

@julian Yeah that worked for mastodon, but not for threads. Guess that's some problem on thread's side and not nodebb.

However, the remote media preview problem still remains https://community.nodebb.org/post/103782 . Guess you will need to cache remote media like misskey.

@julian https://www.threads.net/@khabydistas on threads and https://mastodon.social/@dansup on mastodon

@julian Are categories supposed to follow regular users from this screen in admin panel. Asking this because I tried putting a mastodon user profile link in the textbox but upon clicking on 'Follow' nothing happened. For threads, the request is pending(with some error, I guess) as you can see from the picture.

@bh4-tech Now threads seems to have reduced the time for URL signature expiry and media files expire by 24 hrs @julian For this, the only workaround I think is that my nodebb instance will need to save(cache) the remote media as soon as it is received Posting the link of a recent post below whose media has around 10 hrs more before it expires https://ekk.app/topic/40fda023-3d00-42e1-ad8c-ca3973760012/________

Here is the link https://ekk.app/topic/e670e98f-c13f-4ab5-b174-96974ebca495/jay_shah_%E0%A4%95__%E0%A4%95_%E0%A4%B0%E0%A4%A8_%E0%A4%AE____

and here is the original post link https://www.threads.net/@dhananjay.naidu02/post/DHAlBHgzryu

I tried running with ./nodebb dev and although no response was received from site (pic above) no error message was also logged in console

For mastodon based servers, media loads properly after refresh. For threads, my nodebb instance dosen't respond(Bad gateway cloudflare 502 cloudflare error) after refresh, so the only way I can access the media is clicking on the long link. Both are non user-friendly UX, specially for those who are not accustomed to activitypub

@julian My nodebb instance is able to federate with threads and so I get posts from there also. Media from threads come in extra long url, with a very long hash(I guess) after the actual resource, so this problem gets even more prominent there. Would be nice if this is solved soon. Here, you can see the video url after the text of the post.