Biason::Julio::new(); @juliobiason@functional.cafe

I mean, come the fsck on. #Sysadmin work is hard enough and frustrating enough even without the tools being designed as if someone *wanted* to make things confusing and almost impossible to debug.

But #Zabbix developers looked at #sysadmin work and thought to themselves "hey, I know, we're going to make a tool that dials the confusion up to 11!"

Cyberpunk conjured a world at this end state of neoliberal reorganization. What is remarkable is not that writers anticipated how the neoliberal turn would go, but that 40 years and several international economic crises later, politicians still respond to these crises with solutions that prioritize markets over people. https://slate.com/technology/2020/04/coronavirus-cyberpunk-science-fiction-government-politics.html

huh

> Signal is hiring developers to build Rust libraries that help make private communication simple. If you care about code quality as much as you care about user privacy, you should fit right in.

https://jobs.lever.co/signal/ba4cc493-d110-47a7-85ea-8d0a90a9ccec

Looks like the #Qt devs are using COVID-19 as an excuse to effectively make Qt proprietary software.

"last week, the company suddenly informed both the #KDE e.V. board and the KDE Free QT Foundation that the economic outlook caused by the Corona virus puts more pressure on them to increase short-term revenue. As a result, they are thinking about restricting ALL Qt releases to paid license holders for the first 12 months"

A year in the software world is eternity, may as well not release it.

#functionalcafe should be fine, now. I still have a minor issue with redis, I'm going to solve it tomorrow.

@loke

I found out only yesterday that #Jitsi has dropped #GoogleAnalytics from their public instance https://meet.jit.si/ , which is a great improvement for #privacy ! (They still do analytics, as documented here: https://jitsi.org/security/ , which is a good read for any Jitsi user.)

To Jitsi admins:

– Add a privacy policy (or a link to it) to your landing page.
– Be aware of Google STUN servers in your configuration (see also https://github.com/jitsi/jitsi-meet/pull/5433).
– Change the default text of the landing page since it may incorrectly state that Jitsi is fully encrypted.
– Try to deploy HTTP security headers, like a strict Content Security Policy.
– Keep your server software up-to-date (see also https://infosec-handbook.eu/as-wss/).
– Be nice to each other.

#jitsi

'As the area of our knowledge grows, so too does the perimeter of our ignorance' - Neil deGrasse Tyson
#newsbot

now you're thinking with portals