@ErikUden This is a pogrom - no less.
Notices by Yrjänä Rankka 🌻 (ghard@mastodon.social)
-
Embed this notice
Yrjänä Rankka 🌻 (ghard@mastodon.social)'s status on Saturday, 14-Sep-2024 16:54:20 JST Yrjänä Rankka 🌻 -
Embed this notice
Yrjänä Rankka 🌻 (ghard@mastodon.social)'s status on Saturday, 11-Nov-2023 23:08:46 JST Yrjänä Rankka 🌻 @ErikUden would be fun to see NL invoke NATO Art. 5 on US of A.
-
Embed this notice
Yrjänä Rankka 🌻 (ghard@mastodon.social)'s status on Thursday, 17-Aug-2023 17:58:00 JST Yrjänä Rankka 🌻 @pettter @cmiles74 @HauntedOwlbear @signalapp Indeed, but I’m afraid this becomes a slippery slope. Next thing you know you’re checking for any ”accessibility” components, or screen capture packages that have access to the framebuffer. Now what would you as a dev manager rather allocate limited developer resources for?
-
Embed this notice
Yrjänä Rankka 🌻 (ghard@mastodon.social)'s status on Thursday, 17-Aug-2023 17:53:55 JST Yrjänä Rankka 🌻 @cmiles74 @pettter @HauntedOwlbear @signalapp Risking stating the obvious here: Turning Signal into a full-on vuln scanner would definitely not be within their scope. If your OS - or any components handling I/O to-from the app - you use, it’s game over. Users should be made aware of the importance of general hygiene that messaging apps do not replace.
-
Embed this notice
Yrjänä Rankka 🌻 (ghard@mastodon.social)'s status on Thursday, 03-Nov-2022 06:10:56 JST Yrjänä Rankka 🌻 @Gargron Also most DB engines really need a sh*t-ton of RAM. If the DB has to go to disk - even SSD - you’re in a world of pain. Biggest challenge is to balance RAM / CPU. Sometimes need to tweak OS VM paging parms as well. A good DB does its own paging, as these workloads differ greatly from regular processes.