[01:50] <leftyfb> arraybolt3[m]: that's what we call a "regular" troll https://pastebin.ubuntu.com/p/SZtfvZmkPt/
[01:51] <sarnold> leftyfb: oh nice!
[01:51] <sarnold> I liked the 2.5 hours of patience
[01:51] <arraybolt3[m]> Ah, so just call ops when I see that particular line?
[01:52] <leftyfb> I used to run a bot on EFnet that had all sorts of common text to immediately kick/ban on
[01:56] <arraybolt3[m]> leftyfb: That sounds really helpful.
[03:34] <lotuspsychje> good morning
[06:27] <ice9> why canonical is pushing on snap?
[06:30] <enigma9o7[m]> money.  eventually they'll surely monetize the snap store, once everyones used to using it after being force dfor a decade or something
[06:31] <enigma9o7[m]> and also probably they were listening to records backwards
[06:38] <arraybolt3[m]> enigma9o7: I don't know of anything that would suggest anything about "monetizing" stuff is true.
[06:39] <arraybolt3[m]> From what I see, Snap has several very good advantages in the realms of security, modularity, and ease-of-use for developers, at a cost of speed, size, and feature compatibility in some instances.
[06:40] <arraybolt3[m]> The most recent "push" of Snap, the transition of Firefox from an apt package to a Snap package, was Mozilla's doing AFAIK.
[06:40] <arraybolt3[m]> Which may have been a bit premature on the part of Mozilla, but I get why they did it (sandboxing a browser is a good idea to avoid catastrophic damage in the event of a browser compromise).
[06:42] <arraybolt3[m]> Also Snap acts as the heart of Ubuntu Core, which is a different OS than Ubuntu Desktop and Ubuntu Server - it uses only Snaps.
[06:57] <rfm> To me the best thing about having Mozilla build the snaps is that security-related fixes get out to all the supported releases immediately, instead of a chain of Mozilla fixes>Ubuntu integrates fix in each supported release
[06:59] <arraybolt3[m]> rfm: 👍️
[06:59] <lotuspsychje> just a bit harder to fix bugs this way if the user has to go upstream