Custom Query (1174 matches)
Results (286 - 288 of 1174)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1071 | fixed | Translations can't compile | ||
| Description |
Translations can't compile currently thanks to Babel not knowing how to handle Lojban. See #1070 for a more permanent solution to this (making so we can actually use the translations we're being generously provided), but as a stopgap measure we might have to skip compiling this file, or use gettext (if available) to compile it. |
|||
| #1069 | fixed | API doesn't support deleting media | ||
| Description |
In pump.io you can delete media by performing a "delete" activity: {
"verb": "delete",
"object": {
"id": "https://gmg.theperplexingpariah.co.uk/api/image/myid"
}
}
You can also do this by sending a HTTP DELETE to the API endpoint. |
|||
| #1066 | fixed | Dianara gets "Invalid Oauth parameter" when passing 'count' or 'offset' params | ||
| Description |
When trying to fetch a feed from Dianara, like /inbox/major it works great. However, if Dianara adds parameters to the call, like 'count' to get more activities in one go (the url then being like "/inbox/major?count=30", the server returns "{"error": "Invalid oauth prarameter."}". I'm unsure if there is something Dianara is not doing right, but this works ok with Pump.io servers. The OAuth header is generated by QOAuth. I know that, when adding those parameters to the call, those are reflected not only as part of the URL, but as fields in the Authorization header, for some reason. Maybe that's what's confusing GMG? The fact that there are unexpected values in the Authorization header. |
|||
