Search results

I have been involved with tech since the late 1970s when I first started programming. Fast-forward to the web, and content management systems and web applications, platforms, products, frameworks, etc. Plone has been a stellar solution up until the version 5.x line, and since then something seems to be going more and more "wrong" with the development and community, which breaks my heart...

My response to a discussion on Alignable: "For small business owners : I have noticed and experienced uptick in legal issues and cybersecurity concerns with some of my clients. What do you small biz owners have in place to help and protect you legally and what do you have in place to not only help to prevent an attack on your company /clients / employees /devices but also to restore the identities and stop the bleeding? "

In recent years some distros and apps no loger responding to kill -9 <app name> such as killall -9 firefox.

There has been a very disturbing increase in a trend over the past 5-10 years in the volunteer, paid, and opensource sectors: decreasing worth ethic, lack of motivation, and increasingly severe mercenary and inconsiderate attitudes and behaviors from workers and developers. This trend pre-dates covid. Of course, correlation does not prove causality, but these are some parallel observations.

This is a reading list for those interested in learning more about Information Security (InfoSec).

Recently had interactions with representatives from the organization "Team Decades" with CEO "Ron Norman". There are a LOT of red flags with this company. Is it just a start up, or an exceptionally complex scam?

January 9th, 2024, 10:00 am Pacific Time, BitDefender Total Security Alert: @janhq\inference-nitro-extension\dist\bin\win-cpu\nitro.exe is infected with Gen:Variant.Tedy.258323 !

Started with Q$OS tracked to Debian Upstream, problems booting after install.

This is one of many postings about observations of an organization "doing it wrong" when it comes to projects, with some suggestions on how such a situation can be improved.

Due to Jitsi’s modular, opensource, and highly configurable nature, there are many different architecture variations available when deploying a Jitsi ecosystem. This posting attempts to summarize, some more theoretical for the sake of discussion and analysis, a wide range of variants to consider for different implementations. Which Jitsi Architecture Variant to choose is based on each individual's specific scope and budget. Each successive variation tends to be more complicated than the prior variant. Note that these are NOT Jitsi official variations or terminology. These variation distinctions were created by Hawke Robinson as an attempt to bring some order to the many different potential approaches, and increase clarity when considering scalability, features, and budget constraints.