« first day (891 days earlier)      last day (340 days later) » 

7:02 AM
in Data Explorer Discussions, 4 hours ago, by Tim Stone
6
A: Provide convenient way to get the current site URL in SEDE query

Tim StoneWell, since we already support arbitrary autolinking if your results have something like http://example.com/|link text I thought the easiest way to solve this problem was to introduce a site:// protocol so you could return a column 'site://posts/' + CAST(Id AS nvarchar) + '/revisions|History ...

I think I whined about this before in some other context, but that URL should definitely not be a link there. Why is the autolinker even run on that text?
 
because the information "this part is code" is stripped way earlier
(in fact the autolinker is client-side in chat)
 
Right, I just meant in the sense of "Why should the autolinker look at the text in oneboxes?", but I forgot about it being client-side.
So I suppose that's the answer, it just indiscriminately looks at message contents.
 
yeah
e.g. in this onebox:
"When we come up with clever hacks & polyfills for dealing with oldIE, we shouldn’t feel pleased. We should feel angry" http://adactio.com/journal/5964/
you can't argue that linking is good
 
Yeah, that's fair.
 

« first day (891 days earlier)      last day (340 days later) »