Forum: Pinned List of Known Bugs & Popular Feature Recs (+ Bigger FAQ?)

Archive Feature Requests
#1

Reason:: TL:DR: Topic Duplication, ease of awareness (for lack of a better word) for both RemNote team and users.

Why?
  • Sometimes the same bugs and features are pointed out/suggested over and over and it will get hard to navigate the two forums as the App grows.
  • Sometimes we do ignore a topic even if it is above the fold or latest one made in a category by not checking, not noticing or when one’s new idea/bug seems different from what’s already posted.
  • RemNote expands, those kinds of topics should help both the RemNote team and the users needing or offering help. Obviously, duplicate topics won’t disappear, but they should hopefully lessen.
  • For Features, you can list only the popular ones, to cut down on time fiddling with them as well. More obscure requests can be found, but f you really want a complete list, go for it.

Proposed Action:: TL:DR: Pinned and locked topic listing current bugs/popular features in each category and their links. (Or make a public Trello-like board, that also works).
I propose a Pinned, locked (so only mods/designated people can edit) topic is made in each of those two categories, one as Currently Known Bugs List and one as Widely Requested Features (or whatever better name in that vein you can find).

How the topics would be structured:
  • Inside each of those two topics, a concisely named link to the users’ topics (for bugs: + link to the submitted GitHub bug report, when one appears) will reside in a somewhat alphabetical list.
  • Nested below the main link will be links to similar/same idea/issue topics if they cannot be merged into the main one. There is little point in alphabetising those (unless the list is huge and A-Z-ing it can be done easily).
  • The topic’s link name renamed for clarity (eg.: “I noticed something strange yesterday while drunk” to “Interface: Missing Header Button”).
  • No promise that they will be added disclaimer for Feature Requests.
  • Both topics will urge users to search for a suggested feature/bug first before a new topic is created and to contribute to bug report reproducibility/vote on desired features (sometimes searching will fail despite trying due to huge results numbers/unintuitive past naming of the current issue/feature).
  • If a bug if known/only reported on Github a link is posted (discussion topics can be added in if there is a need).
  • Would be nice if you can give some nod whether a request is viable at some point/will be implemented shortly to create hype but there’s a reason why that’s avoided as well. :woman_shrugging:
  • The Bug report topic will also contain the bug template from GitHub and instructions on how to submit one (link a short tutorial). Bug topics can also get a GitHub Tracker Report/known tag added by user or mod whenever it happens.
  • For bugs you can also make one is currently known to only be affecting one thing (e.g.: Google, Desktop App, Android 9), in case it occurs in other places for others as well.
  • Solved Bugs and Implemented Features can live in the folder for 1 month more or so to spread the word about the status.

You can also pin a select number of topics alongside if the bugs are incredibly nasty and widespread or a heavily requested feature just got implemented (tag it like so). :wink:

Quick and dirty unformatted examples:

Requested Features Topic:
No promise that they will be added disclaimer here. Then the popular features being requested list:

  • Aliases:
    Add hover preview (link).
    Make them shiney (link). Related: Make them fly to the moon(link).
  • Interface:
    Add font choice (link),
    Add more official themes(link)
    Fix Dark Mode(link).

Known Bugs Topic:
How to submit (a how to GitHub video/article link will be useful for some), link to reporting template. Then the current Bug Reports list:

  • Imagine Occlusion: Editing not allowed (link). Not displaying on Desktop App(link to topic + github), related: A green imagine file icon is shown instead (link).
  • PDF: Cannot rename(links). Cannot upload(links).
  • PDF Highlight: X, Y, Z and their links.
  • PDF Pins: A, B, C and their links.

On the same vein a mega FAQ pulled once in a while from the Forum, Discord, Reddit & other sources can live/be linked to in Community QA for easy referencing.
A locked topic and minimal number of editors would work better than users running wild with it. Assign 1-2 specific mods (preferably on different time zones if there’s more than one) to monitor and add to the pinned list topic in a category.

Excuse any typing errors, this turned into a wall of text. :woman_facepalming:

Community Connection 👋🏻
#2

