Hey Nicole, thanks for your answer and your feedback. Showing a message like "This comment has been deleted" would ensure that every user knows that there was an item that others might have answered to or referred to. Just deleting or hiding a comment might create a gap in the conversation.
I like the idea to just hide comments (in terms of a soft deletion), though. It makes revision much easier. We'll keep that in mind and think about it.
btw: discussing this topic in the user community has the advantage that other people could join in. If we would discuss this directly others would miss out ;)
Hey Nicole, we are thinking about removing the option for normal users to delete any comments under their post. This would only be possible for the author of the comment themselves or moderators. In addition we would like to make it possible to report comments specifically and not deleting the comment as such but replacing it with "This comment has been deleted" or something similar. What do you think?
@Jörg: Sorry, I didn't see your comment here. You are right, we changed this in version 11 which is already available on the cloud and will be shortly for on premise.
Hey, sorry for the very late response on this. We are planning to do some changes on deleting comments.
We are thinking about removing the option for normal users to delete any comments under their post. This would only be possible for the author of the comment themselves, admins of the page / workspace or moderators.
In addition we would like to make it possible to report comments specifically and not deleting the comment as such but replacing it with “This comment has been deleted” or something similar.
Since the admin of the page / workspace is responsible for moderating the content within their page / workspace we won't remove the permission to delete comments, though.
What do you think?
Hey Noah, does the external workspace member feature solve your problem? You can invite users via their email addresses to certain workspaces in COYO to collaborate. The users have to sign up and login to COYO after receiving an invitation email. See https://www.coyoapp.com/en/blog/external-workspace-member for more information
Hey Marcus, so in detail the email sender should be also the sender of the email (instead of the system email address)?
Let's see whether other customers would need this feature, too.
Yeah, I heard this idea from other customers as well but unfortunately there are other tasks with a higher priority right now. But let's see whether other customers like to see this getting implemented as well.
To make this more specific: the title and the url would need to be provided in different language, right? The images might be the same in every language?
Nice idea. This could also be quite helpful for blog and wiki articles.
Hey Anne, thanks for your suggestion. That's not possible right now but I'll leave this suggestion open so other interested customers can vote for it.
Can you tell me a bit more about the use case? What should happen with archived form entries? Is it simply a graphical thing?
we are upgrading the emoji picker to feature more emojis and also show a list of lately used emojis. Would that be sufficient for your case?
Hey Josephine, I know this has been the case in COYO 3 but whats the actual use case for this? In my opinion people are used to insert emojis directly by now instead of using characters. And people who choose to use the character version are mostly annoyed if those get "translated" automatically?!
I am personally not a big fan of comments of comments. But what about a feature to answer to comments (like in WhatsApp) or easy quoting comments?
In COYO3 we experienced that hardly anyone really understood the "Top posts" filter and it does not really help with the use case of coming back from holidays.
I like the idea having filters on the timeline, though. Let's see whether other customers are voting for this idea as well.
@sarah: Thanks for your ideas. With the next cloud and enterprise release we will replace links with a button again. So, here we will provide an improvement. Sharing of list items with a preview picture could be quite difficult since there might be 0, 1 or multiple images in on entry - but I still think the idea is quite interesting. We'll take this (together with preview pictures in the list entry) into consideration.
@mark: Thanks for your reply. I'll put your suggestion on our internal roadmap.
I guess you are using the blog app instead of the list app for this since it looks nicer, correct? I am just asking because I know that other customers are rather using a timeline or list app for providing a marketplace.
But regarding your suggestion: would it be sufficient for your use case to add a setting to the blog app that allows users to only edit / delete their own blog articles? Or would you actually need a dedicated app for this?
Deleting images attached to a blog article is (by concept) not possible right now. Because admins could use those images at any other place as well and this would break those links.
That would add quite some complexity to the configuration of the form app. But generally I'd agree that it is waste of space to put 3 checkboxes in columns on their own.
But we'd rather find a solution to improve the widths of the columns to solve this. Would that also be sufficient for your use case?
It would fit into the product and would be a nice feature. Unfortunately, I can't give you a timeline on this because there are many other features with a higher priority right now.
Can you provide a use case? What would this be helpful for?
We are going to make it possible to remove and add new attachments within the “Edit post” dialog.
Hey Christoph, this is still planned but I don't have a timeline, yet.
for ordering uploaded files see: https://community.coyoapp.com/forums/306010/suggestions/36050935
There is also a suggestion for making posts editable entirely:
Hey Thomas, can you tell me a bit more about the use case? Why exactly do you need this?
This is an ongoing discussion for a very long time. There are advantages and disadvantages of having this button.
On the downside users may not understand the concept or simply don't see the button and therefore miss new posts. Additionally, it seems like an unnecessary click for a user.
On the other hand it gives a user control over when to read the new posts and once the concept is understood it is very simple. If posts would simply be displayed without any action the user also might get confused for several reasons:
- the timeline might "jump" because new items are added
- the user might miss new posts because he or she scrolled down and a new item was added during this time
- new items came in during a reload by the user
- a user was on holidays and has 100+ of new posts.
With clicking the button it is clear what a "new" post means. When new posts come in every time when should the "new" badge be removed for older posts?
I personally would vote FOR the button and against removing it because it is a concept that users learned to use for years now and because it makes things clear and simple.
Although, I'll leave this discussion open because I am very interested in what other people think and what ideas are out there that might be better than the button.
Thanks for you response! I edited the title to make it clearer for others to understand. Let's see whether other customers have the same need and vote for it.
Hey Thomas, do you mean a field that automatically increments the number?
I merged these 2 suggestions since they are connected to each other. I like the idea of colleagues being notified if there is a major change / update on a wiki article that others should be notified of. Also there should not be a notification if it is just a minor change.
Thanks for this idea. After we released the new launchpad we will have a look into it.
We are working on a major improvement of the launchpad. We are not planning on adding a widget, though.
But generally: what's wrong about the fullscreen?