GET /api/v2/news/3/?format=api
HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept
{
"id": 3,
"url": "https://swarfarm.com/api/v2/news/3/?format=api",
"title": "What's changed lately",
"body": "After coming back online from the loss of the old server, the first order of business was ensuring that the loss of all data could **never** happen again. This was accomplished by:\r\n\r\n1. Owning all server resources directly\r\n2. Nightly full database snapshots, retained for 90 days\r\n3. Hot-Standby database server running in a different datacenter\r\n4. Backup job reporting and alerts\r\n\r\nAs I detailed previously, the server resources used to be completely donated and all I had to pay out of pocket for was the domain name. That is quite a different story now, but well worth it to ensure that the rug won't be pulled out from under us. To cover these costs I have set up a [Patreon](https://www.patreon.com/porksmash) account. I greatly appreciate those who have contributed to the past through donations, and Patreon will help me continue to devote resources and time to development in addition to covering the monthly costs.\r\n\r\nDespite outward appearances, development has never really stopped on SWARFARM. The majority of recent work has been in the background. I provide [an API](https://swarfarm.com/api/v2/) for monster and skill data, which powers many Discord bots, monster data in the SWOP rune optimizer (<3 Xzandro), and even other websites. This API has been expanded to include most of the data available on the website, including user profiles, and will eventually power the complete rewrite of SWARFARM, which can be previewed [here](https://alpha.swarfarm.com/bestiary).\r\n\r\nI am still working to bring the data logging back online as the first priority. The loss of all of the data provided a bit of an opportunity to correct a lot of early decisions that proved to be difficult to work with.",
"created": "2019-02-13T18:51:13-08:00",
"sticky": false
}