It seems sqlblog.com is now sqlblog.org 1.. One effect of this is to break outgoing links from dba.se.
In the past, I've tried to be a good netizen 3,4,5,6 and edit posts with dead links to an appropriate new home or archive copy (god bless the wayback machine - RIP MS Connect). Sadly in this case, I'm not even able to submit the suggested edit (
.com -> .org) unless I spam in filler characters to meet the minimum edit length.
In general - these outgoing links were helpful at the time and still can lead to useful additional relevant information. Is there a general solution for finding and repairing damaged links across the network?
I have in mind the Community-bot going about and hoovering up http
-> https redirects for SE, but I'm not aware of any community-supported solution for arbitrary pattern updates.
...as I dig into my own revision history for examples... I did notice this interesting edit history - so... is that a generally supported solution? If so, how does the general (low-rep) community make suggestions to it?
1. as of like like... well... earlier this year way to stay up to date, self...🙄
N.B. this is not an isolated problem: https://blogs.msdn.microsoft.com/extended_events/2010/03/17/extended-blogs-now-cross-posting-to-sqlblog-com/