I'm working on a 2020 revision to my book, OAuth 2.0 Simplified!
oauth2simplified.com
If you find a typo or other error that I am not already aware of, I will send you an OAuth cat sticker! Send me an email or DM with details if you find something!
I don't have a *good* solution for this, but I usually do a combination of:
inviting my work account from my personal calendar
manually adding an event called "Busy" to my work calendar
Out of curiosity what do you mean by spam? Unwanted bridgy feedback? Spam sent via pingback?
I am not likely to add a manual approval step FYI because that kind of moderation gets tiring and overwhelming quickly. But you can do it via the web hook!
I still think you're missing the overarching goal that we're doing here. We're explicitly not saying "do it all yourself", which is why I'm super glad that things like micro.blog make it very easy for people to start to take ownership of their data.
That's why I download a copy of all the responses to my posts and serve the copies from my site. By now I'm sure there are plenty of cases of comments on my posts that are gone, but they still show up on my site because I decide to keep them there.
I think it's the title more than the thumbnail. A "tips and tricks" video is probly going to appeal to people who already have it. For a brand new $$$$$ one like this I'd expect something like "why you should buy the..." or "my favorite things about the..." would work better.
This is actually a very good description of the benefit of IndieAuth's use of URLs as client IDs.
w3.org/TR/indieauth/#client-…
Every app is identified by its URL, so you can build trust that way across providers.