= Hack call: 14:00 UTC =

	* Pleased to be here (fred1m)
		* Feels very welcomed by the !FreedomBox project, recommends to others
	* Community Networks (michaelgraaf)
		* Feels that !FreedomBox offers less academic people an entry point, wishes to try soon (in Cape Town, South Africa).
	* NAS status (sunil)
		* a lot of tasks completed, still need: NTFS drives; fix usb lock
		* plans to write a guide on how to use !FreedomBox as a NAS
		* scheduled backups in progress
		* backups of arbitary folders not yet done, move target release to end of month
		* New UI for sharing ongoing by veiko
	* Infinoted fix (sunil)
		* migration to testing prevented by test assuming specific ordering
		* patch given to Maintainer for inclusion until fixed upstream #935614
	* tt-rss fix (sunil)
		* php-gettext has security issue because it uses eval()
		* Replace eval() with parser implementation
	* DBus based daemon plan (sunil)
		* tempted to combine web & sharing apps because calling multiple items is slower
		* each app will have actions.py/privileged_actions.py with no boilerplate
		* a method decorator called @privileged on methods that are currently calling actions scripts, supports types, optional parameters
		* daemon will scan all apps, looking at the actions for @privileged, generates dbus introspection file
		* exceptions are propagated to client
		* will improve performance, reduce boilerplate, eliminate latency
		* plinth.service !NoNewPrivileges=true, whitelist root+plinth users via dbus
		* will make it easier to include new apps, currently need to drop in both actions and module, future will be just module so less coupled with plinth
		* why separate daemon rather than executable? - 
		* more complex for developer mode containers, initially need to restart daemon when editing actions, can eventually monitor file for changes
	* Infrastructure work (Joseph)
		* Fixed issue with automated AMI building triggered off new stable-backports uploads
		* Trying to move some of the cron jobs to CI or Lambda, get metrics/graphs for free
		* 200x cheaper than existing EC2 instance for a month (still within account limit)
		* functional test results published in #freedombox-ci less useful than gitlab/emails
		* https://ci.freedombox.org/
		* sunil will review patch for first-time scenario failures
		* would be good to skip testing only for missing packages rather than mass failures
	* upgrades: Use apt-daily-upgrade for manual update (James)
		* Fixes exception when upgrade is started manually and upgrades freedombox package
			* https://salsa.debian.org/freedombox-team/freedombox/-/issues/1638
		* Requires system to be on AC power. - put in app description
		* Does nothing unless automatic upgrades are enabled. - Disable button when automatic upgrades are disabled.
		* Considering changing UI to 'Trigger an update'. Complete refresh of existing page's two-step process.
		* "Trigger an update" sounds too technical, but "Update now" might not actually run
		* Instead of apt-daily-upgrade, create a new service to run unattended-upgrades manually.
		* suggest running `dpkg --configure -a; apt-get --fix-broken install` before any package related actions, loop until no action taken? APT::Get::Fix-Broken?
	* Oasis: Secure Scuttlebutt (SSB) web server
		* https://github.com/fraction/oasis
		* solves the p2p==device problem by having multiple clients to single bouncer
		* backend is nodejs, so may be difficult to package
		* could use a runtime like deno