ekk

bh4-tech that's good to know, thank you!

[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.

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

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.

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

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.

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

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

I suppose you're right in a way. The context owner is not supposed to be set by someone other than the context owner. It's a fallback mechanism intended for better compatibility with Mastodon. When a group is addressed and it is one of the local NodeBB categories, it will assume control If it is another group that it knows about but isn't same origin to the author, then no category is assumed.

Thanks! It's something that I personally feel is more performant and future proof for other important things like private discussions (which Mastodon also doesn't support natively yet — mention spamming doesn't count.)

chartung ah... Yes usually they're in there for a reason hehe Glad you figured it out!

The use case seems clear: actual DMs on the fediverse. How does this interop with existing implementations that utilise direct addressing (and intentional omission of as:Public) as a form of direct messaging? As usual I am assuming we will have to support both.

> Ubuntu 8.10 Intrepid Ibex also had its namesake animal on the default wallpaper, but more subtle than the last release. That was an Ibex? All this time I thought it was a coffee stain.

[email protected] let me know if I got any of the details wrong. Much thanks to your team for the assist in debugging!

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.

I love Kagi. You get what you search. Never had anything pro russian or weir result

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.

Update: Able to follow now