France's move to ditch Windows for Linux is its latest effort to reduce its reliance on American tech giants.

Archived version: https://archive.is/newest/https://techcrunch.com/2026/04/10/france-to-ditch-windows-for-linux-to-reduce-reliance-on-us-tech/

I am a tradesman with a lot of technical skills with some specialized skills in short supply (at least in the US) with a little less than a decade of experience. My partner is a skilled social worker with more than a decade of experience.

We cannot afford a golden visa in any country.

We are at least 3rd generation Americans, and do not have the right to claim citizenship in any other country without going through the immigration and naturalization process there.

Neither of us is very good at picking up a new language (lord how I've tried)

Where could we realistically look to go?

cross-posted from: https://lemmy.dbzer0.com/post/66896725

Almost 800 Hungarian government email addresses and associated passwords are circulating online, revealing basic vulnerabilities in the security protocols of ministries involved in classified and sensitive work.

A Bellingcat analysis of breach data shows that 12 out of the government’s 13 ministries have been affected, which in some cases have exposed the confidential information of military personnel and civil servants posted abroad.

Among those affected were a senior military officer responsible for information security, a counter terrorism coordinator in the foreign affairs department, and an employee whose role was to identify hybrid threats against the country.

The revelations come as Hungarians head to the polls this Sunday to decide if Viktor Orbán, leader of the right-wing populist party Fidesz and the country’s longest-serving prime minister, will be elected to a fifth consecutive term.

cross-posted from: https://lemmy.world/post/45435884

"the company admitted it likely won’t be able to keep up with competing models."

"As such, the announcement is a bit of an enigma: if it can’t keep up with the competition, why release it at all? There’s a good change Meta is just trying to get its foot in the door — or a “seat at the big kid’s table,” as Wired put it. The company has struggled to stay relevant in a rapidly changing landscape" "Meta’s preceding Llama open source models largely failed to catch on, with a major controversy last year finding that Meta may have faked benchmark results to make its Llama 4 model seem more capable than it actually was."

cross-posted from: https://lemmy.nz/post/36343692

cross-posted from: https://lemmy.world/post/45429546

It's been a month since Fetcharr released as a human-developed (I think we're sticking with that for now) replacement for Huntarr. So, I wanted to take a look at how that landscape has changed - or not changed - since then. I know this is a small part of an arr stack, which is a small part of a homelab, which is a small part of a small number of people's lives, but since I've been living in it almost every weekend for the last month or so I've gotten to see more of what happens there.

So, where are we at?

Let's start with Fetcharr itself:

• ChatGPT contributions jumped from 4 to 17 instances, with 8 of those being "almost entirely" to "100%" written by LLM. 5 of those are github template files
  • An interesting note is that there are no Claude contributions, except for a vibe-coded PR for a plugin which I haven't reviewed or merged, and is unlikely to be merged at this stage because I don't want a bunch of plugins in the main codebase
• Plugins is a new thing. I wanted to have my cake and eat it, too. I liked the idea of being able to support odd requests or extensible systems but I wanted to make sure the core of Fetcharr did one thing and did it well. I added a plugin API and system, and an example webhook plugin so folks could make their own thing without adding complexity to the main system
  • I may make my own plugins for things at some point but they won't be in the main Fetcharr repo. I want to keep that as clean and focused as possible
• Fetcharr went from supporting only Radarr, Sonarr, and Whisparr to including Lidarr and Readarr (Bookshelf) in the lineup. This was always the plan, of course, but it took time to add them since the API docs are.. shaky at best
• There were no existing Java libraries for handling *arr APIs so I made one and released it as arr-lib if anyone wants to use it for other projects in the future. No Fetcharr components, just API to Java objects. They're missing quite a few things but I needed an MVP for Fetcharr and PRs are always welcome.
• The Fetcharr icon is still LLM-generated. I haven't reached out to any other artists since the previous post since I've been busy with other things like the actual codebase. Now that's winding down so I'll poke around a bit more

What about feedback Fetcharr has received?

The most common question I got was "but why?" and I had a hard time initially answering that. Not because I didn't think Fetcharr didn't need to exist, but because I couldn't adequately explain why it needed to exist. After a lot of back-and-forth some helpful folks came in with the answer. So, allow me to break how these *arr apps work for a moment.

When you use, say, Radarr to get a movie using the automatic search / magnifying glass icon it will search all of your configured indexers and find the highest quality version of that movie based on your profiles (you are using configarr with the TRaSH guides, right?)

After a movie is downloaded Radarr will continue to periodically refresh newly-released versions of that movie via RSS feeds, which is much faster than using the automated search. The issue with this system is that not all indexers support RSS feeds, the feeds don't get older releases of that same movie, and the RSS search is pretty simplistic compared to a "full" search and may not catch everything. Additionally, if your quality profiles change it likely won't find an upgrade. The solution to this would be using the auto-search on every movie periodically, which is doable by hand but projects like Upgradinatorr and Huntarr automated it while keeping the number of searches and the period of time reasonably low as to avoid overloading the *arr and the attached indexer and download client. Fetcharr follows that same idea.

