A bookshop door in Canada. 🦇
-
A Sleeping Bat at The Next Page Bookshop in Calgary Becomes an Unlikely Star: streetartutopia.com/2025/01/30…
This entry was edited (10 months ago)

#LibreOffice is used by 200 million people. Every major release goes through extensive testing – and there are regular minor updates to fix issues too. The #QA Team analyses bug reports from users, and here’s an example of how quickly they can work: blog.documentfoundation.org/bl… #foss #opensource
in reply to Network == Abstraction Layer

@overunderlay There's no such thing as universal outlet. The one on the picture does not provide earthing for dominant european plugs nor accepts italian or swiss plugs.

I think having alternating scheme of BS 1363 and Schuko sockets is much better than that. Hopefully, during some future refresh, 60W USB-PD chagers would be installed which will make everyone's life much easier.

For 2025, here is a updated and hopefully-useful notice about Linux kernel security issues, as it seems like this knowledge isn't distributed very widely based on the number of emails I still get on a weekly basis:

- The Linux kernel security team does not have any "early notice" announcement list for security fixes for anyone, as that would only make things more insecure for everyone. The number of organizations that fail to understand this is way too high.

- The kernel community DOES assign CVEs, as we are a CNA, please see kernel.org/doc/html/latest/pro… for how they are handled and assigned. Side note, we were #2 in quantity for CVE assignments in 2024 despite only doing so for 10 1/2 months, averaging about 10 CVEs per day. Any process you might have where you feel you need to research each CVE on an individual basis manually is going to be a major time suck, automate it! All CVE entries are provided with proper git commit ids for the vulnerable release ranges for you to check yourself, AND we have tools and other formats that you can use to check this yourself. See git.kernel.org/pub/scm/linux/s… for the tools and raw data for you to pull from directly if you don't want to deal with the cve.org json feed.

- Kernel CVE entries are constantly updated over time, you can not just look a them only when created, and then ignore all updates. Too many groups are missing revoked CVE entries and tightening of vulnerable kernel ranges that we are updating on a weekly basis. By ignoring the updates, you are causing yourself more work, not less. cve.org provides an "updated" feed in their git tree, use it!

- Along the lines of the huge number of recorded CVEs, you HAVE to take all of the stable/LTS releases in order to have a
secure and stable system. If you attempt to cherry-pick random patches you will NOT fix all of the known, and unknown, problems,
but rather you will end up with a potentially more insecure system, and one that contains known bugs. Reliance on an "enterprise"
distribution to provide this for your systems is up to you, discuss it with them as to how they achieve this result as this is what you are paying for. If you aren't paying for it, just use Debian, they know what they are doing and track the stable kernels and have a larger installed base than any other Linux distro. For embedded, use Yocto, they track the stable releases, or keep your own buildroot-based system up to date with the new releases.

- Test all stable/LTS releases on your workload and hardware before putting the kernel into "production" as everyone runs a different %
of the kernel source code from everyone else (servers run about 1.5mil lines of code, embedded runs about 3.5mil lines of code, your mileage will vary). If you can't test releases before moving them into production, you might want to solve that problem first.

- A fix for a known bug is better than the potential of a fix causing a future problem as future problems, when found, will be fixed then.

#2

The pissant's executive order lead to 1 air traffic controller on duty, doing the job of 2 people, at least, b/c of the policy implemented more than 1 week ago. These deaths are a direct result of the pissant administration.

Collision between helicopter and plane kills 67 in nation’s deadliest air disaster since 2001: apnews.com/live/dc-plane-crash… #SHAMEFUL #USA

Apple Explains How to Keep Your Mac From Turning on When Opening Lid macrumors.com/2025/01/30/apple…

reshared this

Want your fediverse project listed on fediverse.info/explore/project… and FediDB.org/software ?

Add your details to the CommunityDB repo:

github.com/fedidb/communityDB

I will merge and update so they are ready for #FOSDEM

This entry was edited (10 months ago)

Here is a silly custom ringtone that I found in a random collection that someone uploaded in the mid-2000s. It appears this collection is no-longer online, and fortunately I downloaded it before it disappeared. The file showcased in this post is 12967819.mp3, and the full collection can be found at datajake.braillescreen.net/V71…

🏆 A huge congratulations to @bagder , founder of cURL , for receiving the first European Open Source Achievement Award! 🎉

The award was presented by Omar Mohsine, Open Source Coordinator at the UN, a key advocate for using open technologies !

👏 Daniel will take place in the EOSAcademy as its President! #EOSA2025 #FOSS #cURL

NVDA-IBMTTS-Driver V25.1.1 has been released.
What's new?
• Added support for NVDA 2025.1.
• Now the driver looks for the audio output in two config paths.
• Deleted the audio output change handler. This was created because in some cases the driver was not synchronized with the current audio output, it needs more testing but seems that this doesn't happen in wasapi mode.
github.com/davidacm/NVDA-IBMTT…

reshared this

It feels like it took me too long to realize that the underlying opposition to Universal Basic Income (UBI) isn't "it's too expensive" or that it redistributes money; it's because it redistributes power.

