Comments

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

My take from this Cybernews article about an Android toolkit to trick KYC verification significantly differs from theirs!

Them: "...the existence of such tools puts users and organizations at imminent risk." "Not a tool for the masses"

Me: "Where can I find this amazing Privacy tool?" "A tool the masses everywhere need access to ASAP"

Almost a year after the Multikernel project shared its Linux kernel code and submitted its first patches for review, the team has now made its Multikernel Linux tree publicly available for the first time. This release is built on Linux 7.0 and is labeled v7.0-mk2 in the project’s kernel tree. Currently, only x86_64 is officially supported.

If you haven’t heard of it, Multikernel is a new way of using Linux on big multi-core systems. Rather than one Linux kernel running everything, it lets several separate Linux kernels run side by side on the same hardware.

The main idea is simple. One Linux instance acts as the host and manages a pool of CPUs, memory, and PCI devices. It can split these resources into separate groups and start another Linux kernel in each group. Unlike virtual machines, these extra kernels don’t run on a hypervisor. Each one gets its own physical CPUs, memory, and devices, and runs right on the hardware.

Resources aren’t locked in place, either. The project says you can shut down instances, return their CPUs, memory, and devices to the host, and then start new instances with a different kernel if needed.

With this release, the project has also shared performance comparisons showing where its bare-metal approach can outperform traditional virtualization. In one set of lmbench tests, Multikernel was compared to a well-tuned KVM virtual machine. Both used the same kernel build, two CPU cores, and 1 GB of memory on a dual-socket Intel Xeon Gold 5418Y system.

The results showed almost the same memory latency and bandwidth, which makes sense given how efficient modern hardware virtualization is. The bigger differences showed up in tasks that need lots of transitions and CPU wakeups.

For example, the tests showed a two-process context switch took 1.37 microseconds with Multikernel, compared to 3.42 microseconds in the default KVM guest. Pipe latency was 3.24 microseconds versus 7.06, and Unix socket latency was 4.81 versus 7.48 microseconds.

However, the developers point out that these numbers don’t mean Multikernel is always several times faster than KVM. A lot of the difference comes from how idle virtual CPUs are managed. In the default KVM setup, waking an idle vCPU means leaving and re-entering the virtual machine. Multikernel, on the other hand, manages its physical CPU cores directly.

The downside is that these CPU cores look fully used to the host and use more power. The project measured about 19 extra watts in this setup. Giving the guest more control over CPU power management also helped latency, but still came with power and resource tradeoffs.

For this first public release, the developers say x86_64 has been tested the most. Support for other architectures may come later. The architecture-specific interfaces have already been separated with future ports in mind, but none are officially supported yet.

For additional details, see the announcement. You can find the Multikernel Linux source code on GitHub. The project also offers a getting-started guide for anyone who wants to try out the technology.

cross-posted from : https://lemmy.zip/post/70365816

Comments

Hey everyone!

A lot has happened since the v5.0 announcement. Step by step, Reitti grows into something richer: it now understands journeys with multiple transportation modes, tells you how much of your world you have actually explored, geotags the photos your camera didn´t, and reads the FIT recordings from your sports watch. Yesterday's v5.3.0 brought all of these threads together, and I want to take a moment to share this progress with the community.

For anyone new here: Reitti (Finnish for "route") is a self-hosted, privacy-first alternative to Google Timeline. It turns raw GPS points from your devices into visits, trips and a timeline of your life, stored exclusively on your own infrastructure.

Here are the features I'm most excited about:

Multi-Segment Transportation Modes

Real journeys are rarely single-mode: you walk to the car, drive, then walk again. Reitti now understands this and models it as one trip with multiple transport segments instead of mislabeling everything as "Driving".

• Color-coded track lines with transition badges exactly where you switched modes (new "Display Transportation Modes" map setting)
• Fully customizable icons & colors per transport mode under Settings > Transportation Modes
• One click to reclassify your entire existing history, with live progress on the redesigned job status page

Spatial Coverage

Hexagons are bestagons.

The "fog of war" for your life: Reitti now calculates how much of your cities, regions, and countries you have actually explored, down to the percentage. With the historical sliders you can watch your map fill in year by year.

