From Newsgroup: comp.sys.mac.advocacy

Happy New Year!

What are technical restrictions preventing useful apps on iOS?

Offhand, I know of these... but what other useful categories of
functionality are not only not on iOS, but on every other OS?

1. Real background daemons
Reason: iOS does not allow long-running background processes.
Examples: Tasker (Android), cron (Linux), launchd services (macOS)

2. System wide VPNs with full packet control
Reason: iOS does not expose raw sockets or packet level APIs.
Examples: WireGuard full mode (Android/Linux), OpenVPN TAP mode

3. Tor relays or exit nodes
Reason: Tor needs background tasks and raw network access.
Examples: Orbot relay mode (Android), Tor daemon (Linux)

4. Torrent clients
Reason: Torrents need background networking and filesystem access.
Examples: qBittorrent (Windows/Linux), Transmission (macOS)

5. WiFi analyzers and packet sniffers
Reason: iOS does not allow monitor mode or packet injection.
Examples: Wireshark (Windows/Linux), Kismet (Linux), Airodump-ng

6. Mock location apps
Reason: iOS does not allow apps to override system GPS data.
Examples: Fake GPS (Android), developer location spoofers

7. System wide ad blockers or firewalls
Reason: Apps cannot intercept or modify traffic from other apps.
Examples: AdAway (Android), Pi-hole (Linux), Little Snitch (macOS)

8. File managers with full storage access
Reason: iOS sandboxes every app and blocks filesystem access.
Examples: Total Commander (Windows), Dolphin (Linux), Finder (macOS)

9. Emulators with JIT or dynamic code loading
Reason: iOS forbids JIT and dynamic code execution.
Examples: Dolphin Emulator (Android/PC), RetroArch (Android)

10. Virtual machines or containers
Reason: iOS does not allow hypervisors or low level CPU control.
Examples: VirtualBox (Windows/Linux), VMware, Docker (Linux)

11. System wide automation tools
Reason: Apps cannot modify system settings or hook system events.
Examples: Tasker (Android), AutoHotkey (Windows)

12. Custom launchers or home screens
Reason: iOS does not allow replacing the system shell.
Examples: Nova Launcher (Android), Lawnchair (Android)

13. Custom dialers or SMS apps
Reason: iOS does not allow replacing system communication services.
Examples: Truecaller dialer (Android), QKSMS (Android)

14. Debuggers or system profilers
Reason: Apps cannot inspect other processes or system logs.
Examples: strace (Linux), lsof (Linux), Activity Monitor (macOS)

15. Theming engines or UI modifiers
Reason: iOS does not allow modifying system UI or injecting code.
Examples: Substratum (Android), KDE themes (Linux)

16. Kernel level tools
Reason: No root access and no kernel extensions.
Examples: sysctl tools (Linux), kernel modules, kexts (macOS)

17. Backup tools that copy apps or IPAs
Reason: iOS deletes the IPA after install and blocks access to app
bundles.
Examples: Titanium Backup (Android), full app backup tools

18. Sideloading tools without developer mode
Reason: All apps must be signed with Apple issued entitlements.
Examples: APK sideloading (Android), pkg install (macOS/Linux)

19. Apps that modify routing tables or DNS system wide
Reason: iOS does not expose routing APIs or allow DNS override.
Examples: ip route (Linux), NetGuard (Android), dnsmasq

20. Apps that monitor notifications or other apps activity
Reason: iOS does not allow cross app inspection or event hooks.
Examples: Notification Listeners (Android), system monitors
--
To even be able to ASK these questions, you have to understand iOS.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.mac.advocacy

On Jan 2, 2026 at 8:00:41rC>PM EST, "Maria Sophia" <mariasophia@comprehension.com> wrote:

What are technical restrictions preventing useful apps on iOS?

Nothing. I have loads of useful apps on my iPhones and iPads. Are you saying you have actually logged in to one of your alleged iOS devices, gone to the
App Store and found nothing useful?

Uh huh. Sure.

But if they violate security by running random shell scripts - or other absurd shit that apps have no business doing - then they will not work. They won't even make it into the App Store. And since loading from random websites is not allowed - DING DING DING - iOS is more secure than Android.

