ekk

Pitter patter!

Paweł said in Native Push Notifications Support for NodeBB: > julian maybe it is worth to check this behavior in Browserstack? Yes, this is a good idea does browser stack have support for push notifications?

Luckily, from where I'm from, they were.

[email protected] for me, summary is a stop-gap until a proper alternative representation is agreed-upon. content in Article is unusable at the moment due to aforementioned restrictions (even more so than content in Note). Don't worry [email protected], stuffing the whole post body into summary isn't a "trend" you should be worried about.

> One weakness I have noticed in NodeBB's current federation is that posts which are in reply to a topic (e.g. a Lemmy comment) show up as individual threads until (or if) the root post of that topic shows up in the local NodeBB. No, Lemmy does not implement either strategy, they rely on 1b12 only. If NodeBB is receiving parts of a topic that don't resolve up to the root-level post that might be something we can fix. I'll try to take a look at it.

Furbland-Channel-2 Yes, this is a feature which even I too would like to have and have already mentioned in https://community.nodebb.org/post/104536 point 1. julian You are most probably on a fast internet connection and that is why you are not facing any problem in the current behavior(fetching the entire file). But people like me, Furbland-Channel-2 and most peope in real-life who are on average-speed internet connection are facing problem in playing peertube videos and would like to have the peertube videos played in iframe embed(hls) just like other platforms(mastodon, misskey, etc)

Yes. When the reply is posted to C, it is sent to A. A then sends as:Announce to C, as well as any other communities that follow it. B seems to be irrelevant here.

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

Please let it be my species. Wait I'm still here. Shit.

You have to look up the lyrics to Cecilia? Is she not sufficiently breaking you apart? How does your confidence manage on a day to day basis?

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.

It trickln't

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

You had a chance to let people assume youre cool.

I think they believe getting their fingerprints and having a background check means they have a security clearance or something.

draga79 interesting... I wonder why FreeBSD support was removed.

Paweł we are not able to reproduce on this site, which is why we cannot fix it.

How to pick up a duck

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.

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