It doesn't, no. The bot gets its data from another bot, at https://lemmyverse.net/, which only crawls Lemmy and MBIN instances at the mo.
We'd either need to send a PR to get that bot to crawl PieFed instances too, or just replicate the functionality from the same machine that runs 'tcbot'. Communities would also need to provide their 'active users / month' too. It's just the subscriber count currently, but it shouldn't be too much of a problem hopefully.
I'm now concerned that I've unfairly brought PieFed into all this. It's not my project, and it will continue to thrive irrespective of how much I do or don't contribute to it.
I do, however, think that cm0002's current project is doomed. The idea that the admins of Lemmy instances of any significant size will defed from ML on the promise that one person will continue to be willing and able to replicate missing content, presumably forever, is not one I can foresee succeeding. If the admins of lemmy.ml weren't also the devs, then maybe, but otherwise no.
It was this approach that I was attempting to criticize, not any fundamental political disagreements.
I'd be wary of getting a conversation node from anybody other than the original author (as described in the second approach).
There's a reason why, if you want to resolve a missing post in Lemmy, etc, you have to use the fedi-link to retrieve it from its source, not just from any other instance that has a copy (because, like the "context owner", they could be lying).
For Group-based apps, conversation backfill is mostly an issue for new instances, who might have a community's posts (from its outbox), but will be missing old comments. Comments can be automatically and recursively retrieved when they are replied to or upvoted by a remote actor, but fetching from the source (as you arguably should do) is complicated by instances closing (there's still loads of comments from feddit.de and kbin.social out there - it will be much worse when lemm.ee disappears). So perhaps Lemmy could also benefit from post authors being considered the trusted owner of any comments they receive.
What is the update delay for Fediseer?
I don't know. It's not something I'm familiar with - it might just default to saying 'closed' if it doesn't have the data.
It's interesting that the obvious bot accounts on those instances were set up in mid-March last year, so I'm guessing that these are somebody's army that they've used before, but overplayed their hand when they turned it on the DonaldJMusk person. The admins can reasonably be blamed for setting up instances with open registrations and no protections and then forgetting about them, but I'd be wary of blaming them for being behind the attack directly. The 'nicole' person is unlikely to have used their own instance - it's probably just someone with the same MO as whoever owns the bots, finding and exploiting vulnerable instances.
lemmy.world recently updated from version 0.19.3 to 0.19.10. This change - for Lemmy communities to federate out posts with the community name as a hashtag - was introduced in 0.19.4, so that might be the other reason why this has only just become an issue for you.
The attacker seems to be the admin of those two instances. Both instances have their registrations closed.
The alternative theory would be that these instances had open registrations, but rightly closed registration down after the admins noticed the bots. chinese.lol is on 0.18.4 with an admin with a 2 year old account, lemmy.doesnotexist.club has an admin with a 1 year account, and it was also that instance that the 'nicole' person has used before. This downvote attack would need to be a long time in the planning for what you're suggesting to be true.
Your link is broken.
It's probably not worth editing (vs. deleting), 'cos the video is also linked to in !games@lemmy.world, !gaming@lemmy.ml and again in this community too (a minute after you).