capjamesgWhen you click on a poll option, you are prompted to vote with your personal website according to whatever web+action handler you have configured.
[echo]hey, i was reading the WM article on indieweb and looking at implementation, and question: how is spam being dealt with? i know on `WP.com` we deal with pingback spam, and this looks like a potential vector.
LoqiThe Vouch protocol is an anti-spam extension to Webmention that can also be used to customize how your site accepts responses from different audiences https://indieweb.org/Vouch
[aciccarello]haha, usually. I was thinking the receiver could differentiate, but then I remembered Vouch makes the sender look up the vouch and so they wouldn't know if it's per domain or path.
[KevinMarks]subdomain works OK, which suits tumblr and blogspot etc as well; if you have folderpath for users then you need to be a bit more careful yes.
jackythat could be in a number of ways (ideally /representative-hcard, reading things like rel=author then falling back to the authority part of the incoming URL)
[echo]right- so that’s because `*.tumblr.com` or a custom domain you have is driven by your theme, which is mostly arbitrary code. that’s what the GH repo code is
[echo]but the internal www space is driven by our React frontend and SSR, so we don’t put canonical there it seems. we could certainly add that- i’ll have to make a ticket
[echo]yeah my thinking is that we’d want a set of URIs to point to a specific blog identity. that can either be the internal Tumblr ID of `t:XXXX` which is effectively a stable ID, or the blog name which is semi-stable
[echo][Scott_Jack] we’re still keeping subdomains! we’re talking internally about redirecting users who never customized their blog theme to the www. path though
[echo]but from a technical perspective, given cross-domain issues actually _interacting_ with Tumblr is really hard. that doesn’t affect something like WMs, except in the fact that we have very limited engineering resources and maintaining two completely different code paths is really difficult
[KevinMarks]by default webmention has the 'twitter @ reply' problems - presumably tumblr already has an equivalent of unwanted replies and what gets shown to whom?
[echo]i’m less concerned about us for spam tbh- we can leverage existing code to deal with this, it’s just another form of pingback spam. i’m more interested/concerned about self-hosted folks that don’t have the big-picture data we get
[KevinMarks]It is a big messy problem, always. You need allowlists and blocklists and to decide how to construct them and what you do by default and so on. As you say, you only tend to need it once you are a target.
capjamesgWe haven't seen a large-scale spam issue with Webmention to the extent I understand so we'll likely learn a lot when we start to see real world vectors.
Loqi[pluginkollektiv] Description
Say Goodbye to comment spam on your WordPress blog or website. Antispam Bee blocks spam comments and trackbacks effectively, without captchas and without sending personal information to third party services. It is free of charge, ad-free...