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

Leverage a demo user for writefreely to decrease lingering user accounts #150

Closed
mrvdb opened this issue Aug 1, 2019 · 1 comment
Closed

Comments

@mrvdb
Copy link
Collaborator

mrvdb commented Aug 1, 2019

Running a writefreely instance for a while shows that many users just register to have a short look at writefreely and then never post anything. This is of course fine, but creates quite a bit of 'noise-data'.

If we could leverage a 'demo' user and enourage visitors to use that before registering, this would have a number of advantages:

  • casual exploration of the system is even easier than it is now
  • we could provide some content for them to look at to get familiar with the system and prefill an installed instance with 'showcase content' (probably refreshed at certain intervals, this could be as simple as some sql-script running under cron-like control)
  • the number of users and posts will be qualitatively better on sites like https://the-federation.info
  • it's easier to support users of the system by using an account both user and administrator can use to work something out.

Alternatively, at least allow users to delete their created account, but perhaps that should be a additional issue.

@thebaer
Copy link
Member

thebaer commented Aug 9, 2019

Thanks for the input! I like the idea of a demo account, or some temporary way for people to try out an instance.

Let's continue discussing this idea on the forum, where we discuss other feature requests. Closing the issue here since it isn't a bug.

@thebaer thebaer closed this as completed Aug 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants