pay-to-read and pay-to-post sections (possibly most of the site being pay to post but publicly readable. a way to choose or generate an anonymous name that becomes your default in that one thread, and being able to pick different names for individual comments Rails 6 added a WYSIWYG rich text javascript text area as an included default thing. i'm not sure how much users care about this or how much trouble it is. probably want to convert it to markdown and save it in the db as markdown so ppl who write in markdown can quote it, and limit the features to what has a markdown equivalent.
LIGHTPAPER EDIT WYSYWYG ARCHIVE
integration with email newsletters like mailchimp so the archive "read on the web" pages for my newsletters would be on the website and then auto format and send that to mailchimp (or whoever else) to be emailed out RSS, email notifications, on site notifications subforums could include sections like serious discussion, "i want criticism", debate, "i want to discuss to a conclusion". subforums, which might just be category tags and allow a post to be in several user entered category tags? maybe, maybe not, idk education, relationships, parenting, rationality
having good s for some common searches that represent e.g. being able to do comment search stuff across multiple threads (so you can see my top level comments + my self reply chains to my own top level comments, but not my replies to other ppl including if i self-reply to a reply to someone else then that's treated as part of me replying to someone else) and for non-replies you should optionally be able to have self-replies be given the status of their parent. smart filtering options like in a thread filter for only comments by particular users, in a date range, nested under a particular parent, or non-reply comments. you can see a personal blog for Joe by searching for top level posts by joe) category tags on posts and comments, e.g. graph view showing all the comments with the parent/child links tagging parent posts, including multiple parents, similar to writing #1 here
For stuff not in version 1 it can be good to have it in mind in advance so you design things in a way compatible with it. Some of these are maybes, and some don't need to be in version 1. payment processor library that abstracts over Stripe (so it's easier to switch if deplatformed) might want to display **bold** in the way does, and compatibility with lots of existing markdown editors and tools is good) standard markdown library (idk what but we'll want some ability to customize it, e.g. auto generate CRUD pages framework like (which looks way better than Rails' built in scaffolding feature) high abstraction level web dev framework (like Rails), preferably with "convention over configuration" approach (good defaults customize when you need to but stuff just works automatically when u don't) if it was me i'd probably just use whatever Rails has as a default i don't have much experience with front end js libraries. Stripe (from reading patio11's marketing, i am under the impression that Stripe has the best tech of the payment processors) some sorta virtual machine or container setup for development environment (vmware, docker, vagrant, virtual box, idk what's best) linode has been fine as my web host for (not rackspace) Debian (over ubuntu i don't have much experience with other linuxes)
LIGHTPAPER EDIT WYSYWYG UPDATE
David Deutsch Harassment Update for September 2021.Writing Critique for "Community Banking and Fintech".David Deutsch Harassment Update for November 2021.Analysis of David Deutsch’s The Final Prejudice.Harassment Campaign Update for May 2022.Specialist Creators with Small Audiences.Restating Opposing Views Charity in Debates.Discussion and Boundary Based Relationships.Mammals (Energy, Digestion, Broad Conceptual Explanations, and the Lion Diet)
0 kommentar(er)