AGAIN, iOS is all about security. So we don't need the "secure browsers" that Android and Windows need.

But hey, keep up the good work by asking ridiculous, easy-to-answer questions.
Questions that have already been answered many times.

Any new insights on "crappy batteries" you would like to share? Any questions on how to move files back and forth between Windows and iOS?
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.mac.advocacy

On 2026-01-02 17:00, Maria Sophia wrote:

Happy New Year!

What are technical restrictions preventing useful apps on iOS?

Offhand, I know of these... but what other useful categories of
functionality are not only not on iOS, but on every other OS?

1. Real background daemons
Reason: iOS does not allow long-running background processes.
Examples: Tasker (Android), cron (Linux), launchd services (macOS)

You're wrong.

<https://developer.apple.com/documentation/backgroundtasks/performing-long-running-tasks-on-ios-and-ipados/>

But what else is new.

Since you were wrong right off the top, why would I bother with anything
else?
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.mac.advocacy

On Jan 2, 2026 at 8:26:28rC>PM EST, "Alan" <nuh-uh@nope.com> wrote:

On 2026-01-02 17:00, Maria Sophia wrote:

Happy New Year!

What are technical restrictions preventing useful apps on iOS?

Offhand, I know of these... but what other useful categories of
functionality are not only not on iOS, but on every other OS?

1. Real background daemons
Reason: iOS does not allow long-running background processes.
Examples: Tasker (Android), cron (Linux), launchd services (macOS)

You're wrong.

So Arlen is either stupid or lying???? SHOCKING!!!!

<https://developer.apple.com/documentation/backgroundtasks/performing-long-running-tasks-on-ios-and-ipados/>

But what else is new.

Well, TBF he DOES have a new name. But of course he STILL has the same old, tired act.

Since you were wrong right off the top, why would I bother with anything else?

Touche.

But the good news is, he IS consistent. Arlen has maintained his 100% score on NEVER being correct on ANYTHING he posts.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.mac.advocacy

Tyrone wrote:

On Jan 2, 2026 at 8:00:41 PM EST, "Maria Sophia" <mariasophia@comprehension.com> wrote:

What are technical restrictions preventing useful apps on iOS?

Nothing. I have loads of useful apps on my iPhones and iPads. Are you saying you have actually logged in to one of your alleged iOS devices, gone to the App Store and found nothing useful?

Uh huh. Sure.

But if they violate security by running random shell scripts - or other absurd
shit that apps have no business doing - then they will not work. They won't even make it into the App Store. And since loading from random websites is not
allowed - DING DING DING - iOS is more secure than Android.

AGAIN, iOS is all about security. So we don't need the "secure browsers" that Android and Windows need.

But hey, keep up the good work by asking ridiculous, easy-to-answer questions.
Questions that have already been answered many times.

Any new insights on "crappy batteries" you would like to share? Any questions on how to move files back and forth between Windows and iOS?

Hi Tyrone,

Happy New Year!

You are responding to a question which is not asked in this technical
thread as I certainly did not claim that iOS has no useful apps.

I simply asked a purely technical question about categories of app functionality that are possible on all other common consumer operating
systems but not on iOS due to iOS' innate baked-in architectural
restrictions on what iOS apps are allowed, by Apple to do.

Those restrictions aren't due to the Apple hardware.
But to the Apple decisions to not allow this functionality on iOS.
(Yet, it's on all other operating systems, including macOS in most cases.)

As to your personal feelings, whether a person finds iOS "useful" is subjective. However, the restrictions themselves are objective and well documented by Apple.

For example:

A. iOS does not allow arbitrary background daemons. Only short,
system-managed background tasks are permitted, and they cannot run
indefinitely or start on their own. Apple does provide
BGProcessingTask and BGContinuedProcessingTask, but these are not
daemons. They must be triggered by foreground activity, they run only
when the system decides resources are available, and they cannot run
persistently or autonomously like cron, Tasker, or launchd services.

B. iOS does not expose raw sockets, packet capture APIs, or monitor mode,
which prevents full VPN implementations, packet sniffers, Tor relays,
and similar tools.

C. iOS enforces strict sandboxing. Apps cannot access the filesystem
outside their container, cannot inspect other processes, and cannot
hook system events. This prevents full file managers, system-wide
automation tools, and system profilers.

D. iOS forbids JIT and dynamic code execution, which prevents many
emulators and virtual machines.

E. iOS does not allow replacing system components such as the launcher,
dialer, or SMS subsystem.

These are not value judgments. This is just how iOS works.
Apple designed iOS to not be able to run apps that all other OS's run.

Nobody doubts that.
What we're doing here, is simply discussing what those functionalities are.

Specifically, this thread is discussing the technical boundaries which
Apple has chosen for the platform that no other OS vendor has chosen.

Hence, if we can't answer this question, then we know nothing about iOS.

My question was about identifying additional categories of functionality
that are technically impossible on iOS due to Apple's architectural
choices.

If you have further technical information about capabilities that iOS
exposes or does not expose, that would be on-topic for the discussion.

If we don't even know what iOS can't do that all other operating systems
easily do, then we know nothing about how Apple designed iOS, and why.
--
My posts aim to explore how iOS actually works beneath the surface,
as we know nothing about iOS if all we know is Apple propaganda.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.mac.advocacy

Tyrone wrote:

On Jan 2, 2026 at 8:00:41 PM EST, "Maria Sophia" <mariasophia@comprehension.com> wrote:

What are technical restrictions preventing useful apps on iOS?

Nothing. I have loads of useful apps on my iPhones and iPads. Are you saying you have actually logged in to one of your alleged iOS devices, gone to the App Store and found nothing useful?

Uh huh. Sure.

But if they violate security by running random shell scripts - or other absurd
shit that apps have no business doing - then they will not work. They won't even make it into the App Store. And since loading from random websites is not
allowed - DING DING DING - iOS is more secure than Android.

AGAIN, iOS is all about security. So we don't need the "secure browsers" that Android and Windows need.

But hey, keep up the good work by asking ridiculous, easy-to-answer questions.
Questions that have already been answered many times.

Any new insights on "crappy batteries" you would like to share? Any questions on how to move files back and forth between Windows and iOS?

Hi Tyrone,

Happy New Year!

You are responding to a question which is not asked in this technical
thread as I certainly did not claim that iOS has no useful apps.

I simply asked a purely technical question about categories of app functionality that are possible on all other common consumer operating
systems but not on iOS due to iOS' innate baked-in architectural
restrictions on what iOS apps are allowed, by Apple to do.

Those restrictions aren't due to the Apple hardware.
But to the Apple decisions to not allow this functionality on iOS.
(Yet, it's on all other operating systems, including macOS in most cases.)

As to your personal feelings, whether a person finds iOS "useful" is subjective. However, the restrictions themselves are objective and well documented by Apple.

For example:

A. iOS does not allow arbitrary background daemons. Only short,
system-managed background tasks are permitted, and they cannot run
indefinitely or start on their own. Apple does provide
BGProcessingTask and BGContinuedProcessingTask, but these are not
daemons. They must be triggered by foreground activity, they run only
when the system decides resources are available, and they cannot run
persistently or autonomously like cron, Tasker, or launchd services.

B. iOS does not expose raw sockets, packet capture APIs, or monitor mode,
which prevents full VPN implementations, packet sniffers, Tor relays,
and similar tools.

C. iOS enforces strict sandboxing. Apps cannot access the filesystem
outside their container, cannot inspect other processes, and cannot
hook system events. This prevents full file managers, system-wide
automation tools, and system profilers.

D. iOS forbids JIT and dynamic code execution, which prevents many
emulators and virtual machines.

E. iOS does not allow replacing system components such as the launcher,
dialer, or SMS subsystem.

These are not value judgments. This is just how iOS works.
Apple designed iOS to not be able to run apps that all other OS's run.

Nobody doubts that.
What we're doing here, is simply discussing what those functionalities are.

Specifically, this thread is discussing the technical boundaries which
Apple has chosen for the platform that no other OS vendor has chosen.

Hence, if we can't answer this question, then we know nothing about iOS.

My question was about identifying additional categories of functionality
that are technically impossible on iOS due to Apple's architectural
choices.

If you have further technical information about capabilities that iOS
exposes or does not expose, that would be on-topic for the discussion.

If we don't even know what iOS can't do that all other operating systems
easily do, then we know nothing about how Apple designed iOS, and why.
--
My posts aim to explore how iOS actually works beneath the surface,
as we know nothing about iOS if all we know is Apple propaganda.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.mac.advocacy

Tyrone wrote:

On Jan 2, 2026 at 8:26:28'PM EST, "Alan" <nuh-uh@nope.com> wrote:

On 2026-01-02 17:00, Maria Sophia wrote:

Happy New Year!

What are technical restrictions preventing useful apps on iOS?

Offhand, I know of these... but what other useful categories of
functionality are not only not on iOS, but on every other OS?

1. Real background daemons
Reason: iOS does not allow long-running background processes.
Examples: Tasker (Android), cron (Linux), launchd services (macOS)

You're wrong.

So Arlen is either stupid or lying???? SHOCKING!!!!

<https://developer.apple.com/documentation/backgroundtasks/performing-long-running-tasks-on-ios-and-ipados/>

But what else is new.

Well, TBF he DOES have a new name. But of course he STILL has the same old, tired act.

Hi Tyrone,

Happy New Year!

The goal of this thread is to UNDERSTAND how iOS is different from all
other operating systems in terms of what app functionality is forbidden.

If we don't understand what iOS can't do that every other operating system easily does, then we won't be able to UNDERSTAND why Apple designed iOS to
not be able to do the things that all the other operating systems do.

Regarding that Apple background tasks URL...
<https://developer.apple.com/documentation/backgroundtasks/performing-long-running-tasks-on-ios-and-ipados/>

B. The Apple documentation linked above does not contradict the claim.
It describes background tasks that extend limited work begun in the
foreground. These tasks are discretionary, resource-dependent, and
cannot run indefinitely or autonomously. They are simply not close to
nor equivalent to real background daemons on Android, Linux, or macOS.

C. Every other mainstream OS allows at least one of the following:
a. user-scheduled recurring jobs (cron, systemd timers, Tasker)
b. autonomous background services that start at boot
c. persistent processes that run without user interaction
iOS allows none of these. That is the distinction being discussed.

D. The purpose of this thread is not to debate personal opinions about
iOS, but to identify categories of functionality that iOS restricts
at the architectural level. Background daemons are one such category,
and the Apple documentation confirms the limitation rather than
refuting it.

Since you were wrong right off the top, why would I bother with anything
else?

Touche.

But the good news is, he IS consistent. Arlen has maintained his 100% score on
NEVER being correct on ANYTHING he posts.

As I've already replied to your other post...

A. iOS does not allow arbitrary background daemons. Only short,
system-managed background tasks are permitted, and they cannot run
indefinitely or start on their own. Apple does provide
BGProcessingTask and BGContinuedProcessingTask, but these are not
daemons. They must be initiated by foreground activity, they run only
when the system decides resources are available, and they cannot run
persistently or autonomously like cron, Tasker, or launchd services.
--
If we can't discuss what iOS isn't capable of doing, what is it that we're allowed to discuss on an Apple ng whose members purport to understnad iOS?
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.mac.advocacy

On 2026-01-03 02:02:40 +0000, Tyrone said:

On Jan 2, 2026 at 8:26:28rC>PM EST, "Alan" <nuh-uh@nope.com> wrote:

On 2026-01-02 17:00, Maria Sophia wrote:

Happy New Year!

What are technical restrictions preventing useful apps on iOS?

Offhand, I know of these... but what other useful categories of
functionality are not only not on iOS, but on every other OS?

1. Real background daemons
Reason: iOS does not allow long-running background processes.
Examples: Tasker (Android), cron (Linux), launchd services (macOS)

You're wrong.

So Arlen is either stupid or lying???? SHOCKING!!!!

<https://developer.apple.com/documentation/backgroundtasks/performing-long-running-tasks-on-ios-and-ipados/>


But what else is new.

Well, TBF he DOES have a new name. But of course he STILL has the same old, tired act.

Since you were wrong right off the top, why would I bother with anything
else?

Touche.

But the good news is, he IS consistent. Arlen has maintained his 100% score on
NEVER being correct on ANYTHING he posts.

The moron can't even get his own name right and keeps changiing it!! :-\



--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.mac.advocacy

Your Name wrote:

The moron

Hi Your Name,

Happy New Year!

I'll ignore the ad hominem as it doesn't help us all understand iOS better.

In the original post, I had stopped at showing only a score of categories
of app functionality which Apple disallows on iOS but which every other
common consumer operating system has no problem running (including macOS).

But there's more... much more... I'll stop at 50 this time.

21. Full Bluetooth control and scanning
Reason: iOS restricts Bluetooth APIs to specific profiles and does not
allow raw BLE scanning, custom profiles, or arbitrary device pairing.
Examples: Bluetooth sniffers, HID emulators, custom BLE tools.

22. USB host mode and USB device access
Reason: iOS does not expose USB host APIs or allow apps to communicate
with arbitrary USB devices.
Examples: USB serial adapters, USB debugging tools, USB storage access.

23. Real filesystem mounts
Reason: iOS does not allow mounting external filesystems or exposing
block devices to apps.
Examples: mounting ext4, NTFS, FAT32, or network filesystems.

24. SMB/NFS/CIFS filesystem clients with full access
Reason: iOS only allows limited file provider extensions, not real
filesystem mounts.
Examples: full SMB/NFS clients on Windows, Linux, Android.

25. System wide clipboard managers
Reason: iOS does not allow persistent clipboard monitoring or access to
clipboard changes from other apps.
Examples: Clipboard managers on Android, Windows, Linux.

26. Real call recording
Reason: iOS blocks access to the audio stream of phone calls.
Examples: Native call recording apps on Android.

27. Real SMS backup and restore
Reason: iOS does not expose SMS/MMS databases to apps.
Examples: SMS Backup and Restore (Android).

28. Real phone number management (SIM toolkit access)
Reason: iOS blocks SIM toolkit APIs and carrier level controls.
Examples: SIM management apps on Android.

29. Kernel level networking tools
Reason: iOS does not expose routing tables, ARP tables, or low level
network configuration.
Examples: iptables, nftables, ip route, ifconfig, tcpdump.

30. System wide logging tools
Reason: iOS does not expose system logs or kernel logs to apps.
Examples: logcat (Android), journalctl (Linux), Console (macOS).

31. Real developer shells or terminals
Reason: iOS does not allow fork(), exec(), or arbitrary process
creation.
Examples: Termux (Android), bash/zsh shells on Linux/macOS.

32. Compilers or interpreters that generate executable code
Reason: iOS forbids dynamic code generation and JIT.
Examples: gcc, clang, javac, python with native extensions.

33. Real browser engines
Reason: iOS forces all browsers to use WebKit.
Examples: Chrome with Blink, Firefox with Gecko on all other systems.

34. Apps that modify system settings
Reason: iOS does not expose APIs for system configuration.
Examples: Android apps that toggle radios, change DNS, modify APNs.

35. Apps that replace system keyboards with unrestricted ones
Reason: iOS keyboards are sandboxed and cannot access system APIs or
perform automation.
Examples: Android keyboards with macros or scripting.

36. Apps that access sensors without user interaction
Reason: iOS requires explicit user permission and often foreground use.
Examples: background accelerometer logging, background GPS logging.

37. Apps that modify or inspect notifications system wide
Reason: iOS does not expose notification listener APIs.
Examples: Android notification listeners, automation triggers.

38. Apps that access the phone's file metadata or inode structure
Reason: iOS does not expose inode level filesystem APIs.
Examples: Linux stat tools, forensic tools.

39. Apps that manage or modify system fonts
Reason: iOS does not allow font replacement or system font injection.
Examples: Android font managers, Linux fontconfig.

40. Apps that install system wide codecs
Reason: iOS does not allow third party codecs or media frameworks.
Examples: VLC codec packs on Android, ffmpeg system installs.

41. Apps that modify the lock screen or notification shade
Reason: iOS does not allow UI replacement or modification.
Examples: Android lock screen replacements, custom notification panels.

42. Apps that run at boot
Reason: iOS does not allow user apps to register boot time services.
Examples: Android boot receivers, Linux init scripts.

43. Apps that access the baseband or radio stack
Reason: iOS does not expose modem APIs.
Examples: Android engineering mode tools, Qualcomm diagnostic tools.

44. Apps that access NFC in full mode
Reason: iOS restricts NFC to Apple approved uses.
Examples: Android apps that read/write arbitrary NFC tags or emulate
cards.

45. Apps that modify or inspect the ARP table
Reason: iOS does not expose ARP APIs.
Examples: arp command on Linux, network scanners.

46. Apps that run servers accessible on the LAN
Reason: iOS suspends apps in the background, killing servers.
Examples: Android SSH servers, Linux web servers, SMB servers.

47. Apps that access or modify the hosts file
Reason: iOS does not expose system configuration files.
Examples: Android ad blockers, Linux DNS overrides.

48. Apps that access the GPU directly
Reason: iOS only exposes high level graphics APIs.
Examples: Vulkan tools, GPU compute tools on Android/Linux.

49. Apps that access the microphone or camera in the background
Reason: iOS suspends apps and blocks sensor access.
Examples: Android background audio recorders, security camera apps.

50. Apps that modify system-wide permissions
Reason: iOS does not expose permission management APIs.
Examples: Android permission managers, Linux ACL tools.
--
My posts aim to explore how Apple product actually works beneath the
surface, in ways most users may never understand in their entire lives.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.mac.advocacy

On 2026-01-02 18:29, Maria Sophia wrote:

Tyrone wrote:

On Jan 2, 2026 at 8:26:28'PM EST, "Alan" <nuh-uh@nope.com> wrote:

On 2026-01-02 17:00, Maria Sophia wrote:

Happy New Year!

What are technical restrictions preventing useful apps on iOS?

Offhand, I know of these... but what other useful categories of
functionality are not only not on iOS, but on every other OS?

1. Real background daemons
Reason: iOS does not allow long-running background processes.
Examples: Tasker (Android), cron (Linux), launchd services (macOS) >>>

You're wrong.

So Arlen is either stupid or lying???? SHOCKING!!!!

<https://developer.apple.com/documentation/backgroundtasks/performing-long-running-tasks-on-ios-and-ipados/>

But what else is new.

Well, TBF he DOES have a new name. But of course he STILL has the same old, >> tired act.

<snipped>

Regarding that Apple background tasks URL...
<https://developer.apple.com/documentation/backgroundtasks/performing-long-running-tasks-on-ios-and-ipados/>

B. The Apple documentation linked above does not contradict the claim.
It describes background tasks that extend limited work begun in the
foreground. These tasks are discretionary, resource-dependent, and
cannot run indefinitely or autonomously. They are simply not close to
nor equivalent to real background daemons on Android, Linux, or macOS.

Your statement was that:

"Reason: iOS does not allow long-running background processes."

iOS most certainly DOES allow "long-running background processes." Period.

Now you're dragging the goalposts and attempting to minimize.

BTW: "launchd"?

You stated as examples of "long-running background processes" that
aren't supported on iOS:

"Examples: Tasker (Android), cron (Linux), launchd services (macOS)"

launchd is integral to iOS, Arlen.

C. Every other mainstream OS allows at least one of the following:
a. user-scheduled recurring jobs (cron, systemd timers, Tasker)
b. autonomous background services that start at boot
c. persistent processes that run without user interaction
iOS allows none of these. That is the distinction being discussed.

D. The purpose of this thread is not to debate personal opinions about
iOS, but to identify categories of functionality that iOS restricts
at the architectural level. Background daemons are one such category,
and the Apple documentation confirms the limitation rather than
refuting it.

Since you were wrong right off the top, why would I bother with anything >>> else?

Touche.

But the good news is, he IS consistent. Arlen has maintained his 100% score on
NEVER being correct on ANYTHING he posts.

As I've already replied to your other post...

A. iOS does not allow arbitrary background daemons. Only short,

"No true Scotsman".

system-managed background tasks are permitted, and they cannot run
indefinitely or start on their own. Apple does provide
BGProcessingTask and BGContinuedProcessingTask, but these are not
daemons. They must be initiated by foreground activity, they run only
when the system decides resources are available, and they cannot run
persistently or autonomously like cron, Tasker, or launchd services.

--- Synchronet 3.21a-Linux NewsLink 1.2