mirror of
https://akkoma.dev/AkkomaGang/akkoma.git
synced 2024-10-30 05:23:10 +00:00
4ff5293093
Usually an id should point to another AP object
and the image file isn’t an AP object. We currently
do not provide standalone AP objects for emoji and
don't keep track of remote emoji at all.
Thus just federate them as anonymous objects,
i.e. objects only existing within a parent context
and using an explicit null id.
IceShrimp.NET previously adopted anonymous objects
for remote emoji without any apparent issues. See:
|
||
|---|---|---|
| .. | ||
| activity_pub | ||
| mrf | ||
| object_validator | ||
| object_validators | ||
| side_effects | ||
| views | ||
| activity_pub.ex | ||
| activity_pub_controller.ex | ||
| builder.ex | ||
| internal_fetch_actor.ex | ||
| mrf.ex | ||
| object_validator.ex | ||
| pipeline.ex | ||
| publisher.ex | ||
| relay.ex | ||
| side_effects.ex | ||
| transmogrifier.ex | ||
| utils.ex | ||
| visibility.ex | ||