Samantaz Fox

115 Followers
99 Following
2K Posts

Young Vixen-Panther hybrid, who loves computer stuff and electronics.
Proud #Furry🦊 and #Lesbian 🏳️‍🌈.
May rant now and then.

My invidious commits are PGP-signed with this key:
A203 12E5 44F7 B9CC 5792 2D40 F428 2105 9186 176E

Previous key was:
6E2D 9DE7 A584 E411 5253 47AD 3DF5 6D7D 1CD8 02E1

PronounsShe/Her (EN) | Elle (FR)
LanguagesFR 🇫🇷 / EN 🇬🇧
Location1 AU from the Sun
AgeLegally allowed to drink
Websitehttps://samantaz.fr

RE: https://mstdn.ca/@Paulatics/116295875711029533

I am so proud @Paulatics is part of my government!! Thank you for talking about this huge issue! This is such an excellent speech, and I hope this makes some sort of difference (as I'm pulling my hair out trying to help write responses to Reflect Orbital's horrifying FCC proposal for space mirrors)

Also, this speech means that I'm officially recognized by the Canadian Senate as a goat farmer and orbital dynamics expert. That's right up there with having an asteroid named after me!

Since the NextCloud Office maintainers have not taken into account the arguments against their decision to use Microsoft OOXML as the default format, I submitted a pull request with code that sets OpenDocument as the default format:
https://github.com/nextcloud/richdocuments/pull/5516
I strongly encourage you to retweet, upvote, and comment on this PR, which will be harder to ignore than a “resolved” issue.

Edit: The maintainer (who is clearly terrible at managing comm) has closed the PR and directed people to the issue, which remains open for votes and comments↴
https://github.com/nextcloud/richdocuments/issues/4812#issuecomment-4129406883

Ping @tdforg @libreoffice @nextcloud

#NextCloud #RichDocuments #OpenDocument #microsoft #FreeSoftware #LibreOffice #sovereign

fix(format): makes OpenDocument the default format by nojhan · Pull Request #5516 · nextcloud/richdocuments

This reverts commit 8b464b6 by setting "od[fp]" instead of "ooxml" as a default. Following several downvotes and arguments against making the Microsoft-controlled format OOXML a...

GitHub
Self-propagating malware poisons open source software and wipes Iran-based machines
Development houses: It's time to check your networks for infections.
https://arstechnica.com/security/2026/03/self-propagating-malware-poisons-open-source-software-and-wipes-iran-based-machines/?utm_brand=arstechnica&utm_social-type=owned&utm_source=mastodon&utm_medium=social

@bagder "The SMB protocol has weak security and is rarely used these days" in PR 21079?

I though most NASes use the SMB protocol. Am I missing something?

@bagder Oh, completely, okay! Why though? Too much work required for too little use? Or "better" tooling already exists and you want to incentivize people to use that instead?
@bagder If I understand that correctly, you want to remove the curl implementation of SMB/NTLM and only rely on external libraries in the future, right?
If you have an iPhone, today is a good day to make sure you are running the latest software. https://techcrunch.com/2026/03/23/someone-has-publicly-leaked-an-exploit-kit-that-can-hack-millions-of-iphones/
Someone has publicly leaked an exploit kit that can hack millions of iPhones | TechCrunch

Leaked "DarkSword" exploits published to GitHub allow hackers and cybercriminals to target iPhone users running old versions of iOS with spyware, according to cybersecurity researchers.

TechCrunch
@stargirl Oooh, nifty! Thanks for sharing!

The open source vulnerability scanner trivy has experienced a *second* security incident: a compromised release (v0.69.4) was published to the trivy repository.

https://www.stepsecurity.io/blog/trivy-compromised-a-second-time---malicious-v0-69-4-release

Trivy Compromised a Second Time - Malicious v0.69.4 Release, aquasecurity/setup-trivy, aquasecurity/trivy-action GitHub Actions Compromised - StepSecurity

On March 19, 2026, trivy — a widely used open source vulnerability scanner maintained by Aqua Security — experienced a second security incident. Three weeks after the hackerbot-claw incident on February 28 that resulted in a repository takeover, a new compromised release (v0.69.4) was published to the trivy repository. The original incident disclosure discussion (#10265) was also deleted during this period, and version tags on the aquasecurity/setup-trivy GitHub Action were removed. Trivy maintainers deleted the v0.69.4 tag and Homebrew downgraded to v0.69.3. The following is a factual account of what we observed through public GitHub data.

@toomanyfoxes @FoxbrushTailwag Awww, what a cutie!