Alicornutopia

Yeah it would probably be super hard and annoying to implement but it would be so nice to have.

aaaaaa

if this becomes a thing can there be a user option to hide all of it

I cannot think of anything that would make me more likely to just-not-write-things than having to see people's reactions to my writing every time I went to write

If it were just a kudos count like on AO3, would that be fine?

Moriwen wrote:aaaaaa

if this becomes a thing can there be a user option to hide all of it

I cannot think of anything that would make me more likely to just-not-write-things than having to see people's reactions to my writing every time I went to write

I think we did have an issue mentioning this somewhere but I can't seem to find it, and it definitely had a note that it should be possible to turn it off because it would be awful for some people. (I mentioned this earlier in Discord.)

DanielH wrote:If it were just a kudos count like on AO3, would that be fine?

This definitely came up before, albeit on a thread level rather than a post level (which would indeed be like AO3), and was shouted down; something about it being likely to turn into an obligation and failing to be useful feedback because of that, iirc.

A kudos count would be just on the edge of tolerability.

(When my brain is being brain, what it really wants is to pretend that No One Else Exists, And If They Do, They Definitely Can't See Me. Visible evidence of other people reading my posts is juuuuust tolerable. People talking to me about my posts is not.)

(No, my cowriter tagging me back does not bother my brain. My brain does not believe in cowriters; all those other posts magically coalesce out of the mist. Do not question the Ways Of Brain.)

I do agree it seems like there's a risk of people ending up feeling obliged to leave comments/kudos/likes/whatever (even with arbitrary amounts of disclaimers that there's no obligation). And I wonder if people mightn't end up feeling anxious or unhappy about Not As Many People Liking Their Posts; though otoh it might be nice for people to see that there actually are people reading their threads.

Also, like -- would comments/kudos be public? Visible only to the person who wrote the post they're on? To all authors in the thread? (Being able to, say, sort threads by kudos count like on AO3 seems like it would have both upsides and downsides.)

Kudos would be okay but I'm specifically hoping for something where I could make a quick note that I found a post super adorable or heartwrenching or hilarious. Personally, having *any* feedback at all would be a major bonus and I would not feel bad that more popular authors might have more reactions. I'm not sure how I feel about being able to sort threads by kudos count - if it's a simple +1 all that tells me is that a lot of people read it, not that it's any better than something few people have read. What I would be really interested in is, for a suite of multiple types of reactions, being able to see *which kinds* of reaction were most common. If I can tell that a thread is 30% haha, 50% adorable, 10% heck YES, 5% sobbing, and 5% sparklefling, that gives me a good idea of whether it's the sort of thing I'd want to read.

My ideal is that the reactions/comments/kudos would be public and act basically like notes on a tumblr post or comments in a reaction thread or likes/comments to a facebook post or etc. I definitely wouldn't want it to be structured in a way that makes people feel obligated to leave them - I think per-post rather than per-thread helps with this, for me? Because I'm obviously not going to have a noteworthy reaction to *every post* in a thread, whereas if it's on a per-thread basis that makes it feel like it's simply a "I read this and enjoyed it" signal rather than showing how I felt about a particular moment or having a metatextual conversation.

I think the ability for authors to turn off the feature or limit it in other ways should definitely be a thing. Fear that other people are paying attention to me and have expectations of me was definitely something keeping me back from authoring anything for a long time, so I can see how this would be a potential Bad for some people and I think that should be accommodated!

so hiding a continuity from unread breaks the green arrow (no matter whether i read a thread or not, green arrow status doesn't change from the moment i hid the continuity on)

Tiny request of the day (as usual, Marri, Throne, please do tell me to let it go for a while if you're overloaded enough that this is more annoying/stressful than useful):

When you're typing a reply, it shows the character information block next to the text box just like on a finalized post; however, unlike on a finalized post, the character name is not a clickable link to their character page. Could it be, please? I often start making a reply with a new character, realize I want to (give them a new icon/double-check that it's the correct instance/add an alias/etc), try to click their name, and then have to either track down an earlier post by them in the thread or open up my character page and find them in there. It would be very convenient to just be able to open their page directly.

Also: would be cool if each gallery showed a list of characters it was attached to (in the same way as icons have a list of galleries they're in).

Also also, not a request, but: it was just striking me how much I love the ability to re-order galleries for a character. Such a tiny thing but such quality-of life. The Constellation is so good. <3333

The first thing sounds like it might be problematic especially on mobile devices where the "swap alias" or "swap character" buttons are small (as with the unread button), in case people accidentally click them and get redirected away from their post. (Of course, hopefully a browser would save the text when you press back, but it may not.) I'm not sure how to get around this.

The second request has already been suggested (issue #144).

I think these requests are fine (and good to have, so we at least have them documented on a list somewhere and don't forget them and/or get used to them and then never fix them but continue to be inconvenienced by them), but we are getting quite a mounting list and it's not decreasing very quickly. People should maybe … not expect all these requests to be processed very timely, perhaps? We're getting to things but I think it's in a reasonably haphazard order and I'm not sure there's a good way to make it known what order we should prioritize them in.