User Tools

Site Tools


packet:whatspyc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
packet:whatspyc [2026/05/15 22:02] 2e0hkdpacket:whatspyc [2026/05/15 22:02] (current) 2e0hkd
Line 7: Line 7:
 There is a more fully featured TUI based interface via the ''--ui textual'' command line argument: There is a more fully featured TUI based interface via the ''--ui textual'' command line argument:
  
-{{:packet:whatspyc-tui.png?800|}}+{{:packet:whatspyc-tui.png?600|}}
  
 And a less CPU intensive interface via ''--ui urwid'': And a less CPU intensive interface via ''--ui urwid'':
  
-{{:packet:whatspyc-urwid.png?800|}}+{{:packet:whatspyc-urwid.png?600|}}
  
 The default interface is pure text which may be useful for older terminals: The default interface is pure text which may be useful for older terminals:
  
-{{:packet:whatspyc-text-ui.png?800|}}+{{:packet:whatspyc-text-ui.png?600|}}
  
 It is also possible to run it as a node command, so users connecting to your packet node can run a command and access whatspyc with the pure text interface. Use ''--nodecmd'' to do this, so each user gets their own state folder based on the callsign they connect to the node with. It is also possible to run it as a node command, so users connecting to your packet node can run a command and access whatspyc with the pure text interface. Use ''--nodecmd'' to do this, so each user gets their own state folder based on the callsign they connect to the node with.
packet/whatspyc.1778882556.txt.gz · Last modified: by 2e0hkd