Noob: Can I install Linux on an empty nvme while in windows? Without needing a USB?


Basically. I have separate drive for my windowsOS/media etc. And one of my nvme drive now is completely empty.

Is there a way to install Linux onto that empty nvme with windows and then like turn the PC off remove my windows drive entirely, and then have it just boot with the linux drive without needing to do a whole bootable usb through the motherboard uefi?

I don't have USB drives and they cost too much for something i never use.

Like if there was a linux installer that Ibcan run while logged in to windows that would be amazing...

Open Grind: an unofficial open-source Grindr client for Android, Linux, macOS and Windows


I've been working on reverse-engineering Grindr and creating an open source client implementation for it since March.

When GrindrPlus closed, my project turned out to be its de-facto successor and immediatelly several thousands of people started following it. Now it has 70k+ downloads on Forgejo and the authorship is dedicated to public domain 😀

  • MIT licensed, no ads, no analytics, no trackers, no diagnostics, no statistics, no telemetry, only opt-in updates checking
  • Signed releases, reproducible builds on all four platforms, full transparency
  • And it's now in Google Play (for the time being) and being reviewed for F-Droid!

Already applied for Apple developer enrollment and going to publish this to EU alt stores as well as in the TestFlight. Then a classic unsigned ipa and also going to attempt Apple AppStore just for completeness.

You need an existing Grindr account. Downloads: opengrind.org/download

Questions and criticism welcome.

My Ex-Girlfriend’s Hot Evil Twin


No, this isn’t the title of a spicy movie. Women pretend stuff like this doesn’t happen, but it does.
#Redonkulas #HotEvilTwin #ModernWomen

To donate to this content, see our list of channels, purchase merchandise or join Popp’s Preppers, click here: linktr.ee/redonkulas

Send physical donations to:
Redonkulas.com Productions
29488 Woodward Avenue, Unit 407
Royal Oak, MI 48073
If you write a check, make it out to Second Class Citizen, 501c3
All donations are tax deductible

And be sure to tune in to see the Redonkulas Regiment Live!
Tuesday and Thursday at 8pm Eastern time!
And
Supporter Sunday streams for Locals, Odysee, and SubscribeStar members only!

All sources available on Redonkulas.com!

This entry was edited (today, 4:18 PM)

Reading: The USA bombing of the Minab Iran kid's school


OrangeMaxxing FreddyG reads about the USA bombing of the Minab Iran school on the first day of the US/Israel War Against Iran...

video source: https://x.com/OrangeFreddyG/status/2107082374328574013

https://x.com/OrangeFreddyG

A Technician's Overview of the Manitowoc Moment Control System


Use the correct parts and calibrate the system afterward. Keep accurate records for future reference. These steps help return the crane to safe service. They also support longer periods of reliable operation.

When a Manitowoc crane stops working, the Moment Control System often gets attention first. This system, also known as the Load Moment Indicator, protects the crane from unsafe lifting conditions. Understanding its parts and behavior helps technicians diagnose problems faster. This guide reviews system generations, common failures, and replacement options.

MCS Fundamentals


The Moment Control System calculates safe working load from boom length, angle, and radius. It uses electronic sensors and a controller to compare actual conditions against a stored load chart. If the lift exceeds safe limits, the system interrupts the lifting functions. That action helps prevent tipping and structural damage.

The system operates in harsh conditions. Sensors face vibration, moisture, and temperature swings. Wiring can rub against metal edges. Connectors can corrode. These conditions explain why periodic inspection matters. A small fault can grow into a lockout.

Determining Your System Generation


Manitowoc has used several LMI designs across its crane families. Older machines may carry the EPIC system. Newer units often use CRCS or CAN-bus architectures. Each design performs similar safety functions. Their communication methods differ significantly.

Older systems often run dedicated wires from each sensor to the controller. Newer systems share data over a network. That network connects controllers, displays, and sensors. Troubleshooting steps differ between the two approaches. Testing a digital sensor requires different tools than testing an analog one.

