Tim Stone

1,847 reputation

616

bio	website
	location	Delaware
	age	24
visits	member for	2 years, 4 months
	seen	2 hours ago
stats	profile views	32

When I'm not working, I have a tendency to meddle in bug reports on Meta or take part in writing userscripts for the Stack Exchange network which add features that sometimes get implemented natively. Here's a few you may be interested in:

I've also been known to occasionally break (and sometimes fix!) the Data Explorer, and to busy myself with maintaining the Election Statistics page.

	1,847 reputation	bio	website		visits	member for	2 years, 4 months
616 badges		location	Delaware		seen	2 hours ago

summary answers questions tags badges favorites bounties reputation activity

118 Actions

suggestions reviews revisions comments badges posts accepts all

Jan 30	comment	SE Modifications — Username autocomplete in comments, inline revision source, and utility links @AnnaLear Now comment timestamp links are natively supported.
Jan 25	answered	Is the display name meant to be escaped HTML in the 2.0 version of the API?
Jan 20	comment	API endpoints do not set Access-Control-Allow-Origin, so CORS requests fail Not that it invalidates this request in any way, but note that the API does support JSONP.
Jan 13	comment	SE Modifications — Username autocomplete in comments, inline revision source, and utility links @AnnaLear Ah, I may have been unclear. They didn't add links to the comment timestamps, but they did natively implement the scripting that shows you hidden comments if you click on a link to them from your profile (or if you share a link using the userscript's comment timestamp linking feature).
Jan 11	awarded	Yearling
Dec 22	comment	SE Chat Modifications — Keyboard navigation and commands for chat @NullUserException Updating to the latest should fix the issue for the moment.
Dec 18	answered	How do I get a GreaseMonkey/UserScript to interact with the Live Preview?
Dec 6	comment	SE Modifications — Username autocomplete in comments, inline revision source, and utility links Awesome. :) And yeah, it'd be nice if browsers had a way of syncing userscripts, but even Chrome's syncing feature doesn't handle that as a result of its implementation. We are hoping to make the update process a bit more apparent though, so at least the script will remind you when it's out of date.
Dec 6	comment	SE Modifications — Username autocomplete in comments, inline revision source, and utility links Click the install link in the question again and it should replace your current version with the most recent on next page load.
Dec 5	revised	SE Modifications — Username autocomplete in comments, inline revision source, and utility links added 68 characters in body
Dec 5	comment	SE Modifications — Username autocomplete in comments, inline revision source, and utility links I haven't had a chance to properly fix this yet, but I've gone ahead and disabled it for now while I'm working on it.
Dec 5	comment	SE Modifications — Username autocomplete in comments, inline revision source, and utility links Both of these should be fixed now.
Nov 29	comment	SE Modifications — Username autocomplete in comments, inline revision source, and utility links The "change into search term" feature quotes the tag term in the current search query, which is a different behaviour than you'd get from clicking the tag. It's primarily useful if the term is automatically converted to a tag by search, but in your particular example it's clearly just broken. I'll fix that and address the UI concerns that you mentioned, thanks for the report!
Oct 21	comment	SE Chat Modifications — Keyboard navigation and commands for chat Note: Chat upgraded from jQuery 1.4 -> 1.5, which caused several things to unexpectedly break. Updating the script to the latest version will resolve these problems.
Oct 20	revised	Stack Exchange Elections Statistics Page Fixed links
Oct 20	suggested	suggested edit on Stack Exchange Elections Statistics Page
Oct 8	awarded	Nice Question
Oct 7	answered	How to get “inbox” items
Sep 28	comment	Draft Specification for API v2.0 Makes sense. I sometimes wish the other routes could return Markdown too, but I guess that's more than likely a narrow userscript-related usecase.
Sep 27	comment	Draft Specification for API v2.0 Partly related to all of the fields being HTML-safe, will `/users/{id}/timeline` continue to return Markdown instead of HTML?