GregZone

@tindie Don’t worry about the period that should have been a comma. I think the message was nicely conveyed. Also, I know all about being a perfectionist with these little things! LOL
Also, (just saying), it doesn’t take a web developer very long (at all) to change the content of a 503 Error Page. 🤓

@tindie Thanks for the longer statement.
Q. If due to new ownership (from 14 April), and the new owners “are genuinely excited about Tindie and what the platform can be” (which is great news, by the way), can you also advise when the new owners intend to make a public statement?
I would think it would be in their best interests to do this sooner, rather than later!
Ideally, the 503 Error Page would simply be replaced with a more descriptive message about what is happening and what is coming! 🤓

@tindie My only question is: What is the (honest & genuine) expectation of when Tindie will be live again?

I thank you for your posts, but without any actual, first hand, technical detail of what the problems are (that “they” are working to resolve), we are all in the complete dark!

As long as this appalling lack of official communication continues, I think Tindie will have lost significant support and trust within the community (if not already)!

@tindie Yes, thanks for this more detailed update. It seems like Mastodon is the only place to get this update?

As others have alluded to, I can’t state how bad this event is for the future of Tindie.

All that was needed, to avoid the significant loss of trust, was some appropriate planning and clear communication, starting from before the maintenance event!