Knowing the generation prevents wasted effort. It also helps when ordering components. A part that fits one generation may not fit another.

LMI Components Most Likely to Fail


Several components within the MCS are prone to wear. Recognizing them helps narrow down a fault. The list below covers the most frequent trouble spots.

Length and Angle Sensors: These units mount near the boom head. They report boom tip position to the controller. An angle sensor may use a pendulum or inclinometer. Weather, dirt, and vibration affect its accuracy.

A length sensor uses a mechanical reeling system, and its cable can stretch, break, or wear. If the controller receives a false boom length, the load chart becomes incorrect. These crane parts endure constant movement, which eventually causes wear.

Pressure Transducers: These devices measure hydraulic pressure to estimate load weight. They connect to the hoist cylinders. Moisture, shock, or age can cause failure. When they fail, load readings may become erratic.

The Controller: This unit acts as the system's brain. It receives sensor signals and compares them to stored load charts. Then it sends commands to the display and cutoff valves. Controllers rarely fail without cause, but water intrusion or short circuits can damage them quickly.

Displays and HMI: The cab display shows critical lifting information. Backlights can burn out, screens can crack, and buttons can stop responding. If the operator cannot read the display, safe operation becomes difficult.

Early Indicators of a Problem


An LMI does not always fail with a clear error code. Sometimes readings jump around. Load weight may bounce by several thousand pounds while the load is stationary, and boom angle may drift by a few degrees. These symptoms deserve attention.

Operators often notice subtle changes before a full failure. If an operator reports unusual behavior, investigate promptly. Waiting can lead to a lockout on the job site.

Start with basic checks. Inspect wires near the boom hinge for chafing. Look inside junction boxes for moisture. Corroded crane parts and connections cause many apparent sensor failures. Cleaning or replacing a connector may solve the issue.

Sourcing Replacement Components


When a component fails, replacement speed matters. Correct selection matters just as much. The wrong component can waste time and create new safety concerns. Use the following guidelines to improve outcomes.

OEM and Aftermarket Options


Original Equipment Manufacturer components are built for specific crane models. Genuine Manitowoc parts match the system's electrical and software requirements. They reduce compatibility risk in safety-critical applications. Aftermarket alternatives exist, but quality varies.

Some Manitowoc parts from aftermarket sources may work correctly. Others may not meet output specifications. A pressure transducer with the wrong milliamp output can produce inaccurate load readings. Buy from suppliers who understand crane electronics and ask about warranty and return policies.

The Role of Serial Numbers


Manitowoc updates systems over time. A 2012 crane may have a different LMI setup than a 2016 model. The crane model name alone does not guarantee compatibility. Serial numbers and old part numbers provide the details needed.

Record the crane serial number before calling a dealer. Also note the part number from the failed component. This information helps confirm the correct replacement. It also reduces the chance of ordering the wrong item.

Firmware and Software Considerations


Hardware replacement is only part of the repair. Controllers require correct firmware to read sensors properly. A used controller may not arrive with the right software. A Manitowoc dealer may need to load load charts and configuration files.

Do not assume a replacement controller will plug and play. Even genuine Manitowoc parts may need programming. Confirm software requirements before installation. That step prevents delays after the part arrives.

When Parts Are No Longer Available


Dealers sometimes report that a component is obsolete. This situation is common with older cranes. The original sensor may be out of production. Several options remain available.

You can search for rebuilt or used crane parts online. Verify the seller's reputation and the part's condition. Ask for test results when possible. Another option is a retrofit kit.

Manitowoc and some third-party companies offer upgrade kits. These kits replace older analog sensors with digital equivalents. They may cost more upfront, but they can simplify future maintenance and improve diagnostic capabilities. Some rebuilders specialize in Manitowoc parts for discontinued systems.

Installing and Calibrating Electronic Safety Components


Mechanical installation is often straightforward. Electrical work requires care. Follow these practices to avoid damaging new components.

