And finding the relays that do not honor requests (and have not shut down or scrubbed old data) is slightly more annoying than just having your own internal reply guy record, which is my point.
They are likely to have multiple angles on post archiving, bots, their own relays etc to point to when needed.
In that case, no need to have a “ReplyGuy”. Just have a “client” that connects to every possible relay, and scrape as much data as possible, and never delete anything.
They are likely to have >>>multiple<<< angles on post archiving, bots, >>>their own relays<<< etc to point to when needed.
Sure, but there’s simply no point to making a ReplyGuy bot if archiving is your intention. Instead of the bot “replying”, it could simply archive to a private database instead. There’s no reason to do the extra step of spamming the network for no additional benefit.
