Old API Deprecation Notice

@Joey  
Gasp are you a fellow Firefox user?!

@Background Pony #3E8E  
Yes

@Marker  
I messed up the Next one a little, it needs to be reverse sort order (ascending instead of descending). This is what I get for doing brain-related things at 2am.
 
Next: https://derpibooru.org/api/v1/json/search/images?per_page=1&q=oc%3Agreg%2C+id.gt%3A152470&sf=created_at&sd=asc  
Prev: https://derpibooru.org/api/v1/json/search/images?per_page=1&q=oc%3Agreg%2C+id.lt%3A152470

@Damaged  
Ahh, I didn’t catch that either, fixed.
 
EDIT: I just realized that the user’s API key is required for it to work properly with their personal filter and any of the “my:*” queries. Which means I’ll have to use the GM_* api to store the key instead of keeping it in localStorage like the other settings, and requiring an additional set up step for new and existing users (like, all 4 of them). Now I’m debating whether doing things the “right” way is worth all the extra complexity. Hmmm…  
EDIT2: Both, both is good.

Is random_image not available anymore as a query parameter in the search API? What about lists?

@joedeeloo  
You can use the following instead:
 
&sf=random&per_page=1

@MagpulPony  
I’m starting to think that it will be an April Fools joke! Literally!

@Background Pony #EE98  
It’s February…

I read it “old API Appreciation notice” for some reason

@Mercurial64  
Appreciate the old API

Is there a new way to get the artist tags of a user?
 
My current work flow to get images of an artist which uses my site:
 

@Bastler  
We don’t currently have a way to get user pages in the API. That will need to be fixed. Also, it would probably be better to just have the user drop a link to their userpage rather than get their API key.
 
I’ll add this to the to-do list.
 
Edit: Added to to-do list
 
I’ll take a crack at implementing in the next few days.

@Bastler  
Got that coded. Waiting for review process, merge, and push to the server before the endpoint will be live.

@Bastler  
Endpoint is live.
 
https://derpibooru.org/api/v1/json/profiles/:id
 
Example:  
https://derpibooru.org/api/v1/json/profiles/386691

I already posted in the other thread, but I’m not sure if my post was seen. All the issues are still there, so I’m copying my post from there:
 
1. The new API no longer returns the mp4 representation for images uploaded as WEBM.
 
Example: Old API, New API
 
For images uploaded as GIF, the new API still returns both the webm and mp4 representation as before (Example).
 
Is this intended behaviour? WEBM still isn’t as widely supported as MP4, so I’m relying on the MP4 representation (in my case sending the image to Telegram, which supports sending MP4 videos but not sending WEBM videos). Of course I could just change the file extension in the URL, but that would be quite hacky and I’d have to check if the MP4 actually exists each time.
 
2. I noticed a second issue. The API now always returns the mp4 and webm fields for GIFs, even if the video versions don’t actually exist on the server (for old uploads where no video version was generated). The URLs just return 404. This was not the case before, it would just not include the video representations in the response. However, it seems that even the old API now returns those non-existant representations.
 
Example: Old API, New API
 
3. And a minor issue with the API documentation, the format field of an image response can also return jpeg (instead of jpg), depending on the original file extension of the image. The behaviour is the same as with the old API, it’s just missing from the documentation.

@Rene_Z  

@Damaged
 
Would it be possible to also give out the tag slug of the artist tags?  
Currently the tag ids are not usable for any new api requests.

@Bastler  
https://derpibooru.org/api/v1/json/search/tags?q=id:2874
 
You can get tag data from IDs just fine.

@Luna  
2. The fix you should take is to generate the missing video representations for these files.  
3. The fix you should take is to change all the usage of jpeg to jpg. (Note that this is a nontrivial data migration which requires renaming files.)

How long will the scheduled downtime last?

@Squeakiergerm8  
There generally isn’t any downtime when updating code.

I saw that the site is going down at 3/9/20. Is this because of the API upgrade? And I do use Firefox.

@Squeakiergerm8  
@theawesomeguy98201  
From the first post in this topic:
 

@Damaged  
Ok, my bad. I just see things like that and get concerned.

@Squeakiergerm8  
Likely an hour. Scheduled a bunch of package upgrades and a database upgrade (PG 11 -> 12).