OK, but you understand that nobody here has anything to do with that, right? This was just some event that an instance admin put on. Maybe you should run the next “Lemmy Place” and use rules that you feel are appropriate?
OK, but you understand that nobody here has anything to do with that, right? This was just some event that an instance admin put on. Maybe you should run the next “Lemmy Place” and use rules that you feel are appropriate?
Ahh, ok… so it clearly wasn’t some sort of centralized “Lemmy” thing (I was wondering why I, as an instance admin, hadn’t heard anything about it until after the fact). With that in mind, have you considered posting your criticism over there?
Sorry, I don’t know who Grant is… could you be a little more specific?
Honest question: who was running this “Lemmy Place”?
Respectfully I don’t think what I’ve written here is appropriate for official documentation, mostly because I don’t know what I’m talking about. My hope is that somebody who DOES know what they are talking about could use this as a starting point for updating the documentation.
Awesome, thank you!
edit: you may want to specify that it’s lemmy-ui
that has the update, not lemmy
.
I’m curious why the UI update to 0.18.2-rc.1 isn’t mentioned anywhere in this thread. I understood that updating the UI was a fix for this exploit.
lemmy.ml is indeed the instance run by the developers of lemmy. But this “lemmy place” that you’re complaining about doesn’t seem to have anything to do with lemmy.ml or the lemmy devs… It was just an activity that one instance admin put on, as far as I can tell.