Email subscriptions are huge, huge; one of those features you think is relatively simple to build until you realize it needs to do that.. and also that.. oh and that, too.
Things are looking good enough to ship this in Write.as Labs soon. Last pieces:
- verifying email addresses
- sending posts on a delay
Another thought today: if we support ActivityPub mentions in WF posts, you could add your Mastodon / Pleroma / etc. handle to your posts, and any subsequent fediverse replies would mention and notify you. Could be a good stopgap until @remark_as is out.
Posts would remain "don't @ me" by default, but if you wanted comments on a post, you'd just mention yourself. 🤔
Kind of proud of this... I just finished per-topic browsing on @readwriteas, and instead of creating new database tables and adding to the admin UI, I just stored the featured topics in a plain Write.as post (https://write.as/w9fggtfchntbfj6c.md). The server uses the go-writeas library to fetch the post, does some simple string operations, and then generates the navigation bar.
What do you call this? Bootstrapping features on the platform I'm storing data for the features on?
State of the Development, March 2019:
Going to be a very busy month for development! Several major features planned for release, including standalone @snap_as accounts 📷
Updated the #WriteFreely Instances page to explain more of what's going on, and to not prioritize Write.as over everyone else's instance anymore.
At this point, it gets enough exposure elsewhere on the site. The goal for this page is to help all these other great communities grow.
Could use some input on this. Would data URIs be useful for you in WriteFreely? Or not needed?