Yesterday I was thinking a bit about Web Monetization, and how it’s a little less ideal for written content than, say, video content. Whereas someone might skim or skip through an article, cutting their time on the page short and thus WM revenue, it’s much easier to passively watch a video.
Later in the afternoon, the thought occurred to me again, and of course it’d make sense to support WM on our own visual platform, Snap.as. So now (well, launching soon), for any blogs with a monetization pointer on them, their equivalent Snap.as profile will also include that monetization pointer.
Just sent out some updates to the new Classic editor (which I’m using to compose this post). It includes:
I’ll bring those updates over to WriteFreely next.
Finished the manual moderation tools I mentioned yesterday, and I'm pretty happy with the result.
I tested it out on a queue of about 160 posts from the last 24 hours, and it went smoothly, once I switched from my original design (quick form submissions and a
JOIN with the main
posts table — bad idea, it's too big) to async requests and denormalized data.
I'm thinking about what this would look like in #WriteFreely, and I'm not yet sure if exposing all of our spam detection logic will make it easier for spammers to work around our roadblocks. I don't know if they put that much effort into it. But I know instance admins would be very welcoming to a feature like this. So I'm thinking of bringing it over soon.
Working on some moderation tools today. As I've written about before, we see a ton of spammy SEO / link-building content published every day, and have had to put some automated filters in place to keep it at bay.
Besides these loose rules that take automated action on users and posts, we also have a manual side, where a second tier of suspicious-looking posts are emailed to us to review and optionally take action on. But these reports come in through individual emails and make moderation very, very tedious.
So to speed things up, I'd like to add a post moderation queue on the admin dashboard, to make it easier to watch for widespread spammy behavior and quickly stop it. Then, as I know WriteFreely instances see plenty of spammers too, I'll port it over there once it works well.
In the beginning, Remark.as was meant to be an answer to “How do I interact with people on my blog?” I'm wondering now if we expand its scope to include information about who you're interacting with.
I didn't want it to merely become a “comment management” platform, where people comment on your posts, and you display those comments publicly. I wanted more conversation and more social context. Those goals alone mean more potential paths for this product.
For more conversation and context, I primarily intended to provide more communication channels, for private replies and public commentary. We're going to dip our toes into this shortly, with the added ability for Write.as email subscribers to reply directly to your emails (private replies). This will be a very minimally-viable way to communicate today, but it'll open the gates to richer interactions down the road, perhaps facilitated by a web application instead of your email client, for example.
What kinds of interactions will people have? How will this feature be used? I'm not sure yet; I think we need that functionality in place, out in the wild, before we have answers.
Working on giving authors access to their email list, a frequent feature request I hear. I'm thinking about this from a few different angles:
It'll start off bare-bones, and we'll add only what's needed. As a bonus, this will lead to visibility into your fediverse followers, too.
I just fixed a long-standing bug that prevented people from following blogs from a Mastodon instance with Authorized Fetch enabled. The fix is deployed on Write.as, and will be merged into #WriteFreely soon. Write.as also sends out
Notes instead of
Articles in some cases. You should see that for this post, if you're following @email@example.com in the fediverse!
Working on a “welcome” email for one of our ongoing migration projects. I've always seen these as unnecessary, from my limited viewpoint and personal anti-automated-email bias. But over the years I've heard from a few people that expected to get an email like this after signing up — if anything, just to remember their username, and that they created an account in the first place.
Now that I'm implementing it and writing the email in the helpful way I would love to see as the receiver, I'm coming around to the idea. We'll roll it out for some very specific signups in the near term, and then expand it to all new signups if it works out well.
People who are good at designing and building incredibly complex systems are bad at recognizing their complexity and abstraction for what they are. If they did, they might be able to break them back down into simple devices.