Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Results of the Social app survey #904

Open
1 of 8 tasks
jancborchardt opened this issue Jun 11, 2020 · 6 comments
Open
1 of 8 tasks

Results of the Social app survey #904

jancborchardt opened this issue Jun 11, 2020 · 6 comments
Labels
1. to develop enhancement New feature or request

Comments

@jancborchardt
Copy link
Member

jancborchardt commented Jun 11, 2020

The core results from the Social app survey are, in order of importance:

  • Make Social compatible for 18 and 19 make 18 compatible #844 make 19 compatible #901
  • Limiting of visibility, private/public (just like Mastodon)
  • Hashtag support, grouping
  • Showing link embeds so they look nice
  • Integration with Notifications
  • Mobile apps are seen as important, and we can reference & advertise Mastodon apps here
  • Recommendations for who to follow (colleagues, people who you worked with frequently, Nextcloud Mastodon account) so you have existing content and also see it as a useful work tool. → Recommendations for who to follow #1078
  • Improved messaging/marketing around also using it as a work tool, not only for private

cc @daita @violoncelloCH @rullzer @jospoortvliet and @nextcloud/social :)

@jancborchardt jancborchardt added enhancement New feature or request 1. to develop labels Jun 11, 2020
@StCyr
Copy link
Contributor

StCyr commented Jun 11, 2020

Hi @jancborchardt

May I ask where this survey comes from?

I'm asking because I believe some of the points are already solved:

  • Limiting of visibility, private/public (just like Mastodon)
  • Hashtag support, grouping

@jancborchardt
Copy link
Member Author

Yes, sorry @StCyr this survey was running between May 27 – 9 June and got 159 responses.

Keep in mind the possibility of bias due to the audience of the survey. We primarily asked for people to fill it out via the Nextcloud blog and the @Nextclouders Twitter account, which means that many respondents are likely to be people who know about Nextcloud, use it already, or are otherwise more technically apt.

But also, many people might not know about Social yet, so are not aware of what exists already. The questions were also to gauge how we are standing with our current features in comparison with other solutions, and what is important to polish. :)

Does that explain it?

@StCyr
Copy link
Contributor

StCyr commented Jun 22, 2020

Hi @jancborchardt

Thanks for your answer. It's a shame I didn't see that survey but anyway...

I just want to mention that I was hitting serious performance issues after using Social for a few months, with some DB queries taking up to 10 seconds or more (From memory I believe these were some WHERE <column>='%foobar%' queries on tables with tens of thousand of rows).

Are there any plans to review the DB 'structure by any chance?

PS: For the record, here's a link to an already solved issue that I've reported in the past regarding a DB structure issue: #737. I believe there are some other such issues still lurking around

@jancborchardt
Copy link
Member Author

@StCyr oh ok – could you open a new issue for that database issue (or multiple ones if they are separate)? :)

@ArtificialOwl
Copy link
Member

Hello @StCyr, glad to hear from you as I could not get any news from Telegram.
As you can see, the project is back on track.

Alpha3, that should be released today or tomorrow, include the first part of the fix: better structure.
The second part that is generating backup of oldest streams yet needs to be done.

I hope you're ok, please contact me on Telegram !

@jancborchardt jancborchardt pinned this issue Sep 10, 2020
@Mannshoch
Copy link

Any news on this APP?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants