Complete STIQRA manual

Managing feeds and refresh

A feed is a website's list of recent articles or episodes. Some sites call it RSS or Atom. You do not need to find a special link to get started: try pasting a public website address, and STIQRA will look for a supported feed.

STIQRA can only add feeds that are available over HTTPS without signing in. Private feeds that ask for a username, password, or other sign-in information are not supported. STIQRA reads the text publishers include in their feeds; it does not fetch a linked webpage to retrieve the full article.

The first-run tour offers the public XMAKYNA company feed as an optional, initially enabled starter source. You can switch it off in onboarding or later in Settings → Source Settings → Subscriptions. When no independently chosen source is enabled, a dismissible Add sources reminder shows this same path and lets you change the XMAKYNA setting. It may recur after a dismissal until your first non-XMAKYNA feed is enabled.

Add a feed

  1. Open Settings → Source Settings → Subscriptions and enter a public HTTPS address in Website or feed URL.
  2. If STIQRA finds more than one feed, choose the one you want. Review the source name, refresh, image, and enabled settings.
  3. Add the source after it passes the checks. If an address cannot be used, STIQRA shows an error and does not save it.

A normal website address or a direct feed link can work. Some public YouTube channel-ID links are also supported, but channel handles and names are not. A publisher's site may have no compatible feed even when its homepage opens normally in a browser.

The free app allows up to 5 enabled sources that can refresh. Disabled sources do not use a slot; STIQRA Premium allows more active sources. After adding a source, use its More → Rename… option in Subscriptions to change the name shown in STIQRA. Renaming does not change the website address or its articles.

After adding sources in Settings

After Check and add, STIQRA shows which websites were added, which were already present, and which could not be added. If at least one was saved, choose Done to open Preparing your sources. This shows whether STIQRA is checking newly added sources for articles.

Only new, enabled sources set to refresh automatically are checked at this stage. A source can be saved successfully even when its first article check is delayed or does not run. To check all enabled sources yourself, use Refresh or pull down in the Feed. If preparation cannot be confirmed, choose Retry preparation; this checks the saved list without adding the sources again. Closing the sheet does not cancel work already accepted by STIQRA. If preparation stops before every source has been checked, STIQRA does not mark it complete merely because another source already returned articles. You can check the individual source status and retry preparation.

Removing a feed

Open Settings → Source Settings → Subscriptions, choose a source's More → Remove, and review the confirmation. Removing a source permanently removes its exclusive local articles and source-specific history. Articles also provided by another source stay available.

STIQRA checks that removal was saved before updating the subscription list. The feed-selection sheet uses the current subscribed-source list; a removed source should disappear, and an empty list stays empty rather than restoring bundled example feeds. Your Feed may briefly show as unavailable while its hidden-article checks catch up. If you see Retry verification, use it rather than removing the source again. A storage failure may leave some cleanup unfinished; do not try to fix it by deleting app files manually.

Recovering subscriptions after an older installation or storage error

Subscriptions saved by a version older than the provenance-safe feed format remain visible as Pending validation after a supported upgrade. They do not fetch automatically. In Source Settings → Subscriptions, choose Validate for each source you want to approve under the current public HTTPS policy; old bundled sources are not restored as trusted network origins. A protected local copy of the older subscription list is retained for recovery.

If Subscription storage unavailable appears, the app could not safely read your existing subscription file. It has not replaced that file with an empty list. Choose Retry after local storage access returns. If the file was created by a newer STIQRA version, reopen it with that version rather than resetting the list in an older version.

Free active-source allowance

Only refreshable sources that are currently enabled consume the free allowance. Disabled sources, pending or failed validation records, and non-refreshable records do not count. You can therefore save a newly validated source with Start this source enabled turned off even when all 5 active slots are in use; enabling it later requires an available slot or Premium.

Source Settings → Subscriptions shows the active count against the allowance, such as 0 of 5 through 5 of 5. Enabling a sixth active refreshable source is blocked with the subscription explanation. If a downgrade leaves more than 5 approved requested-on sources, STIQRA preserves all saved settings but only the first 5 eligible source IDs (stable identity order) can actually refresh. Extra sources display Locked · Premium required, and neither manual nor automatic refresh fetches them until renewal. The saved enabled switch represents your intended setting, not a guarantee of current network permission. When Premium renews, eligible requested-on sources resume automatically. Disabling or removing active sources remains available, and reducing the active count below the cap frees capacity for another source.

Feed images

STIQRA can show images supplied by publishers, including supported JPEG, PNG, and static WebP images. If an image is damaged, animated, or too large to process safely, STIQRA may leave it out. You can still read the article without its image.

Which feed addresses work?

STIQRA accepts public HTTPS addresses without sign-in details. It checks addresses, redirects, and the content they return before adding a source or refreshing it. Local-network addresses, insecure links, and pages that are not supported feeds cannot be added. STIQRA does not run website scripts to find articles.

A feed may fail because the publisher's server is unavailable, its security certificate is invalid, its response is too large, or it does not return a supported feed. You can try again later or ask the publisher for its public RSS or Atom link. A publisher's website working in your browser does not guarantee its feed will work in STIQRA.

For more about how STIQRA handles outside content, see Privacy, security, and data.

Small differences in how the same address is written, such as an extra # section at the end, do not create a second subscription. Different paths or query options can still identify different feeds.

Article dates after refresh

When a publisher supplies an article's publication date, STIQRA shows it and uses it when sorting by date. A website's general "last updated" time is not treated as the date of every article.

If an article has no usable publication date, STIQRA remembers when it first found it. Refreshing does not reset that first-seen time or your read status. Once an article or episode is saved, subsequent feed refreshes keep its original publisher-supplied content and publication date; later publisher edits to that same address are not imported automatically. A newly discovered article or episode can still be added on refresh. STIQRA cannot recover a missing date for an article the publisher no longer provides.

Source types

