Skip to main content

Timeline for StackAuth feature requests

Current License: CC BY-SA 2.5

10 events
when toggle format what by license comment
Apr 13, 2017 at 12:25 history edited CommunityBot
replaced http://stackapps.com/ with https://stackapps.com/
Sep 5, 2010 at 19:15 comment added Sky Sanders @jon - first, to get my attention on a post that is not mine, use @code. And my response was to kevin (thus no @jon ;-o).
Sep 5, 2010 at 15:34 comment added Jonathan. Or rather, like there's /users on normal api sites which list all the users and then theres /users/{id}, on the stackauth there could be sites/{state}
Sep 5, 2010 at 15:32 comment added Jonathan. But if you want to remove all the beta sites, then it would be much easier to remove all the sites whose states contain "beta", rather than checking upon each meta whether it's parent site (which as you said could be easier) is in beta and then removing it. Couldn't each normal site have a meta_site (or sub_site) property which is an array, and the array contains what the meta sites currntly do. So in the list of sites you don't get the meta sites at all. The meta sites aren't just linked to the parent, but actaully inside the parent.
Sep 5, 2010 at 7:47 comment added Kevin Montrose @Jonathan - no, because the meta site will always have the same effective state as the parent site, it shouldn't be duplicated like that. In the future it will be easier to tell which site is the parent site, which is a little annoying right now.
Sep 5, 2010 at 7:09 comment added Jonathan. Code poet, is that reference to my comment or Kevin's answer? kevin, I mean in the returned results, Gaming Meta's state is linked_meta, there's no way to distinguish between Meta Serverfault and Gaming Meta, in terms of state. Couldn't the gaming Meta have a state like Linked_meta_open_beta or something.
Sep 5, 2010 at 1:38 history edited Kevin Montrose CC BY-SA 2.5
Answering edit, and acknowledging systempuntoout's answer which really should go without saying but... yeah, its a good thing to point out.
Sep 5, 2010 at 0:59 comment added Sky Sanders with close to 60 sites online and an unlimited number to come in the future, your conclusion that taking the small effort of providing a file hash is less compelling that forcing the developer to download an ever increasing number of files every day in order to assure currency is short sighted.
Sep 4, 2010 at 7:35 comment added Jonathan. (is that once a day per user or developer, I take that it's user). It's not only the bandwidth I'm worried about but the time it takes to download the logos (which ATM is thaat long but there will be many many more logos when the stackexhange sites come out of beta and stop using the same logo. I download them once the first rime the app is run and then I'd like to check at a certain interval(days not minutes) if they've been updated.
Sep 3, 2010 at 23:14 history answered Kevin Montrose CC BY-SA 2.5