03:12 <kentonv> Couldn't get Qubes working. :(

03:53 <ocdtrekkie> :(

15:24 <JonTheNiceGuy> I found qubes overly complicated when I tried it.

18:32 <xet7> I did use Qubes 3.2, but I not have enough RAM to use many VMs at the same time, it was too slow, and VirtualBox did not work well with it. With Qubes 4.x there is development of VM Manager GUI in progress, but it's not ready yet. So I'm currently using Pop!_OS https://system76.com/pop

18:32 <xet7> Pop is based on Ubuntu 17.10

18:33 <xet7> and for sandboxing I use Firejail

19:49 <kentonv> in my case, my network card didn't want to work from inside the sys-net VM and I couldn't figure out how to debug... especially when I, uh, didn't have a network available for web browsing.

19:50 <kentonv> really cool idea but I guess, like Sandstorm, there's a lot of rough edges

22:12 <kentonv> the incidence of asshats bashing my open source work as if I owed them something seems to be increasing

22:16 <TimMc> D-:

22:20 <kentonv> keep encountering people getting excessively indignant about some minor issue they don't like and then angrily threatening not to use my stuff

22:20 <kentonv> and I'm like... "Uh, sure. I'd actually prefer you not use it, thanks."

22:20 <TimMc> I saw one of those, yes. It's a good response.

22:24 <jemc> some folks seem not to get the concept that a "dissatisfied" user who isn't paying you any money and isn't contributing to the project in any other constructive way is a net drain on the project, and there's no incentive to satisfy them

22:33 <kentonv> in this case someone on twitter is bashing me for having google analytics on sandstorm.io. Honestly if he'd asked politely I would have said "Oh yeah, we don't really need that anymore, I guess I'll remove it"... but now that he's been a dick about it, I'm anti-motivated.

22:34 <kentonv> (we always meant to switch it to piwik but never really had time)

22:35 <kentonv> the whole web site really needs an overhaul to reflect the fact that it's an indie project now, not a business

22:37 <jemc> unrelated question - has anyone implemented a cap'n proto based hash map that I could draw some "inspiration" from? like, I'm assuming, some form of wrapper over the List type that allows hash-based lookup in a potentially large cap'n proto message?

22:38 <jemc> seems like it might be a bit of an anti-pattern, but I'm just checking

22:39 <kentonv> jemc, that's something I've always intended to implement someday, but I'm not aware of any implementation currently.

22:46 <jemc> okay, well at least I'm not headed down a fundamentally dumb path then

22:56 <xet7> hehe I really feel the same like Qubes and Sandstorm, as there is old and new bugs popping up in Wekan :D Just fighting to get all updated, fixed and working :D Anyway I'm so happy of all supporters of Wekan that have kept me pushing forward :)