![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/1f910de9-62b5-43a9-8c93-94821c945577.png)
Yes and no, it is your instance’s backend that is responsible for this behavior. Once your instance is up-to-date, you should not see these old results any more. No need to wait for all other servers 😉
Yes and no, it is your instance’s backend that is responsible for this behavior. Once your instance is up-to-date, you should not see these old results any more. No need to wait for all other servers 😉
Wow, that is incredibly annoying! I can’t imagine they wouldn’t get forced to take it down.
Are you expecting a developer to test everything every time they commit? Thoroughly testing even a small application or feature subset will take up quite a bit of time. You also want devs to commit often, so it is easy to roll back an approach that didn’t pan out, or just to go back and figure out what change caused something to stop working. If you end up committing only a few times per week because everything needs to be thoroughly tested, I’m not convinced it is a good approach.
FYI, this is an attempt at humour, clearly “/s” is needed on lemmy as much as it was on reddit 😅
What would be the probability of u/spez being behind this attack, in an attempt to sabotage lemmy?
Thanks for the reminder, I still had one of those messages waiting for me…
Which programming language will you use?