@JourneymanGeek Thank you. Now that I notice that the user numbers are separated by a value of two it supports the theory that one account was created to promote the other; especially if they share IP addresses.
@bad_coder Can you please clarify how your edits to organize links into a list are "ease of reading edits"? They don't change the rendered output at all, so are you talking about "ease of reading" for editors of the post? meta.stackexchange.com/posts/371933/revisions
As an editor, I tend to find inline URLs easier to read in some cases, since the link is right in that spot, depending on what I'm editing.
I might also mention that the new editor, in its current form, automatically edits footer links into inline links, so if a user who's opted into that edits one of these posts, your edits will be overwritten.
@SonictheAnonymousHedgehog actually pretty simple, from experience I read along with the text as I edit it. If you have a bunch of URLs inline the prose becomes much harder to read. It's also easier to simplify the URLs (adding SSL, updating addresses that have changed, or removing needless slashes at the end) if they are in a list.
@SonictheAnonymousHedgehog I haven't tried the new editor but if they are in-lining links automatically by all means someone post an FR to stop doing that.
@bad_coder I guess I was just thrown off by the phrasing there. "Ease of reading" implies to me that you're making the post easier for non-editor readers to read, and I didn't see how your edit fell into that.
Then there's the half-full/half-empty argument. Either have the links in a list (the better option) or have them all inline. The only reason to have an inline link is for the title to auto-render, so you don't have to paste it in and risking the title changing on the target post (but that's a CommonMark short coming as it's implemented, there should be an option to automatically render the title even if you are using link references.)
@SonictheAnonymousHedgehog ok.
@SonictheAnonymousHedgehog I only use three introductory sentences, "ease of reading edit", "search edit" or a combination of both. In those cases it makes it easier on the editor (the same way using the language code js instead of javascript makes things mentally easier to read.)
Maybe consider rephrasing that to "ease of editing edit", if those edits are primarily aimed at editors rather than readers?
@bad_coder Yeah, I disagree with that strongly, especially since link labels can be custom text and not just numbers in order, and the new editor will wipe out those custom labels.
@SonictheAnonymousHedgehog that's an interesting idea, but then I'd be at increased risk of no one understanding the edit summary. (I actually developed the habit of the introductory sentence on SO because it tended to be a preemptive counter-argument to the "no improvement" rejection reason, and it worked.)
@SonictheAnonymousHedgehog that's completely wrong, the editor is working against the functionalities CommonMark makes available, and the more experienced editors will be the worst affected. Over time that will also create poorer editing habits in the user base.
@JourneymanGeek the fabric seems to be good quality.
@bad_coder some of the shirts in the 'middle' were pretty thin. I think my AU shirt has a hole, while my original SU and SF shirts are going pretty good after over a decade, other than maybe some fading and collar fraying...
Kinda mixed on the socks... they're neat but I don't wear socks if I can avoid it
and the pairs I do wear have the sides labelled which is the greatest thing
