• Log In
  • Sign Up
    • it would help if the "Publish" button was at the bottom, or remained visible at the top regardless of how long our post is.

      I agree here. So much about Cake is very intuitive but when publishing a new thread I find myself looking at the bottom for the public button first (on desktop).

    • I used a bold font for section headers in my post, as well as to highlight the main points (suggestions) of my post, to make it easier for people who are just skimming through. On Facebook, I don't think people write that way

      Facebook does have a "Note" feature with rich-text editing though.

      Edit: the Note feature has been greatly demoted it seems. It's not on the "new post" UI and have to hunt it down to your profile under a sub-menu in order to create a new Note :D :D

    • Here is what I miss the most from some of the other social media platforms I play with:


      I really like the ability to use very simple text decorators to create content which makes use of proper section, subsection, sub-subsection, etc. navigation markers, easily lets me link to other media, and even has the option of generating a table of contents.

      To say that I like longform media is probably an understatement.

      I don't mind a really good rich text editor; Medium has one of the best longform content editors in the social media space, in my opinion. But it would be really nice to be able to create the actual text, link to other content, be able to simply cut-and-paste that into a post, and have everything "just work."

      I can get tiny, individual updates in a lot of other social media platforms. What I really want, especially on a topic-first interface, is something that makes it easy to make content which is as ideally presented.

    • I love Markdown too! And I agree that Medium's editor is one of the best; it's the high bar against which we measure our editor. We went with a rich editor for Cake because while Markdown is reasonably well understood among tech-literate people, it's not commonly understood by less tech-literate people.

      One of the features on my personal wishlist that we just haven't had time to implement yet is to enable transparent Markdown support in Cake's editor, so you could use standard Markdown syntax to trigger _italics_, **bold**, `monospace`, etc. without needing to use the editor toolbar or keyboard shortcuts. Just gotta find the time!

    • The way that Typora ( does the integrated Markdown editing with allowing you to enter the codes and then rendering it immediately upon moving out of that editing area is damn near ideal; that and Gingko ( are my editors of choice in nearly every situation. The one thing I miss on a regular basis from Medium is the ability to inset a graphic with scaling on the right side of a para with wraparound and captioning, but that's not even a part of standard Markdown so I can't object too much.

      The other thing that I wish more social media sites did was properly threaded replies. I miss the old days of USENET where you could see the branching structure of peoples' replies and move through them either depth-first to follow a thread you're interested in or breadth-first to find some bit of discussion you want. Quoting and branching are big, huge deals for carrying on conversations that most socmed sites post-USENET just don't seem to care anything about (except Steemit (, though it has other issues).

      I love the fact that Cake is topic/subject-first, which pushes people to pay attention to content and not just follow folks around without concern for what they're saying. It's a long needed design change that needs someone to experiment with it to find where the ideal content-discovery pivot is.

      (But it needs a Dark Mode. That's all greedy me, though.)

    • people who use rich text editing

      On metafilter they allow strike thru fonts so that you can make a snarky sarcastic text, strike thru it and replace with a more PC text. lets call this the sarcasim enhancement.

    • the sarcasim enhancement.

      I'm not sure that making it strictly obvious really enhances sarcasm. Very much like how explaining a joke doesn't make the joke better. Unless the joke is how you explain the joke. But then you have to explain the meta-joke, and at that point we need to implement an entire joke-type system, express it in Haskell, lose 35 pounds and half of our hair, and have job security forever because no one in their right mind wants to learn Haskell to maintain the code.