Thank you for the detailed description, some really nice ideas there. We are reflecting upon them and will definitely get back with a good plan to implement the best strategies.
We really appreciate pointing out the problems and also proposing possible solutions for them :slight_smile:

3 Likes
#3

This is like an extra thing to develop. Requires some time. Not a bad idea though!
I honestly haven’t read the whole thing. Maybe we can have a discussion with the @RemNote Team on Discord to actually have our bug reports and Feature requests more structured? The #bug-reports Category here (forum) and The Github issue tracker collide a lot, Github is kinda weak in discussing, because majority users are in the Forum, but bugs from here has to be taken to Github to actually call it a bug report (portals :rofl: !)
@Karthikk, @hannesfrank, @ognsya, Do you think high level maintenance of the community portals like this is required (or to what extent it is)?
@Gabriela.AD Yet again, thanks Gabriela!

1 Like
#4

Yes the team has been informed about this :slight_smile: we will be able to handle such tasks more efficiently soon :slight_smile:

#5

Having some meta posts would definitely be nice, mainly from a project management perspective, but is of course a heavy time investment. See also Public roadmap for RemNote.
It’s more value if the devs focus on fixing bugs and implementing features instead of writing about that.

And from the community side there are just not enough people who’d like to organize stuff (e.g. sorting through Top Discord Suggestions).

IMO there should be more moderation in #community-help as well to keep this forum usable, but again - time - and this could also potentionally alienate users who have their topics altered too much.

I mean we have this pinned for Q/A:

and there are still duplicate questions, cryptic questions, questions where people just asking “why does this not work for me” (aka support), questions where answers and comments are all over the place (e.g. “Thank you” should be a comment, not an answer) etc.

Just saying that a pinned overview or guide does not necessarily solve having duplicates and stuff :man_shrugging:

In short: If you/anyone can something, do it. Even a little bit is better than nothing. But don’t expect it to magically keep the forum clean.

#6

Pins and rules aren’t always checked or remembered, and yes, over-moderation will turn people off. Also, if mods over-moderate, so will the users. No solution will every fix everything, and there will still be stray repetitive posts and whatnot.

It’s more value if the devs focus on fixing bugs and implementing features instead of writing about that.

Definitely. Since the admin team is so unusual (dev + marketing), it all falls solely on the moderation team (they are probably juggling stuff IRL and are short on time themselves) to deal with any fire and to support them.

The need for the platforms (and the app) to be organised and maintained, and have busy bee moderators is higher since we are dealing with potential and current customers here. RemNote isn’t just a community, since RemNote is seen as a company. It is not an easy feat, especially with so many platforms at play, certainly. People also expect admins and mods to communicate with each other, deal with similar but internal lists, be available, and have access to certain information/decisions as they are seen as one team (and they need to keep believing that, especially in this case), even if that is never completely true internally.

I was checking to see what the response was to one idea, and the non-optimal solution proposed for it (one needs more sleep to brain), to see if I should pester you with any others. Nobody wants to be slapped by staff for overstepping after all.
If you need other people from the community to help with specific things, ask very loudly. :wink: Besides hair-pulling over Discord suggestion hunting, what do you need help with exactly and how?

2 Likes
#7
  • TAG EVERYTHING OF VALUE! Loud enough? :crazy_face: I think that would be a nice way of structuring the forum based on subject while categories sort by type. lesswrong.com does this magnificently!
  • Move topics when in the wrong category, especially out of Q/A if they are not “evergreen”.
  • Rename topics carefully (the original author might already have thought a lot about it) to best describe its content. A naming scheme could create additional lightweight categories similar to breadcrumbs in a hierarchy, e.g. prefix FRs about pdfs with “PDF Integration -” etc.

This was just an example. I think there is nothing to do left. It was meant to kickstart the FR category when suggestions were migrated to the forum and make sure no great ideas from there are forgotten. I think the FR category has enough content now. :smile:

#8

Thank you for coming forward with these suggestions :slight_smile: the team is heavily considering certain measures that would tend to everything that has been brought forward here and elsewhere. We request you to hang on for a little longer, really appreciate your posts and patience.
The community has been very patient and helpful all along. Thank you all.