This issue is already quite widely publicized and quite frankly “we’re handling it and removing this” is a much more harmful response than I would hope to see. Especially as the admins of that instance have not yet upgraded the frontend version to apply the urgent fix.

It’s not like this was a confidential bug fix, this is a zero day being actively exploited. Please be more cooperative and open regarding these issues in your own administration if you’re hosting an instance. 🙏

  • Is the project small? Yes.

    Did it explode in popularity leaving the devs overwhelmed? Certainly.

    Do I expect them to strictly follow established ITIL incident management? No.

    Do I expect them to communicate in a consistent way when an incident happens? Yes.

    I agree the primary developers should be left to fixing the problems but there are enough active members of that project that someone could have handled communication in a more concise and official way. I don’t consider random posts in asklemmy or selfhosting by random users just guessing to be a substitute for that.

    If the project is going to persist and grow it needs to get better at that. Pointing it out isn’t shitposting.