caleb on Nostr: yet again feeling the urge to build pmOS "flavours" for specific usecases honestly ...
yet again feeling the urge to build pmOS "flavours" for specific usecases
honestly would be awesome (and quite feasible?) to get steam deck UI working and ship it as a default on the deck, using GNOME instead of KDE
but there's more, what about some nextcloud/immich images? or preconfigured docker/lxc setup?
an awesome phone-specific use case would be a self-hosted SMS bridge, so you can just grab an old phone, pop a sim in it and use it to remotely send and receive texts (maybe via matrix bridge or some web UI or something)
a super simple and obvious one would be to just autoboot into firefox in kiosk mode that you can configure to cycle through a set of web pages.
we have all the pieces in place for postmarketOS to support this through meta-packages in pmaports (something we already do extensively for regular user interfaces). It really just requires someone to go do it
obviously building a use case specific configuration like this yourself is something people are familiar with (install image, install packages, configure, done) but unlike most distros we would be extremely happy to support configuring these entirely out of the box in pmOS, so almost no user intervention is required. Bonus points for making configuration super easy (e.g via a webserver)
honestly would be awesome (and quite feasible?) to get steam deck UI working and ship it as a default on the deck, using GNOME instead of KDE
but there's more, what about some nextcloud/immich images? or preconfigured docker/lxc setup?
an awesome phone-specific use case would be a self-hosted SMS bridge, so you can just grab an old phone, pop a sim in it and use it to remotely send and receive texts (maybe via matrix bridge or some web UI or something)
a super simple and obvious one would be to just autoboot into firefox in kiosk mode that you can configure to cycle through a set of web pages.
we have all the pieces in place for postmarketOS to support this through meta-packages in pmaports (something we already do extensively for regular user interfaces). It really just requires someone to go do it
obviously building a use case specific configuration like this yourself is something people are familiar with (install image, install packages, configure, done) but unlike most distros we would be extremely happy to support configuring these entirely out of the box in pmOS, so almost no user intervention is required. Bonus points for making configuration super easy (e.g via a webserver)