That was scary and exciting. Response seems competent and transparent. I ❤️ this place.

I think this is a strong reminder: We shouldn't put all our eggs in one basket. This will happen again. Unlike Reddit, we don't need to concentrate all communities on one instance. We should all make an effort to spread out. Some other general use instances are:

• https://lemm.ee
• https://lemmy.one
• https://sh.itjust.works
• https://sopuli.xyz

Again, for those new, you can post content to any of these instances and interact with content from other instances at the same time, just like you can send an email from your Gmail account to your ProtonMail account.

So, do we change passwords, esp those who logged on during the attack? (I created this acct right before the attack happened tho.)

Despite the fact that Lemmy is a fairly new piece of software, which makes these issues more likely, I am really grateful for it being open source, and I really appreciate this level of transparency.

Thank you for the transparency and swift solution!

Any truth to what I've heard this may have been done by a group we defederated with?

At least now we can mark off the "disruptive website defacement attack" line on the checklist of (relatively) new website growing pains. Better to have them make lots of noise and get fixed quickly than quietly do sneaky things in the background.

Thanks for fixing and being so open about it

Well done all involved. Sounds like it was caught and mitigated quickly

How does this impact those using mobile apps like Jerboa or Liftoff, instead of the website directly?

I just disabled whole "/admin" section on my instance and added nice message 😆

Thanks for the transparancy about this.

The quick fix is much appreciated, thank you and everyone that helped for your hard work!

On Liftoff, I had to clear cache and storage in order to log back in. Still having issues with the website on Chrome, which keeps telling me I'm not logged in after clearing cache and logging back in.