Disconnect the Power: Remove battery power before unplugging or connecting electronic parts. Hot-swapping can destroy a new controller instantly. This simple step protects the equipment.

Protect the Connections: LMI connectors use small pins that carry low-voltage signals. A bent pin, dirt, or moisture can cause intermittent faults. Use dielectric grease to keep water out. Take time when mating connectors.

Route Cables Carefully: Length sensor cables must follow factory routing. A cable rubbing a sharp edge can chafe through quickly. Use proper ties and guides. Poor routing can cause repeat failures.

Calibration Is Mandatory: A new angle sensor cannot simply be bolted on and used. The system requires calibration. Certified test weights and a calibrated angle gauge are needed. Skipping calibration compromises safety and puts the crew at risk.

Recordkeeping Practices


After repairs, document the work performed. Record the part numbers used and calibration values entered. Note the date and the technician's name. Keep this log with the crane's maintenance records.

This record saves time during future diagnostics. It also helps the next technician understand prior repairs. A clear history supports better maintenance decisions.

Closing Thoughts


The Manitowoc Moment Control System is a vital safety layer. When it fails, repair pressure is high. Avoid rushing the process. Diagnose the exact failure before ordering components.

Use the correct parts and calibrate the system afterward. Keep accurate records for future reference. These steps help return the crane to safe service. They also support longer periods of reliable operation.

Does Your Website Hold Up on Mobile? A Testing Framework


Mobile devices generate more than half of all web traffic. Treat those visitors as your primary audience. A site that works well on a phone generally works well everywhere.

Many site owners carry a quiet assumption that their website performs fine on phones. The pages render, the text adjusts, and nothing crashes. For them, that settles the matter.

It doesn't settle anything. Mobile-friendliness is a question of usability, not mere display. A visitor should be able to read comfortably, tap accurately, and load pages quickly on a typical cellular connection.

Testing is the only reliable way to find out. What follows is a clear framework for doing it well.

Separating Responsive From Mobile-Friendly


These two labels get used interchangeably, but they describe distinct qualities.

Responsive design molds itself to the available screen width. Resize a desktop browser window and a responsive page will reflow to match.

Mobile-friendly design reflects a deeper intention. It means the site was planned around handheld use. Text remains legible on narrow displays. Interactive elements suit a thumb. Navigation tucks away cleanly. Nothing hijacks the screen with an intrusive overlay.

A layout can respond to screen size and still be awkward on a phone. Real usability is the standard.

The Manual Walkthrough


Set the software aside and take out your phone. Open the site on that device rather than a desktop browser. Then attempt to use it as a customer would.

Readability comes first. Is the text comfortable without zooming? Small fonts push people away.

Tap targets come next. Tap every link, menu item, and button. If you keep hitting the wrong one, spacing is inadequate.

Then review your images. Do they scale correctly? Do they crop badly on a tall screen? Desktop monitors are wide, phones are narrow. An image that looks fine on a laptop may lose key details on a handset.

Forms deserve a close look. Open your contact page and complete it on your phone. Are the fields easy to select? Does the keyboard obscure the submit button? A cumbersome form means lost messages.

Finally, watch for pop-ups. If a signup overlay covers everything and the close button is too small to hit, that fails. Google penalizes intrusive mobile interstitials.

Frequent Problem Areas


As you review by hand, keep an eye out for these recurring issues.

Image carousels often malfunction on phones. The navigation arrows may be too small, or slow slides may push content down the page.

Sticky headers create another problem. A header that stays fixed while scrolling can eat up a large share of a small display. That leaves minimal room for reading.

Infinite scrolling is a third concern. It makes reaching the footer nearly impossible. If your contact details or privacy policy sit down there, visitors won't find them.

Google's Free Diagnostics


Once the manual check is done, move to technical evaluation. Google offers free utilities that reveal how its systems read your site.

