Arsse/docs/en/030_Supported_Protocols/030_Fever.md

[TOC]

About

Supported since

0.8.0

Base URL

/fever/

API endpoint

/fever/?api

Specifications

"Public beta" (at the Internet Archive)

The Fever protocol is a basic protocol which has historically been popular with iOS and macOS clients.

It allows marking articles as read or starred, but does not allow adding or modifying newsfeeds. Moreover, instead of being classified into folders, newfeeds may belong to multiple groups, which do not nest.

Missing features

The Fever protocol is incomplete, unusual, and a product of proprietary software which is no longer available. Conssequently some features have been omitted either out of necessity or because implementation details made the effort required too great.

• All feeds are considered "Kindling"
• The "Hot Links" feature is not implemented; when requested, an empty array will be returned. As there is no way to classify a feed as a "Spark" in the protocol itself and no documentation exists on how link temperature was calculated, an implementation is unlikely to appear in the future
• Favicons are not currently supported; all feeds have a simple blank image as their favicon unless the client finds the icons itself

Special considerations

• Because of Fever's unusual and insecure authentication scheme, a Fever-specific password must be created before a user can communicate via the Fever protocol
• The Fever protocol does not allow for adding or modifying feeds. Another protocol or OPML importing must be used to manage feeds
• Unlike other protocols supported by The Arsse, Fever uses "groups" (more commonly known as tags or labels) instead of folders to organize feeds. Currently OPML importing is the only means of managing groups

Other notes

• The undocumented group_ids, feed_ids, and as=unread parameters are all supported
• XML output is supported, but may not behave as Fever did. Its use by clients is discouraged