72d7580461
This is a pretty simple way for us to track which webmentions are sent by Ghost. Although it's easily spoofed, so are other approaches like using a header (e.g. User-Agent). If we find that this data is being spoofed we can look at different approach. Becuase our receiving implementation stores the payload of the Webmention, we'll be able to know inside Ghost which Mentions originated from another Ghost installation, which is useful for stats and gives us the possibility to display that information in the feed. Longer term we might want to consider storing this data in a separate column for Mentions, rather than the `payload` column - but that is outside the scope of this change. |
||
---|---|---|
.. | ||
adapter-manager | ||
admin | ||
api-framework | ||
api-version-compatibility-service | ||
audience-feedback | ||
bootstrap-socket | ||
constants | ||
core | ||
custom-theme-settings-service | ||
data-generator | ||
domain-events | ||
dynamic-routing-events | ||
email-analytics-provider-mailgun | ||
email-analytics-service | ||
email-content-generator | ||
email-events | ||
email-service | ||
email-suppression-list | ||
express-dynamic-redirects | ||
extract-api-key | ||
html-to-plaintext | ||
i18n | ||
importer-revue | ||
job-manager | ||
link-redirects | ||
link-replacer | ||
link-tracking | ||
magic-link | ||
mailgun-client | ||
member-attribution | ||
member-events | ||
members-api | ||
members-csv | ||
members-events-service | ||
members-importer | ||
members-ssr | ||
minifier | ||
mw-api-version-mismatch | ||
mw-cache-control | ||
mw-error-handler | ||
mw-session-from-token | ||
mw-update-user-last-seen | ||
mw-vhost | ||
oembed-service | ||
offers | ||
package-json | ||
payments | ||
portal | ||
referrers | ||
security | ||
session-service | ||
settings-path-manager | ||
staff-service | ||
stats-service | ||
stripe | ||
tiers | ||
update-check-service | ||
verification-trigger | ||
version-notifications-data-service | ||
webmentions |