PageSpeed Insights is a sensible starting point. Enter your URL and study the mobile report. The tool scores speed and usability while listing concrete defects. It might flag undersized tap targets or weak text contrast.

The report also measures how long the largest visual element takes to appear. That measurement is Largest Contentful Paint. Anything beyond 2.5 seconds calls for image compression or code cleanup.

Cumulative Layout Shift matters too. It describes how much the page moves while loading. Have you ever reached for a link, only to have the page jump and send you to an advertisement? That's a layout shift. It's deeply irritating on mobile, and Google treats it as a ranking factor.

Keep in mind that Google relies on Mobile-First Indexing. Its crawlers evaluate the mobile version of your site before the desktop one. A polished desktop experience won't compensate for a poor mobile one.

Simulating Devices in Chrome


A physical handset isn't always needed. Chrome provides a device simulation mode. Right-click anywhere on your site and select "Inspect." Then click the icon that resembles a phone and tablet side by side. The Device Toolbar appears.

Use the dropdown to pick a device. Options include various iPhones, Galaxy models, and tablets. The viewport resizes, and you can interact with the page as if you were on that device. This is convenient for catching layout issues during edits. You can also rotate the simulated screen to check landscape orientation.

Speed Under Realistic Conditions


Speed is central to mobile usability. A page might look flawless on office Wi-Fi, yet struggle on a busy 4G network. Slow loading drives mobile traffic away.

Return to Chrome's Developer Tools. In the "Network" tab, you can throttle your connection. Choose "Slow 3G" or "Mid-tier mobile" and reload. Watch how the page assembles. If the screen remains empty for five seconds, something is wrong. Visitors will abandon it.

Mobile users are impatient. When a page takes longer than three seconds, most of them leave. Compressing images, trimming code, and using a content delivery network can correct these delays.

Involving a Professional


Testing sometimes uncovers problems that quick fixes can't resolve. If your site is slow, confusing, or broken on certain devices, the cause may be an outdated theme or poorly written code.

An aging platform might justify a full rebuild. That's where a capable website designer Singapore becomes valuable. They can restructure your layout, optimize your images, and tidy your code so the site performs well on any screen. A professional works mobile-first, ensuring everything functions before adapting to desktop.

For businesses that rely on online traffic, a broader approach may be warranted. Engaging a web design agency gives you access to a full team. They can manage ongoing performance checks, browser compatibility, and the technical SEO details that influence mobile speed. A dependable agency validates on real devices, not only emulators, so nothing slips through.

Build Testing Into Your Routine


A single test won't stay accurate for long. Every new post, image, or button change alters the mobile experience. Testing should become routine.

After any update, pick up your phone and click through the new material. Confirm that images load promptly. Verify that formatting changes haven't disrupted the layout.

Mobile devices generate more than half of all web traffic. Treat those visitors as your primary audience. A site that works well on a phone generally works well everywhere.

Don't assume your site is fine because it opens on a smartphone. Test it carefully. Run the manual checks, use Google's tools, and simulate slow connections. Repair whatever you find. If the issues exceed your ability to solve them, seek professional help. Visitors will stay longer, and your search rankings will reflect the improvement. Take a few minutes to test your site today. The results might surprise you.

[Fedora] [Nvidia] Fresh install, DisplayPort monitor not recognized


I'm trying to avoid creating a larger problem for myself, so I figured I'd call in help. Still fairly novice with Linux (especially Fedora), but I'm determined to finally migrate from Windows.

I'm running the XFCE spin of Fedora with a GeForce RTX 5070 Ti and Samsung Odyssey G9. I kept my Win11 partition during migration and confirmed the monitor setup still works in windows, just not Fedora. I'm currently typing this on my Fedora install, on a second monitor I set up to troubleshoot (HDMI on the 5070).

