There's been more discussion about this on the forum. Rather than making this a Snap.as-only feature, it'll make more sense to add this to our existing publish-via-email functionality on Write.as, and simply store the photos via Snap.as.

This is a relatively frequent request we hear from users.

This was recently reported by an affected user in writefreely#490.

Implementing this should also fix writefreely#219 and writefreely#335.

@gytisrepecka If you pull the wm-fix branch again, you should see the exclusive content changes. Please let me know if you notice any issues there!

The plan right now is to include the Title and Description information in Snap.as (so we can incorporate those later), and then include the alt text in the posts themselves. But it might make sense to add "alt text" storage to Snap.as too. We can do that if it seems to make more sense.

Awesome, thanks!

The paid shortcode changes haven't been included in WriteFreely yet, as it was hard to set up the infrastructure for that before. However, they recently launched a public receipt verifier server, so I'm going to port these changes to WF now.

Thanks, after merging wm-fix I can now see input field to add Web Monetization Pointer for particular blog.

Thanks, will pull sources and try again 👍

Ah, good catch @gytisrepecka! There was an issue with the template file, which is now fixed in #463.

Does it mean that hosted WriteFreely will need to wait for SnapFreely to be available and won't have image upload functionality integrated into WriteFreely itself?

But version v0.13.0rc1 doesn't yet allow to set monetization pointer in blog's customize page? I couldn't find it even with monetization = true set in config.