Heads up: this optional feature requires SPATIAL_COVERAGE=true, roughly 10 GB of additional disk space and some initial indexing time. Everything about setup and configuration is covered in the Spatial Coverage documentation.

Photo Geotagging via Immich

This one is for everyone running Immich next to Reitti: connect the two services once, and Reitti can locate photos that have no GPS data, then write the coordinates permanently back into your Immich library.

How it works: Reitti takes a photo's capture timestamp, matches it against your recorded location history, and shows you the suggested position. Happy with what you see? One button press writes it into the photo's metadata in Immich. Nothing happens without your confirmation.

This solves a real problem: most dedicated cameras, whether DSLR, mirrorless or action cam, simply have no GPS receiver. Until now, those photos sat forever on Immich's "no location" pile or needed tedious manual tagging. With Reitti, the tracker you already carry does the job your camera never could. And since everything happens between your own two self-hosted services, not a single byte leaves your infrastructure.

FIT File Support

Reitti now natively imports .fit files, the standard format for cycling computers and sports watches from Garmin, Wahoo & co. No more converting your rides and runs to GPX first: drop them in and they show up in your timeline like any other recording.

More Highlights

• Live Location Only mode users (v5.2): share your live position without building a permanent history log. Privacy-first family tracking.
• Bulk GPX uploads for GPSLogger (v5.2): fewer connections, noticeably less battery drain.
• Improved visit/trip detection (v5.1): better algorithms mean less manual cleanup.

Community & Support

• GitHub: Report issues & view source
• Docs: https://www.dedicatedcode.com/projects/reitti/latest/
• RSS: Stay updated via the releases feed.
• IRC: #reitti on libera.chat
• Support: Buy me a coffee on Ko-fi

I'm always curious how you all use Reitti, so feel free to share your setup and stories in the comments. ❤️

AI Disclosure

Per this community's rules for project promotion posts, here is exactly how AI was used in building Reitti:

• Implementation (Assisted): AI helps me generate boilerplate and work through specific problems, but the bulk of the code is written by me, and every change is carefully reviewed and tested before it lands in a release.
• Documentation (Assisted): I use AI as a writing tool to get docs and release notes into an appropriate state. The content, structure and decisions are mine; AI polishes language, clarity and consistency.

Everything else, including architecture, system design, testing, review and deployment, I do by hand.

— Daniel

Comments

Comments

Comments

Comments

Ardour 9.8 has been released as the latest stable version of this powerful, free, cross-platform, and open-source digital audio workstation (DAW) software for GNU/Linux, macOS, and Windows systems.

Coming two and a half months after Ardour 9.7, the Ardour 9.8 release introduces initial scales support to let you visualize out-of-scale notes and choose if you want to avoid creating them entirely when composing and improvising in a specific musical key, as well as support for the Novation Launchkey 88 Mk4 and Arturia Drumbrute controllers.

Ardour 9.8 also brings improvements to session recovery for audio recordings in case the system crashes while Ardour is recording, improvements to clip recording guaranteeing at least a 2-bar count-in with the countdown displayed on the screen in the clip editor, and a new option in MIDI Tools to create arpeggios.

The Transport Masters dialog has been improved as well to report the position when the linear timecode is not moving, and the session locates to static timecode to minimize sync time. In addition, the Cue page has been updated to reorder processors in the track when recording a clip and using hardware monitoring at the same time to get a signal to record.

On top of that, Ardour 9.8 adds UI support for LV2 string parameters, adds lib64 search paths on Linux for VST3 plugins, adds support for handling LV2 parameter updates of any known type, disables VST micro-edit inline controls by default, and adds an “add_section” OSC method.

Starting with this release, Ardour now includes cross-cursor preference in metadata, properly converts sends from old Ardour 2 sessions, enables scrolling for the route comments box, no longer allows end BBT markers after paste, and uses pixel-based logic to determine where to start the edge where resize/reposition occurs.

It also latches the rec-enable control when using a transport master and allows translation of startup profiling messages. Check out the release notes for more details about the changes included in Ardour 9.8, which you can download from the official website as ready-to-use binaries and a source tarball.

I opened the door to a shed and found this guy sitting in the middle of the floor. It's been a long time since I've seen one this big in the wild. My coworker said it was nice enough to be out in the open and not hiding somewhere I had to put my hands.

Comments