"rpm -qa | grep -i nvidia | sort" returns the following:
akmod-nvidia-615.71.09-3.fc44.x86_64
kmod-nvidia-7.2.8-200.fc44.x86_64-615.71.09-3.fc44.x86_64
nvidia-gpu-firmware-20260916-1.fc44.noarch
nvidia-modprobe-615.71.09-1.fc44.x86_64
nvidia-persistenced-615.71.09-1.fc44.x86_64
nvidia-settings-615.71.09-1.fc44.x86_64
xorg-x11-drv-nvidia-615.71.09-3.fc44.x86_64
xorg-x11-drv-nvidia-cuda-615.71.09-3.fc44.x86_64
xorg-x11-drv-nvidia-cuda-libs-615.71.09-3.fc44.x86_64
xorg-x11-drv-nvidia-kmodsrc-615.71.09-3.fc44.x86_64
xorg-x11-drv-nvidia-libs-615.71.09-3.fc44.x86_64
xorg-x11-drv-nvidia-power-615.71.09-3.fc44.x86_64
xorg-x11-drv-nvidia-xorg-libs-615.71.09-3.fc44.x86_64

"nvidia-smi" returns the following:
NVIDIA-SMI 615.71.09
KMD Version: 615.71.09
CUDA UMD Version: 13.4

Did I mess something up in my install? I followed Fedora's official instructions on Nvidia driver installation (sudo dnf install akmod-nvidia -y). As always, I appreciate the help. While frustrating as a start, I'm excited about making the leap.

Prank: My AI Got a $500,000 Salary Job Interview - SPX6900


Credits
youtube.com/@LongLiveLumina
https://x.com/fangiskhan
github.com/fangiskhan
github.com/fangiskhan/openvaul…

I spent 10 months building an AI VTuber named Lumi. I trained her on 8 months of manually scraped X shitposts because I refused to pay Elon $200 a month for API access. The result was an AI with the personality of a chronically online shitposter.
So I applied her to a real $500,000 job at Coinbase.
She passed the resume screen. She passed the AI screening. She passed the online assessment. Then, in the real interview, her speech-to-text hallucinated "Hi Lumina" as an ad for a beading website and ten months of work died in real time.
This is the full story. Resume, interview footage, the borrowed US phone number from an immigrant friend who has been rehearsing the line "she's in a meeting" for three months, the VoiceGate bypass I tested three times, all of it.

What company should Lumi infiltrate next? Comment below.

00:00 Intro
00:45 Building Lumi
02:34 Planning For Lumi's Content
03:13 Stage 1 (Resume)
07:16 Stage 2 (AI Interview)
10:31 Technical BS (VOICEGATE)
12:34 Stage 3 (Online Assessment)
14:09 Stage 4 (THE INTERVIEW)
16:53 Conclusion

This entry was edited (yesterday, 5:00 PM)

Steam On Linux Dives Down To 3.05% For September


Steam on Linux use in March hit an all-time high of around 5.33% marketshare. Since then it pulled back to around 4% while for September 2026 the Steam Survey results are now in and it's clocking in just above 3%.

The Steam Survey results for September that were published this evening indicate a rather steep decline of 0.85%, down to 3.05%. Meanwhile macOS is at 1.92% and Microsoft Windows at 95%.

As with most months where Steam Survey indicates an abnormally large decline for Linux use, the second stop is checking on the language use... Once again a case of a big spike in Simplified Chinese use. Steam's Survey reports a 7.42% increase in Chinese use, up to 31.39% overall of the Steam population. Usually with those large month-over-month swings where Steam China use shoots up dramatically is a boost to Windows and a detriment to Linux. Some attribute the large increases in Simplified Chinese use to being a reporting/sampling issue.

When diving into the Steam Linux data exclusively, CachyOS has spiked by another 2.65% to now account for 18.12% of the sampled Linux gaming population. That even outperforms SteamOS Holo coming in at 17.37%.

Among Linux gamers on Steam, AMD CPUs still account for the high 60 percentage space thanks to the Steam Deck and Steam Machine using AMD APUs and their open-source/Linux support being popular with enthusiasts.

