Our great sponsors
-
AppImageLauncher
Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
This solves this problem for me quite well: https://github.com/TheAssassin/AppImageLauncher
It asks whether an AppImage should be integrated (with .desktop files, etc.) upon launching one and does everything automatically, even on my system running Arch+i3 where I except little to work automatically.
As a user, I love having a single executable file and not worrying about anything else like alien dependencies that will usually not work on my outdated distro.
But from the developer point of view, I've seen some claiming that maintaining an AppImage is a PITA and pretty difficult / time consuming to get right: https://github.com/phw/peek/issues/502#issuecomment-58757433...
I've spent the past half hour reading up on Matrix again. What about the metadata issue? Seems like Signal goes to great lengths to ensure that the only data they have about a user is their phone number and the most recent day they connected to the network.
Meanwhile, Matrix servers just ... log everything by default? https://github.com/matrix-org/synapse/issues/4565
signald[^1] + signal libpurple plugin[^2] (finch, pidgin, adium, bitlbee, etc) works beautifully.
[^1]: https://git.callpipe.com/finn/signald
[^2]: https://github.com/hoehermann/libpurple-signald