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!

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.

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.

This is live on Write.as and merged into WriteFreely for the v0.13 release.

Taking this; related to existing work to eliminate references to "static pages" in user-facing docs, etc., in favor of "pinned pages". I should have something to show for this (in terms of changes) next week.

Will finish this up and get it merged. Because of how widely this feature is needed, I think we can get it in without the fediverse deletion functionality for now.

One issue: images aren't automatically resized, as they are when uploaded through Snap.as. Instead of doing client-side image resizing here, we should rely on the server: {T851}.

This is live on Write.as now (Classic editor v2)

Currently, this only uploads to a user's personal Snap.as storage space -- which likely isn't the desired behavior for users writing a post on a team / Organizations blog.

That last issue is fixed and deployed on Write.as. Final WriteFreely pull request: #356

WriteFreely PR #444.

WriteFreely PR: #442

@heyakyra This task has a broader scope / works on a higher level, for managing all users on a WriteFreely instance. We can address Team suspensions in another task.

This is deployed on Write.as, and will be in the next version of WriteFreely (see #439)!

Would this be helpful to leverage?

Docs are updated and WF pull request is open: #436.

This is already supported on Write.as and the Go API library, added in the attached commits. Will add it to WriteFreely and our API docs next.

Is Write.as served by Nginx, Apache, or something like that? I noticed that testmysite.io reports that HTTP2 is not enabled, but should be a one-line fix in Nginx config or there's the more bleeding-edge approach https://h2o.examp1e.net/ 😉