Those wanting to dive in to all the Steam Survey stats for September can find the fresh data on SteamPowered.com.

Northstar is the free-software web browser of the Nordstjernen projec


Northstar is a minimalist web browser written from scratch in C. One window, one page, one process — about 160,000 lines of original C, small enough for one person to read and audit end-to-end. It carries no upstream browser engine: no Gecko, no WebKit, no Blink. It is free software under the GNU General Public License, version 3 or later, and it runs on Linux, macOS and Windows — on Windows from the Microsoft Store.

Northstar Browser version 1.0.12 released! A sunny ark comic on about:start, a classic Mozilla-style toolbar with address-bar suggestions, relayout and repaint that only redo what changed, popovers per the HTML standard, the Microsoft Store package, an 8 MB engine stack, and a build on Fabrice Bellard’s original QuickJS

in reply to SocialistVibes01

I can not tell you how tired of seeing these vibe coded projects I am.

You didn't give nearly enough of a shit to write the application, why should I give enough of a shit to use it? Could you explain, in detail, line by line, what the happy path of a standard web request is in this thing? Could you walk me through the specific engineering decisions that were made and why? Could you point to the specific regions of code that reflect those engineering decisions?

I'm beyond exhausted with these things and honestly I've gotten to the point where I'd like for us to ban non-codeberg repos

Kagi Ends Orion Browser Development for Linux, Will Open-Source It


Kagi has announced it will stop developing the Orion Browser for Linux and Windows, ending its direct work on these platforms. The good news is that instead of dropping the project, the company plans to open-source both versions so other developers or organizations can keep them going.

For Linux users, this is a big shift for a browser that had just started to show real promise. Orion first came to Linux in early alpha at the start of the year, then officially entered beta in August.

Now, only a few months later, Kagi says the current Linux Beta will keep working, but it will stop getting updates from the company after October 2, 2026. Kagi also warns users not to use the beta as their main browser. The main reason is limited resources.

Kagi says only a small team of developers works on Orion, and the project is funded entirely by Kagi users. Expanding Orion beyond Apple platforms was always a big challenge, especially since the company chose not to use Chromium as its base.

Instead, Orion uses WebKit, which makes it one of the few browsers trying to offer an alternative to the many Chromium-based ones.

Kagi says that keeping a browser running on multiple platforms usually requires either a lot of funding or a big open-source community. Since Kagi has neither, it will now focus its limited resources on Orion for macOS and iOS.

The work done on Linux and Windows will be released as open source instead.

Kagi plans to publish the source code for both versions and share more details within 30 days of the announcement. The company has also reached out to open-source foundations and organizations about possibly taking over the projects in the long term.

However, Kagi makes it clear that it does not plan to be the main maintainer of either open-source project. Any future updates will depend on developers or organizations willing to take over the code.

In short, Orion for Linux’s future depends on what happens after the source code is released and whether a community forms to maintain it. For now, the current beta still works, but without future security updates or maintenance from Kagi, it likely won’t be a good daily browser for long.

For more details, see the official announcement.

in reply to SocialistVibes01

This browser was really cool because, despite being WebKit, it was compatible with Firefox and Chrome extensions. That alone made it more worth trying than any non-FF or non-Chromium browser.

I hope that any other WebKit browsers (like Epiphany/GNOME Web) take that from Orion and adopt it in their own browser. That would make them viable.

NVIDIA's Results Of Conducting Wayland vs. X.Org Latency Testing


In addition to NVIDIA announcing their Display Config Server project at XDC 2026 in Toronto, at this annual developer's conference they also presented their findings on scientific testing of X.Org vs. Wayland latency.

X.Org vs. Wayland latency across different compositors and desktop environments has been a heated topic among passionate Linux desktop enthusiasts. Some argue in favor of classic X.Org delivering the lowest latency while others routinely share their own personal anecdotes and argue in favor of modern Wayland solutions. NVIDIA engineer Kamil Łysik took to a Wayland vs. X.Org latency comparison from key press to presentation. For ensuring accurate measurements, a micro-controller was used along with a light sensor for end-to-end measurements. Paired with software for repeatable and automated testing.

