I think it's fine to use a different type. What I wanted to point out is that context property is for grouping related objects, and that there is another property that does exactly you want - relationship.
we're modeling a one-way relationship, not two way.
In a two-way relationship, there is an expectation that another Relationship object exists representing a reverse claim.
Is there another way around this issue that DOESN'T require Object Integrity Proofs?
I am not sure if integrity proofs really solve this problem... It's hard to tell without knowing who signs what (I didn't find that information in the FEP).
Ostensibly, a woman buys her son a DSLR camera. The delivery driver chucks it on her porch. She claims the thing was broken in the box. The CSR handling her complaint talks over her and denies her replacement claim.
Is this real? No one knows anymore.
@josephcox 404media does some great work, and you're absolutely right that what's happening with AI and search is a crisis for the industry that is causing great harm.
That said:
1. The explainer seems to conflate asking for e-mails to halt scraping (to verify that the reader is human) with asking for e-mails to send content there directly. These are not the same.
2. Your post seems to accuse Mastodon users of wrongdoing without anything to support the claim.
Is there something I'm missing?
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.