EDIT: The developer has replied in this thread, see below :)

We banned a spammer from this instance recently, and I went to see what instance it was coming from (in case there was more)

https://coves.social/community-guidelines

Coves is built on the AT Protocol, which means it’s part of a larger decentralized network. Your account and identity exist on your Personal Data Server (PDS), not on our servers. These guidelines and our moderation only apply to the official Coves AppView at coves.social. Other instances of Coves or other AT Protocol services have their own policies and moderation. If you’re banned or have content removed from our AppView, your AT Protocol identity and data on your PDS are unaffected — you can still use other services on the network.

They do credit Photon and they have released the source code for their modified frontend: https://coves.social/legal

I also found this on their GitHub: https://github.com/BrettM86/tidepool

Tidepool is a read-only ActivityPub → atproto bridge for the threadiverse. It follows Lemmy/PieFed/Mbin communities (FEP-1b12 group federation), materializes their posts, comments, and profiles as social.coves.* records in a virtual PDS it operates itself, and serves them over com.atproto.sync.* so the Coves AppView indexes fediverse communities exactly as it indexes native ones. Votes stay bridge-side as aggregates behind one sanctioned XRPC.

EDIT: The developer has confirmed that two-way federation is planned

I think it’s neat that someone is working on this, but I’m a bit concerned that it’s read only from the threadiverse:

• They would suffer from a problem similar to what we have, when someone sets up a Reddit repost bot. Users interacting with some content while not knowing that their replies aren’t reaching the original poster
• they get content without giving content back