Testing with a NVIDIA GeForce RTX 5070 graphics card and using the company's R610 driver branch, tests were done on KDE KWin 6.7.4 and GNOME Mutter 49.7 and the X.Org Server tests using v1.21.1.24.

NVIDIA latency Wayland vs. X.Org results

NVIDIA's findings were that the latency results between X.Org and Wayland are very close with it being hard to conclude a clear winner. Some notable takeaways include that XWayland no longer introduces extra frame delays where it had in the past with an extra frame latency. Variable Refresh Rate (VRR) was also measured to "drastically improve" responsiveness and deliver roughly the same latency between both X.Org and Wayland based sessions.

Those interested can find the NVIDIA presentation this X.Org vs. Wayland latency topic embedded above.

in reply to SocialistVibes01

On my really old gaming laptop, I had to force X because Wayland refused to use the video card drivers for games, so everything would end up on the CPU.

On my main gaming machine, I have to manually run nvidia-smi to make Wayland recognize the video card is still there before I start a game, otherwise it attempts to run games on the CPU.

There's definitely some work that needs to be done. That being said, when it does work, I have no gripes. I just hate the fact it really really wants to use the CPU instead of the (Nvidia) graphics cards for graphical things by default.

L'an 01 (aka "The Year 01") - 1973 - Jacques Doillon, Alain Resnais, Jean Rouch, Gébé (FR + EN subs)


[FR] L'An 01 est un film français de 1973, réalisé par Jacques Doillon. Il est adapté de la bande dessinée L'An 01 de Gébé, dont le scénario avait été enrichi par les propositions via le courrier des lecteurs, lors de ses publications dans Politique Hebdo, puis Charlie Hebdo.