The second largest bit of feedback I've gotten (or, rather, question) is "why use an LLM at all?" - buckle up, because this one gets long. One of the main selling points of Fetcharr is that it's developed by a human with the skills and understanding of what they're doing and how their system works, so it's worth discussing.

The "why?" is a fair question, I think. We've seen distrust of LLMs and the impacts of their usage across left-leaning social media for a while, now. Some of it is overblown rage-bait or catharsis but there do seem to be tangible if not-yet-well-studied impacts on a societal as well as an ecological level, and there's a more than few good moral and ethical questions around their training and usage.

I have (and share) a fair number of opinions on this thread but ultimately it all boils down to this:

• I used the ChatGPT web interface occasionally as a rubber-duck for high-level design and some implementation of the plugin system, as well as a few other things
• I also used it to actually implement a few features. The few times I used it are documented in the codebase and it was a "manual" copy/paste from the web UI and often with tweaks or full rewrites to get the code working the way I wanted
• I, personally, currently have no issue with individuals using LLMs or even using vibe-coding tools to create projects and sharing them with the world, as long as they're clearly documented as vibe-coded projects or LLM usage has been documented in some way
• We, as users of free software, have no obligation from the creators of said free software for anything at all. The inverse is true: the creators of the software have no obligation from its users to continue using it. What I mean to say is, you are just as entitled to not use a piece of software as the creator is to do whatever they want with the software they've made, however they've made it
  • If you don't like how something is done, you don't need me to tell you that it's perfectly okay to not like it, trust it, or use it. Conversely, you are not owed an explanation or re-write of a system you would otherwise enjoy. I have no issues explaining why I made the choices I did but others may not be as comfortable doing so
  • The rise of LLMs and vibe-coding tools has given the average user with an idea the ability to implement that idea. I think that's an amazing thing; seeing people with an idea, some hope, and a few dollars create something from nothing. I thought it was great seeing people learn software dev as a kid, creating useful tools, operating systems, or entire playable worlds from an empty text document and I still think it's great today, even if I don't like some aspects of what a vibe-coded project means. Hell, I prefer human-developed projects over their vibe-coded counterparts when I can find them

Finally, Fetcharr has had a few issues opened and subsequently closed with resolutions. Some are more creative exploitation of how Fetcharr's internal systems work, and others had re-writes of other internal systems before they worked properly. And then there were the frustrating mistakes after a long day of frustrating mistakes. Such is the way of software development.

The new landscape

Since the initial 1.0.0 release of Fetcharr, there's been some changes in other projects and new insights on how this all goes together. Most notably, Cleanuparr got its own replacement called Seeker which is enabled by default. If you run Cleanuparr you may consider replacing or removing Fetcharr from your stack. Try both, see if it's worth running yet-another-thing.

Additionally, the developer of Unpackerr has mentioned that they're looking into a web UI for configuring their project so that's exciting for those that enjoy a web UI config.

It also seems like there's been a few other vibe-coded Huntarr replacements such as Houndarr if you're into those. Looks like a neat little web app and system.

So, where are we at?

Well, let's take an honest look at things:

• It seems like Cleanuparr may very well have a clean Fetcharr replacement. As much as I love seeing folks use tools I've built it's hard to say that Fetcharr is any better than Seeker. Admittedly, I haven't yet tried Seeker, but because it ties directly into Cleanuparr it may very well have Fetcharr beat if you already use the system
• Again, this is a small portion of a stack that a small portion of people use which in itself is a small portion of the general population. Does any of this really matter on a grand scale? No. It's just interesting and I've been living in it for a month, so it's worth sharing some insights which might apply to other, larger conversations.
• The statement-piece of Fetcharr is the (lack of) LLM/AI usage. This is where a large portion of the conversation landed and it's a conversation worth having.
• Web UI config or some sort of stats is a bigger deal to more folks than I originally assumed. It's not a deal-breaker for most but it's interesting to see how important it is to have some sort of pretty web UI. See: the number of stars Fetcharr has vs other similar projects. If you're ever creating your own project that's worth keeping in mind.

Original project release post here for context: https://www.reddit.com/r/selfhosted/s/H4uS9GlwRJ

As a senior software engineer who’s working hard to build a tool for the self hosting community I’m hoping my post will be received better here, given the r/selfhosted’s new megathread tar pit rule for young projects… I’m reposting the Libre Closet feature update announcement here as I had planned to today on r/selfhosted.

I hope this finds some of the people who expressed interest in the project as we worked really hard to deliver on the requested features.

The intended release post read as the following:

——

First I would like to share gratitude for the warm and supportive reception Libre Closet received when I initially posted about it about a month ago. This really motivated me to take the project seriously.

I’d like to introduce ShoshannaTM who’s joined the project as one of the core maintainers.

Since the first post, we’ve gotten 88 github stars, over 3.1k docker image pulls, 2 community PRs contributed, and many helpful issues filed. We’ve made a point to try to respond to everyone in a timely manner and stay engaged with the budding community growing around this project.

We’ve focused a lot on quality and have taken the time to address bugs with numerous minor version releases.

The features and quality improvements have been made with considerable time, engineering, and intention. While myself and Shoshanna are using copilot to accelerate development, substantial upfront deliberate design was done on our part before any feature development. Additionally, nothing is taken without thorough iteration and human review. This project is not vibe coded. It is engineered and we take much pride in our craft and the quality of our work.

Please feel free to ask any questions you may have, whether about the development choices we’ve made, or about the product itself. Both of us are excited to continue to build a community around this project. 

Key changes in this version include:

• Background removal for garment images
• Outfit scheduling calendar, with the ability to plan multiple outfits per day, and mark outfits as worn (future versions could use worn outfit data to tell you which garments you wear most, or perhaps track laundry)
• An improved outfit builder, which allows you to include as many or few garments as you’d like in a single outfit 
• Total customization flexibility for garment categories

As before we’ve maintained the ease of self hosting and only one docker command is needed to deploy! For everyone already hosting Libre-Closet, you simply need to pull the fresh `latest` image to update to the v0.2.0 release.

`docker run -p 3000:3000 -v wardrobe-data:/data ghcr.io/lazztech/libre-closet:latest`

We can’t wait for everyone to try it out, and we hope you enjoy V0.2.0 of Libre Closet! 

Public: https://librecloset.lazz.tech/

GitHub: https://github.com/lazztech/Libre-Closet

The download links for HWMonitor and CPU-Z were redirected to compromised versions of the files.

cross-posted from: https://lemmy.ml/post/45741592

April 9, 2026

As a fragile cease-fire takes hold, Iran is sorting through the wreckage from U.S.-Israeli strikes, which have exacted a heavy toll on its civilian infrastructure. The New York Times has verified damage to 22 schools and 17 health care facilities, a fraction of the devastation in the war so far.

The scale of devastation is likely far greater than The Times’s analysis. The Iranian Red Crescent Society, the country’s primary humanitarian relief organization, said on April 2 that at least 763 schools and 316 health care facilities had been damaged or destroyed in the war.

Access to open source visuals of the current Iran conflict, which has spread to many parts of the Middle East, continues to be sporadic. Videos and photos from within Iran trickle out on social media as the Iranian internet blackout hinders the flow of digital communication.

In past conflicts, satellite imagery has provided a vital overview of potential damage to both military and civilian infrastructure, especially when there are digital black spots or obstacles to on-the-ground reporting. But imagery from commercial providers is becoming increasingly restricted, leaving even those who have access to the most expensive imagery in the dark.

Shortly after the war in Gaza began in 2023, Bellingcat introduced a free tool authored by University College London lecturer and Bellingcat contributor, Ollie Ballinger, that was able to estimate the number of damaged buildings in a given area. This helped monitor and map the scale of destruction across the territory as Israel’s military operation progressed.

Bellingcat is now introducing an updated version of the open source tool — called the Iran Conflict Damage Proxy Map — focused on destruction in Iran and the wider Gulf region.

It can be accessed here.

Former US envoys who dealt with Iran have said that the US-Israeli attack on Iran and Tehran’s subsequent closure of the strait of Hormuz have given Iran new tools and resolve to resist pressure to shutter its nuclear programme.

Two senior negotiators for the Joint Comprehensive Plan of Action (JCPOA), the Obama-era agreement to limit Iran’s nuclear uranium enrichment in exchange for sanctions relief, said the Trump administration’s war had handed Iran a coveted weapon by demonstrating its ability to cut off the strait of Hormuz, an economic chokehold that one negotiator said would help Iran “balance the asymmetry of power” with the US.

“This administration, to say it more politely, cannot unsoil the bed,” said Alan Eyre, a former diplomat who helped negotiate the JCPOA. “There’s no way to get back to the status quo ante before this war started.”

European airports have said jet fuel shortages could hit the summer holiday season, if oil supplies do not start to flow through the strait of Hormuz within the next three weeks.

Airports Council International (ACI) Europe wrote to Apostolos Tzitzikostas, the EU transport commissioner, saying the bloc is three weeks away from shortages.

The warning will raise concerns of a risk of flight or holiday cancellations if the US and Israel’s war on Iran continues. Oil prices have soared since the start of March after Iran effectively closed the strait of Hormuz, a key shipping route for exports from the Gulf, in retaliation.

“If the passage through the strait of Hormuz does not resume in any significant and stable way within the next three weeks, systemic jet fuel shortage is set to become a reality for the EU,” the letter said.