#ActuallyAutistic web dev. Does front of the front-end. Loves perf and minimalism. Prefers HTML, CSS, Web Standards over JS, UX over DX. Hates div disease.
Then there is the under utilized 410 Gone. The biggest issue with 410 is that you often need a human to decide that "this resource will never come back again" and not many think about lifecycling their urls. I'd say it is a good idea for most content to have a lifecycle, and to think what happens once the content will no longer be available. Possible solutions are to redirect to a newer resource (such as newer version of a product) or to indicate something as fully gone but that it did exist at one point. This is a huge difference to 404 which is very generic and you can't tell if it was correct in the past or you have an incorrect link or why it doesn't work.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Then there is the under utilized 410 Gone. The biggest issue with 410 is that you often need a human to decide that "this resource will never come back again" and not many think about lifecycling their urls. I'd say it is a good idea for most content to have a lifecycle, and to think what happens once the content will no longer be available. Possible solutions are to redirect to a newer resource (such as newer version of a product) or to indicate something as fully gone but that it did exist at one point. This is a huge difference to 404 which is very generic and you can't tell if it was correct in the past or you have an incorrect link or why it doesn't work.