[EN] The Year 01 (French: L'An 01) is a French comedy film, directed by Jacques Doillon, Alain Resnais and Jean Rouch released in 1973. It is based on the eponymous comic strip by Gébé and has gained cult film status.

DIVULGÂCHAGE / SPOILER

[FR] Le film narre un abandon utopique, consensuel et festif de l'économie de marché et du productivisme. La population décide d'un certain nombre de résolutions dont la première est « On arrête tout » et la deuxième « Après un temps d'arrêt total, ne seront ranimés — avec réticence — que les services et les productions dont le manque se révélera intolérable. Probablement : l'eau pour boire, l'électricité pour lire le soir, la TSF pour dire “Ce n'est pas la fin du monde, c'est l'an 01, et maintenant une page de Mécanique céleste” ». L'entrée en vigueur de ces résolutions correspond au premier jour d'une ère nouvelle, l'An 01.

L'An 01 est emblématique de la contestation libertaire des années 1970 et aborde des thèmes aussi variés que l'écologie, la négation de l'autorité, l'amour libre, la vie en communauté, le rejet de la propriété privée et du travail.

[EN]The film narrates a utopian abandonment, consensual and festive of the market economy and high productivity. The population decides on a number of resolutions, beginning with "Let's stop everything," and the second "After a period of total stoppage, let's bring back — reluctantly — just the services and products we can't do without. Probably : water to drink, electricity for reading at night, the radio to say 'This is not the end of the world, this is Year 1, and now a page of Celestial Mechanics." The implementation of these resolutions is the first day of a new era, Year 1. L'An 01 is emblematic of the challenge of the 1970s and covers such diverse topics as ecology, negation of authority, free love, communal living, rejection of private property and labor.

This entry was edited (yesterday, 11:29 AM)

Vanilla Minecraft on RK3588 ARM SoC using mainline kernel and drivers


After 5 years, Minecraft: Java Edition (version 26.3+) can finally run out-of-the-box on the Rockchip RK3588 ARM SoC using a fully open-source graphics pipeline!

My setup:
+ Operating system: Vanilla OS 3 Reunion (Linux kernel 7.1)
+ Drivers: Mesa PanVK (Vulkan 1.4)

This entry was edited (yesterday, 11:49 AM)

New app: Aftergleam - academic papers


If you read scientific papers, you know how hard it is to keep up with the hundreds of new ones published every day. So I built a private app that learns your interests locally on your phone. Your data never leaves your device, and the app shows you the relevant new papers in your field: computer science, engineering, biology, medicine, chemistry, law and more.

Here's the website and the code under GPL-3.0.
I hope you find it useful as much as I do!

aftergleam.app/

github.com/jakobkreft/Aftergle…

This entry was edited (yesterday, 6:49 AM)

Kernel Recipes 2026 Talk - Security in the LLM age | presented by Greg Kroah-Hartman


cross-posted from: slrpnk.net/post/43394805

Interesting how he mentions LLMs have a 50% error rate, and predicts how no one will pay for a tool with such a poor rate.
in reply to HaraldvonBlauzahn

Here a comment on this from usernomdeguerre on hacker news (ycombinator.com).

"His" and "GKH" refers to Greg Kroah-Hartmann, who is maintainer of the stable kernel series and the speaker in the video.

I've included a few slides into text that i thought were eye-opening to me:
From his Kernel Recipes 2026 slide on Mythos


<br />  Mythos's 79 vulnerabilities:
  24 - no detail at all "something crashed"
  14 - not a bug at all
  3 - totally made up data
  15 - already fixed in latest release
    - 11 by others
    - 4 by anthropic
  20 - fixes were needed
    - 7 "assume a malicious filesystem image"
    - 2 "assume you can inject a malicious network packet into the middle of the stack"
    - 2 "NOMMU"
    - 6 sctp networking issues for untrusted devices
    - 2 ipv6 minor network issues 
    - 1 gpu driver for local malicious user

GHK called this "10 'real' bugfixes", which to me sounds like there's a wild hype machine around these companies and uncritical parroting of every press release they make that falls apart when you engage the affected real experts.
This entry was edited (yesterday, 6:00 AM)

KDE Picks Enterprise, Documentation, and Styling as New 2026-2028 Goals


#KDE
This entry was edited (yesterday, 1:57 AM)

Windows 11 is failing as an operating system


Timestamps:

00:00 Intro

00:46 Sponsor: TuxCare Radar

02:23 Windows 11 is failing right now

05:20 What's the job of an OS?

06:51 Updates break systems. Often.

10:53 You have to adapt to it

15:14 It's highly intrusive

17:44 Debloating tools don't make it good

20:19 Windows fails at being an OS

21:33 Alternatives are better, but not perfect

27:23 Windows is a sales platform, not an OS


Windows 11 is failing as an operating system


Try TuxCare Radar to have the full picture of your system security:
tuxcare.com/tuxcare-radar/?utm…

Grab a brand new laptop or desktop running Linux: tuxedocomputers.com/en#

👏 SUPPORT THE CHANNEL:
Get access to:
- a Daily Linux News show
- a weekly patroncast for more thoughts
- your name in the credits

YouTube: youtube.com/@thelinuxexp/join
Patreon: patreon.com/thelinuxexperiment

Or, you can donate whatever you want:
paypal.me/thelinuxexp
Liberapay: liberapay.com/TheLinuxExperime…

👕 GET TLE MERCH
Support the channel AND get cool new gear: the-linux-experiment.creator-s…

#linux #windows11 #windowsvslinux

Timestamps:
00:00 Intro
00:46 Sponsor: TuxCare Radar
02:23 Windows 11 is failing right now
05:20 What's the job of an OS?
06:51 Updates break systems. Often.
10:53 You have to adapt to it
15:14 It's highly intrusive
17:44 Debloating tools don't make it good
20:19 Windows fails at being an OS
21:33 Alternatives are better, but not perfect
27:23 Windows is a sales platform, not an OS


⇧