We can, but only if we’re provided with a link to it by one of the participants. For instance, some users may have had PM conversations with mods where other mods have also contributed, which is possible because the first mod has shared the link.
We can’t just guess the link or something, and it’s not enumerable (look at the URL, it’s long and complex). Even if we could, we don’t care or want to.
Moderating the site is sort of like being a nurse; there’s a brief period at the start when the thought of seeing people’s privates might be vaguely titillating in a theoretical sense, but that sort of thing doesn’t last long when it’s up against the daily reality of urine, blood, and vomit.
Now that I think about it, moderating the site is exactly like being a nurse, only people die slightly less often.
Can you tell how many users are making use of the site’s API for things like customized image downloaders, or other ways of accessing the site’s content? Following that, how much of the userbase customizes their experiences like this?Most of our traffic is via the main site, the API counts for a sizable but comparatively tiny fraction of traffic IIRC.What are the most common API-made customizations, for lack of better phrasing, that are made? I imagine that mass-downloaders would be too much of a drain on bandwidth, and would probably get deleted or banned. Is it something like changing the site’s display such that every image is displayed as a certain resolution, with a descriptive filename rather than “medium_1”, or whatever the default image display’s filename is?Are there any further tinkerings and streamlinings that you imagine for the site, if you had infinite time, and didn’t need to worry about the complexity of the code upkeep? Just straight-up extra features or changes in how images are displayed, like Sankaku Complex’s autopaging feature, for example.Given that new bugs are always cropping up for one reason or another, can you give an example of a typical bug that you find, isolate, and fix? I’m trying to get an idea of how tricky general site maintenance is, and how much more of a pain in the neck it is when it’s the same basic site that serves a lot of content to a lot of different users.
What are the most common API-made customizations, for lack of better phrasing, that are made?
Are there any further tinkerings and streamlinings that you imagine for the site, if you had infinite time, and didn’t need to worry about the complexity of the code upkeep?
Given that new bugs are always cropping up for one reason or another, can you give an example of a typical bug that you find, isolate, and fix?
Derpibooru costs over $25 a day to operate - help support us financially!