IGPAPI
    Preparing search index...

    Interface MediaRepostTargetInternal

    What a repost carries beyond the media it acts on: the feed context its like and note send. The media itself — the container id the like addresses and the note attaches to — is the media info answer's, read once into MediaInfoSource, so the two requests cannot name different media. The public brick maps its input into this and the Android post screen maps its own state, so both reach one constructor.

    interface MediaRepostTarget {
        audience?: number;
        deliveryClass?: string;
        feedPosition?: string | number;
        inventorySource?: string;
        loggingInfoToken?: string;
        mediaClientPosition?: number;
        tapSource?: string;
    }
    Index

    Properties

    audience?: number

    Note audience; defaults to the repost default.

    deliveryClass?: string

    Like delivery_class; omitted from the like when unset.

    feedPosition?: string | number

    Feed position of the acted-on item (like body feed_position).

    inventorySource?: string

    Like inventory_source; the note defaults it.

    loggingInfoToken?: string

    The feed's logging token: logging_info_token on the like, ranking_info_token on the note.

    mediaClientPosition?: number

    The acted-on media's position; defaults to 0 on the note.

    tapSource?: string

    Like tap_source; omitted from the like when unset.