jgrim

@m_f@discuss.online has joined d.o to help with all of that. If there are concerns let one us know and we can discuss it… online. 🙃

Yeah, it’s not been easy to moderate, update, & use. If enough people are interested, I’m open to keeping it running as a closed instance. The biggest issue is that there isn’t an out-of-the-box way for me to message all the local accounts to discuss this.

I hosted social.photo, which was a Pixelfed instance.

I had an uptick in users when I started to consider shutting down the site. It was the reason, ultimately, I decided to shut down as soon as possible. The software is awful, and I don’t want to deal with the issues multiplied by growth.

I decided to announce a shutdown by posting and hoping people see it because you can’t make an announcement to users on Pixelfed out of the box. I know there is an admin interface for it, but it doesn’t work.

Afterward, many of my new users told me they came from other instances that shut down.

This trend could be a blip as users create new accounts to migrate as they did before from their previous accounts. I know there is a user interface for this, but it doesn’t work.

Or it could be the terrible spam filter that blocks real users and allows bots. So, real users aren’t there to report bots. This is compounded by an uptick in new hype instances. These are sometimes poorly moderated instances full of bots awaiting returning interest from their owners to get cleaned up or closed.

Or it’s real!

I installed it, and it crashed the browser on every page. I think it has some bugs still to work out. It took me longer than I’m proud to admit to figure out why pages weren’t loading properly and the tabs kept using too much memory.