@[email protected] no worries, and thanks! Will do.

Lmao same, been like this on and off for a few days.

@eeeee Your reply (what Lemmy would term a comment) would go out to friend@nodebbinstance but it would be up to nodebbinstance to resolve what post the comment was a reply to. To illustrate what I mean about Lemmy and User Mentions in posts, see this post as an example. In the body of that post, the user Mentions 2 people - [email protected] [email protected] but neither of those people would have been notified of that post. You can see for yourself by looking at the activitypub representation of that post (by running curl --header 'accept: application/activity+json' --location https://lemmy.dbzer0.com/post/39126561 | jq .) and noting that there are no Mentions in the 'tag' section. By contrast, another user Mentions [email protected] in this comment, and she would have been notified of that (you can see that this time there is a Mention in activitypub representation of that coment). @julian For the other direction - as you've found out, Lemmy will first look at 'audience' for a root post and try to resolve it and bail if that doesn't work. If there's no 'audience', it will look in 'cc' to try to find a community and stops when it finds one. It won't look further, so you can't post in more than one community at a time, and you can't use a root post to post in Lemmy community and also notify a Lemmy user of it. It distinguishes between root posts and other posts because the root post is a Note will 'null' for 'inReplyTo'.

@[email protected] that was my thinking as well.

@rikudou maybe? Nullish coalescing sounds really cool, but I've avoided it for years because of browser compatibility. Node has had support forever (since v14, I've discovered), but I just don't know how to use it is all

@[email protected] thanks, PR opened! https://github.com/fedidb/communityDB/pull/23

@[email protected] if edits from PieFed aren't reflected here that may be a bug.

@[email protected] just wanted to drop a note that your two issues have not been forgotten

The ttl should be in milliseconds, so try 600000.

> Doesn't this mean Mastodon users et al will no longer get boost notifications when their posts are reshared into a topic? Correct, only OP will be shared. Unless I am mistaken this is how Lemmy implemented it. Announce-ing activities only, and one single Announce(Note) for compatibility with Mastodon.

I can no longer reproduce the issue!

1. +1. I will replace webfinger address recommendation with a warning about possible compatibility issues.2. I think observers (and other Application actors on the server) should use a shared key.

@[email protected] can you try renaming the handle to something else and back again?

@julian Just like @pankaj-soni , I too would like to have push notifications on by default

Yep, everything works!

@julian Awesome, thanks. Hopefully Announce / Update isn't similarly afflicted! (I realise that activity is the source of its own Issue, so I haven't seen any yet).

Most other people won't realize it either, I don't think. I've just been clicking on everything with abandon and stumbled across it.

@julian FEP-171b has its own way to backfill, also via context, but it is a collection of activities (such as Create).I am currently trying to figure out how to make Containers compatible with NodeBB and others.