Show newer

Now using an trigger to prevent account updates to the qua.name demo account.

Even with such a small instance, there's a remarkable amount of attempts trying to change
the demo username and/or password.

The trigger is a nice solution to this, it let's me use the writefreely 'as is' and it
is a silent ignore on any attempt.

I have enabled a 'demo' account on instance qua.name so people do not need to create accounts to try things out.

People seemed to be creating accounts just to try things for a bit and move on. This is obviously fine, but leaves accounts lingering and skews the statistics. The demo account is a bit of an experiment, as we all know what typically happens with demo accounts, but let's see what happens.

Mastodon.nl

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!