STIQRA labels each checked source as RSS or Atom (a website's article updates), Podcast, or Video channel. You can see the type in Settings → Source Settings → Subscriptions and search by it with @source-type: or @kind:. Subscription backups also include the type.

Older sources may still be labelled RSS or Atom until they are checked again. A source label does not provide access to private accounts. Social-network connectors and importing newsletters from email are not supported.

Newsletter support

You cannot add a newsletter by email address, import an .eml email message, or connect a mailbox. If the publisher also offers a public RSS or Atom address for its articles, you can add that instead.

Publisher media metadata

Some sources include podcast episodes, videos, or attachments. STIQRA can show details the publisher provides, such as an episode's duration, artwork, transcript, or chapters. Not every article has playable audio.

Refreshing a source checks the publisher feed for newly listed articles or episodes; previously stored episodes are not re-imported even if their descriptions or media metadata change. Refreshing does not download episodes, transcripts, or other attachments. Downloading supported publisher audio starts only when you choose a download or playback action. Audio links must use public HTTPS and work without a login. Broken, unsafe, unsupported, or excessively large source data can be rejected rather than shown as an empty source.

STIQRA may support a YouTube channel's public updates by its channel ID. Handles, private videos, sign-in-only content, and extracting articles from webpages are not supported.

Import or export OPML on iOS and macOS

Open Settings → Source Settings → Subscriptions and choose Import OPML or Export OPML. An OPML file contains a list of website subscriptions. Use Files on iPhone or iPad, or the file picker on a Mac. Cancelling leaves your subscriptions unchanged.

Import opens Review OPML Import before anything is saved. Check which entries are valid, skip duplicates or unsupported addresses, then choose Import Selected. Imported sources stay marked Pending security revalidation and do not refresh until you validate and enable them. Importing a file never grants automatic access to its websites.

Before exporting, review the websites and folders included in the file. OPML exports do not contain articles, passwords, or reading history. A source address can still reveal what you follow, so keep the file private if needed.

Preserved or failed subscriptions

Sources that are disabled, pending, or failing a check stay visible in Subscriptions, but they do not refresh until they are allowed again. Use Validate on a pending or failed public source to check whether it can be enabled. An imported source must be reviewed and validated before it can start updating.

For more detail, open the source's Security row and select its information button. The sheet shows the website address, current access state, and reasons a check may have failed. Article images are checked separately from the source itself, so an unavailable image does not necessarily mean the source is broken.

Why STIQRA does not fetch through XMAKYNA

STIQRA's normal reading path is direct: the app connects to approved RSS/Atom publisher hosts. XMAKYNA should not have to fetch every article for you.

That design matters. If every source had to pass through an XMAKYNA service, then an XMAKYNA outage, rate limit, account issue, or policy change could make your entire reading setup unusable. Direct feed access keeps the failure domains closer to the web itself: one source may fail, another may keep working, and the app can show you which source is having trouble.

Several publishers can use the same hosting or network provider. If that provider has a problem, more than one source may stop updating. Feed Stats can help you see which sources are affected.

Source visibility by section

Some settings let you decide which feeds contribute to specific sections. This means a source can be visible in one context and hidden in another.

If a source appears in Sources but not in Feed, or vice versa, check source visibility settings for that section.

Manual refresh

On iPhone and iPad, pull down from the top of the Feed until the refresh indicator appears, then release. Or choose More Options → Refresh. Both check the websites you follow for new articles. You can keep reading while the check runs.

A neutral spinning arrow appears beside the item count while feeds are being checked. If articles are saved but their safe presentation is still pending, the arrow remains in place as a static status indicator; it does not repeatedly shrink or expand as the app processes updates. It is not a button to apply updates. Articles saved by fast sources can appear before slower sources finish. When you are at the top of the Feed and not scrolling, newly accepted articles appear at the top; if you are reading farther down, STIQRA keeps the same article at the same place on screen. If you start scrolling before updates are ready, their insertion waits until the gesture settles. Changing section or opening another screen does not create a separate approval step. Later arrivals are checked and added in their own verified batch. Pull down again or choose More Options → Refresh for another check; the nearby item count opens feed-check details. A new manual check requested during an existing check is queued rather than discarded.

On macOS, use the existing refresh command or refresh icon. The feed update is still subject to your source, search, Archive and filter settings, and a failed source does not cancel already accepted articles.

Some sources may fail or take longer than others. Updates from successful sources can still arrive, and a failed check does not erase articles you already have. Large podcast feeds may take several minutes to check. See Feed Stats if a source keeps failing.

The feed-check details show whether a source is waiting, preparing, contacting the network, waiting for the parser, parsing, saving, retrying, unchanged, checked or failed. If a check runs out of time or is interrupted, the status may say Refresh stopped early. Sources marked Stopped or Not started were not fully checked; this is not the same as a publisher error. Updates already saved are kept, but the interrupted check is not a complete refresh. On iPhone and iPad, there is no Show new items approval button. The status sheet reports per-source progress; it does not start another feed update. Articles from a faster source may appear while another is still parsing. When a slower source saves additional articles, STIQRA prepares and publishes them in coalesced batches after the current scrolling gesture settles, even if other sources are still parsing. There is no need to refresh again or wait for the last source to finish. If an article cannot pass active visibility or safety checks, it is not shown merely because the source finished downloading.

The status sheet's New stored count reflects newly accepted, durable article keys during the current check, even when Feed settings hide some of them or the keys are ineligible for new-article notifications. This total can update before visibility checks finish. While an accepted batch is still being checked against your visibility rules, New found and Keyword filtered show Counting… instead of briefly showing zero. New found counts those meeting the narrower keyword/historical exclusion rules; Keyword filtered counts newly accepted keys excluded by keyword rules. Counts shown during a check are results so far, not final totals until the source checks settle. When exclusion evidence is unavailable, the narrower totals remain unavailable rather than claiming zero.

On iPhone and iPad, newly received articles appear above the articles already in your Feed after their verified automatic publication, even when their original publication dates are older. The existing article order and your place in the list stay as stable as possible. Your current filters, archived articles, and source choices still apply. Articles already saved on your device may also appear as STIQRA finishes preparing the Feed after launch; this is not a new refresh and requires no action.

STIQRA contacts each approved source directly. Publishers can still share the same hosting or internet providers, so an outage affecting one provider may affect several sources.

Why some refreshes finish as unchanged

STIQRA checks your subscribed RSS/Atom feeds using ordinary HTTP requests. When a publisher supports it, the feed response includes an ETag or Last-Modified value. STIQRA remembers that small value and includes it in a later check of the same feed. If the publisher replies 304 Not Modified, there is no feed document to download or parse; the check can finish quickly and be reported as Unchanged. This is a normal result, not an error.

If the publisher returns 200 OK, STIQRA receives and validates the feed and processes previously unknown articles or episodes. A 200 response does not necessarily mean there are new items. Some publishers do not support conditional requests, so their feeds require normal downloads more often. STIQRA does not send the publisher your stored articles, known-item list, or read status to check whether its feed changed.

STIQRA keeps these feed-specific HTTP values on your device across app restarts to make later checks efficient. They expire after seven days without a successful refresh that renews them; regularly checked feeds can keep valid values longer. Removing a source clears its current feed validators, and Clear RSS Cache clears all stored feed validators. See Privacy, security, and data for where these values are kept.

Per-source refresh and image preferences

Each source can use Automatic or Manual only refreshing. Manual-only sources do not check for updates in the background, but you can refresh them yourself. A manual refresh may still need to wait if a website asks STIQRA to slow down, and it follows the same safety checks. You can also set image preferences for individual sources; turning off images for the whole app still takes priority.

Auto refresh

Auto refresh is free and off until you explicitly enable it, including on existing installations that never opted in. Manual refresh remains available when automatic checks are Off. When enabled, the interval you choose is the shortest time between automatic checks while the app is active. Changing the interval takes effect on subsequent automatic checks without restarting the app. STIQRA may wait longer if a website rarely updates, repeatedly fails, or asks the app to pause. Turn auto refresh Off again whenever you want only explicit refreshes.

Auto Refresh and notifications are separate choices. Free Auto Refresh can run even when you decline notification permission; no system permission prompt appears when you select an interval. Settings → Notifications is a free, independent switch for new-article alerts and iPhone/iPad app-icon badges. Its default is on, but the OS prompt appears only after you press Next on the onboarding reading-options step or explicitly request permission in Settings. You can decline permission without stopping refresh or reading. Only a permitted background check can generate a new-article notification; enabling notifications alone does not schedule checks or guarantee a badge count.

Choose a shorter interval when you want to check for news more often, or a longer interval to reduce network activity. STIQRA may space out checks for websites that update slowly, have problems, or share the same provider. Turn Auto Refresh Off if you prefer to check for updates yourself.

For You topics

Source Settings → For You contains topic selection. Choose All topics for the broadest personalised section, No topics to intentionally empty For You, or individual categories: Finance, Technology, Politics, Health, Science, Business, Sports, and Entertainment. Topic choices affect For You only; they do not remove feeds or change the main Feed. Done applies the selection to the current For You list. No topics clears that list, including previously displayed articles; Cancel discards the draft.

Background behaviour

Auto refresh is primarily designed for active app use. STIQRA does not schedule app-owned background feed refresh on a fresh install or request notification permission merely because the app was launched. On supported iOS builds, a background refresh request can be scheduled only after you enable auto refresh, and platform background rules can still limit what happens when the app is closed, suspended, or not foregrounded.

For background updates on iPhone and iPad, enable Background App Refresh for STIQRA in Settings → General → Background App Refresh. iOS decides when background work runs.

Refresh status shows Counting… only while the displayed refresh is running. When no count is available and no counting is in progress, it shows -. A confirmed zero still appears as 0.

If you need the latest articles now, open the app and run manual refresh.

Feed cutoff

Feed cutoff hides articles older than the selected period. It keeps active views focused on recent content.

Cutoff applies broadly to feeds and search views. Set cutoff to Off when you want older articles to remain visible.

Retention and cleanup

STIQRA may maintain local stores for articles, images, metrics, reports, audio, AI-generated outputs, local analysis outputs, and preferences. Retention behaviour is separate from source subscription. Saving or archiving an article can affect where it remains visible.

Source Settings → Retention includes controls for how long items stay in the active feed list, a maximum item count, exemptions for Saved and History, and Automatic archiving at 1000 articles. When enabled and the main Feed contains at least 1,000 articles, STIQRA moves eligible Feed articles older than 7 days into the Archive library without deleting them. Saved, History, Filtered and already archived items are excluded. The setting starts enabled on genuinely new installations and its onboarding switch sits directly below Images; changes in onboarding save immediately. Existing installations keep their saved setting and receive no prompt or automatic opt-in. You can change the switch at any time. Exempt Saved view and Exempt History view keep those library sections from being trimmed by the separate feed-list retention policy. Retention is not the same as feed cutoff: cutoff hides older articles from active views, while retention can remove older cached feed-list items according to the configured limits.

Cleanup actions are scoped:

  • Clear RSS Cache clears cached RSS feed/article data and rebuilds from the remaining local state. It does not remove feed preferences, keyword lists, saved lists, or archive state.
  • Clear local analysis outputs appears only in supported AI-enabled builds and removes saved per-article local analysis outputs.
  • Clear all AI reports is managed from AI Settings and removes saved AI reports, including multi-article analyses and article-linked reports, without deleting source articles.
  • Delete All Data is the broad reset and can remove cached data, saved articles, reports, keywords, preferences, and cached images.

Read each confirmation carefully before using a cleanup action.

Feed Stats

Feed Stats reflect normal feed refresh and persisted local health data; article-page extraction requests are not supported and do not contribute new health records.

Use the state-specific guidance to retry when permitted or open Source Settings → Subscriptions to inspect a redirect failure, correct a URL, re-enable, disable, or remove a source. A login-only HTTP 401 requires a public feed URL instead; an HTTP 403 is a publisher access denial, not a prompt for feed credentials. Previously stored article-text extraction credentials are retired and cannot authenticate either a feed or an article-page request. To populate optional transport audit rows when Feed Stats is empty, turn on Enable fetch audits. Transport audit metrics such as latency, bytes, TLS policy, cache signals, and provider hints record future normal fetches only; enabling audits does not refresh feeds by itself. Image/media failures are reported separately and do not mark the article source unavailable.

Common feed problems

The feed adds no articles

The feed may be empty, private, invalid, blocked by the publisher, or already up to date. Try opening the feed URL in a browser and confirming it contains RSS or Atom data.

The feed works in a browser but not in STIQRA

Validation may have rejected the URL, connected destination, redirect, transport result, response size, content type, feed structure or parser resource budget, duplicate record, or durable save. The Add Feed message identifies the category without displaying remote response text. Parser-work, helper runtime, helper reply-size, and HTTP-only episode-destination refusals have their own explanations during both source discovery and validation rather than being described as secure-connection failures. Publishers that require cookies, JavaScript, login credentials, unsafe/excessive redirects, or browser-like behaviour are not supported for feed documents. Article-page text extraction and its authentication are also unsupported. Use the publisher website in your browser if the feed does not contain the full article.

Ordinary multi-item RSS and Atom feeds may contain more combined text than any single retained article field. STIQRA bounds each retained semantic field and the whole document without treating an item, entry, or feed wrapper as another copy of all descendant article text, so larger normal feeds can load without weakening response-size, XML-structure, or deterministic parser-work budgets.

Articles disappear after changing cutoff

Increase the cutoff period or set it to Off.

A source badge seems wrong

Badges are scoped to visible unread articles. Read state, filters, archive, cutoff, source visibility, and image-only layout options can all affect counts.

Login-protected RSS/Atom feeds (unsupported)

STIQRA cannot validate or refresh an RSS/Atom/RDF feed that requires HTTP Basic, a bearer token, cookies, or browser sign-in. HTTP 401 identifies an unsupported login requirement; HTTP 403 means the publisher denied access and is handled as an ordinary HTTP failure. Neither status opens a feed credential editor or offers reauthentication. Ask the publisher for a public HTTPS feed URL if one exists.

Older versions could store feed credentials in the Keychain. Current builds do not use those secrets for feed requests; Delete All Data removes the legacy feed-credential service, and source deletion retains the old cleanup steps where applicable. OPML and portable subscription backups do not contain feed credentials or grant network authority. Historical article-text extraction credentials are deletion-only and are not sent to article pages, feed discovery, or feed refresh. Subscription cards and new-source review offer no Access editor.

Proxies, VPNs, and private feeds

STIQRA uses the operating system's network path but does not offer an application proxy setting. A system proxy, VPN, organisation content filter, or captive portal can cause a refresh to fail under the same public-destination, redirect, TLS, and response checks used for ordinary feeds. Complete captive-portal sign-in outside STIQRA, then retry.

With fetch audits enabled, Feed Stats shows only Proxy reported, Direct reported, or Route unknown. This is redacted evidence, not a network-authority control. Private/local addresses remain unsupported, and a VPN or proxy does not grant permission to contact them.