During the pandemic, we saw a massive swell in worker power, as work-from-home requirements showed a better way of working was possible for many, accommodations that had been withheld for ages for being "unworkable" or "too expensive" suddenly were shown to be completely viable and broadly accessible, COVID relief benefits provided much needed supports and showed that direct distribution was possible, and more brutally the work force shrunk because of illness and death.

Remember the "nobody wants to work" mantra? Right, well, because the pool of available workers was lower and expectations for what employers should provide to their employees grew, so employers had to work harder (pay more, provide better working conditions) to fill positions. It's not that nobody wants to work; it's that the job and wages and working conditions you could get away with don't cut it anymore, because people have options.

And they didn't like that...
Workers had to be brought back to heel:
Greedflation juicing corporate profits, mass layoffs, Return To Office (RTO) mandates. These measures aren't about productivity or necessity; they're about taking back power and control.

UBI works in the same spaces.
When people's basic needs are met, they can pursue better opportunities. When the threat of poverty is removed, you have more power at the bargaining table because you don't have to take the bare minimum just to survive. In other words: you have more power in the equation.

That's why UBI is considered threatening to those that want to exploit their power advantage at the negotiating table. We need to recognize that our economic system demands desperation and the threat of poverty. This isn't some bogeyman conspiracy theory; it's documented economic policy (investopedia.com/insights/down…, vox.com/2014/11/14/7027823/nai…).

Our institutions and society haven't solved poverty and unemployment because our economic system doesn't want them solved, because it needs people in a continual state of precariousness. We cannot expect to eradicate poverty and struggle when we're beholden to an economic system that has baked them into its very existence.

The tragedy that occurred above D.C. last night is one we must do everything possible to prevent going forward. But our leaders are not only ill-equipped, they are focused on politics as a priority over safety. My write-up: open.substack.com/pub/statusku…

Hey fellow COVID-aware folks in the US, Armbrust is unloading these duckbill-style ACI N95 respirators for cheap since they are approaching their expiration date.

We use these (along with 3M Auras and Redimasks). The ACIs are a bit lighter weight and work well for when it's hot or you're going to be exerting and breathing heavier.

armbrustusa.com/products/bulk-…

If it doesn't auto-populate, use ACI75 code for the 75% off, which makes these $75 for 300 masks.

Feel free to boost!

Why the Latest Executive Orders Threaten Blind Americans—And How We Can Fight Back

If you’ve been paying attention to the news, you might be feeling frustrated, uncertain, or even afraid about recent executive actions coming from Washington. You’re not alone.

Learn more: buff.ly/40xdHuC

reshared this

A former Air Force pilot was so disappointed with Windows 95's aquarium screensaver that he established a 25-year dynasty of digital fish that continues to this day
pcgamer.com/gaming-industry/a-…

"[...] representatives of this group of hackers, commonly referred to as "ethical hackers", though theft and home invasion have nothing to do with ethics—but well, I understand, ethical hackers, because that's what they call themselves [...]" (a certain Polish MP)

"Hacker", as we in the bizz know well, carries different meanings for different people, and this can cause hilarious misunderstandings. Yesterday, the Polish TV network TVN aired the second part of an ongoing documentary about issues in NEWAG trains that were analyzed by Dragon Sector. Near the end, the documentary featured a recording from the November 2024 meeting of the Parliamentary Infrastructure Committee, which was meant to discuss the matter. During the meeting, one of the Members of Parliament took issue with the Dragon Sector team being referred to as "hackers"—the quote above is from him (translated from Polish).

This, of course, is nothing new—just another example of someone knowing the colloquial meaning of the word but not its specialized one. This disconnect has existed for at least the past 40 years.

This raises an interesting question—should we use the word "hacker" in formal settings (court, parliamentary committees, etc.), or would we be better understood if we opted for "cybersecurity specialist" or a similar term, as we often do on LinkedIn and other professional platforms?

Or perhaps we should continue using the word "hacker," as it serves as a great litmus test for whether the person we're discussing these topics with is truly familiar with the computer security industry and its terminology. It’s an unexpected but useful canary—or perhaps a reminder—that not everyone speaks "computer."

Returning to the original quote, and on a rather amusing note—or perhaps to balance things out—multiple departments of the Polish government are actively seeking to hire individuals with the "Certified Ethical Hacker" certification. In some cases, you can even get grants to earn it! Additionally, one can find information on government websites about how Dragon Sector was invited to the National Security Bureau to receive a commemorative letter of congratulations and symbolic gifts after winning the 2014 CTF season.

So, do we continue advocating for our specialized meaning of the word "hacker" in official settings? Or should we revert to something more neutral instead?

Just food for thought :)

in reply to Gynvael Coldwind 🐈

As a Polish person, I think the word "hacker" (when not refering to a cybercriminal) is a lot less popular here than it is in English-language spaces, and hence should not be preferred.

I personally prefer "ekspert cyberbezpieczenstwa" (cybersecurity expert) to describe people doing ethical security research, haker (hacker) for the "bad guys", and "majsterkowicz" (tinkerer) for people who like to play with tech, but have nothing to do with cybersecurity.

Following a suggestion from Eva Town (on Bluesky), I've just added my "thumbs down" to the PR to remove inclusive design info from the US Web Design System:
github.com/uswds/uswds-site/pu…

How about you? 👿