Atemu

joined 5 years ago
MODERATOR OF
kagi
sorted by: new top controversial old
A distro/set-up for containerization similar to android? in c/linux@lemmy.ml
[–] Atemu@lemmy.ml 1 points 4 months ago (3 children)

That is not relevant here in any way. That's a distro made to easily run one app at a time without really caring about data security w.r.t. that app.

Why is it so difficult to know if a game is goig to run on your system? in c/linux_gaming@lemmy.world
[–] Atemu@lemmy.ml 1 points 4 months ago

Note that even with this it'll be quite likely that games don't work. WineD3D is much less compatible than DXVK.

You need a device that can do Vulkan properly. The best for that are AMDGPUs and Nvidia ones but I wouldn't recommend the latter. Newer Xe Intel GPUs should also work but they're quite a bit behind anything AMD has to offer in terms of performance.

The newer of your GPUs meanwhile is a design from ~2015. Vulkan released in 2016. Just to get you an idea.

The issue here is not Linux, it's that neither of your GPUs was made for modern gaming. On windows that might sometimes work, especially with games targetting older graphics APIs that your GPUs were made with in mind but on Linux everything is Vulkan (a very modern graphics API), even games that only use older APIs.
A modern Vulkan-capable card is a requirement for painless gaming on Linux.

Introducing Privacy Pass authentication for Kagi Search | Kagi Blog in c/privacy@lemmy.ml
[–] Atemu@lemmy.ml 3 points 4 months ago

It uses the same technology but that's it.

Kagi Introducing Fair Pricing in c/technology@lemmy.zip
[–] Atemu@lemmy.ml 2 points 4 months ago* (last edited 4 months ago) (1 children)

Right I can see where you're coming from but that incentivises using Kagi less which IMV is a really bad incentive for all parties involved.

Kagi Introducing Fair Pricing in c/technology@lemmy.zip
[–] Atemu@lemmy.ml 4 points 4 months ago (3 children)

What if they made it so that a single search per month was fine too? You'd be back complaining that it'd be $5 if you only made 2 searches that month.

It's really hard to set a cut-off here.

Kagi Introducing Fair Pricing in c/technology@lemmy.world
[–] Atemu@lemmy.ml 6 points 4 months ago

On the one hand yes but on the other hand this would also kind of set wrong incentives: to use Kagi search less because you'd need to pay more.
That's not an incentive they or you would want.

I think what I'd like is how my mobile carrier handles their data limits: It's not an entirely fair comparison because in that case, contrary to Kagi, there is no real cost associated with my degree of usage of the service, making them entirely arbitrary and unnecessary but besides that the unused data rolls over to the next month and that's something Kagi could mirror.

I hover around 600-1000 searches per month but sometimes exceed 1000. If I could pay for 1000/month and accumulate a little buffer in the months where I search less, that would work for me. Though perhaps I'd still want to just simply pay for unlimited usage for peace of mind.

Kagi Introducing Fair Pricing in c/technology@lemmy.world
[–] Atemu@lemmy.ml 1 points 4 months ago (1 children)

This sounds like FUD. Do you have a source for that?

As a paying member, I know that they started charging (and presumably transferring) VAT last year.

Before that, they claimed they were simply too insignificant to even be eligible for VAT.
I looked it up and there appears to be an exception for such cases where VAT is charged in the company's jurisdiction rather that the customer's (it's usually the other way around) until you reach 10000€ annual turnover. Information on this is extremely intransparent however, so this might be wrong.

Kagi Introducing Fair Pricing in c/technology@lemmy.world
[–] Atemu@lemmy.ml 15 points 4 months ago* (last edited 4 months ago) (2 children)

They do. The $10/month search plan is unlimited.

The only LLM stuff in their search product is the quick answers which can be turned off and page summaries which you have to explicitly click on in a submenu in any case.

As someone aware of how limited LLMs are, I've actually found both of these features to be useful for gauging whether a site is worth visiting or not at times which is part of the core feature set of a search engine IMHO.

A good while back they claimed that Google search index fees make up the vast majority of their costs, so I doubt any of your money is going towards LLM BS unless you actually pay for their assistant product.
I doubt Google has given them any discounts since then.

I'd expect the development of all of their product to be mostly funded by VC. If they can get VC idiots who fell for the """AI""" hype to subsidise building an actually useful thing (the search product), that's a win in my book, even if they also have to build the AI crap on the side to keep said VC idiots happy.

Kagi Search Changelog Jan 21st, 2025 - Share Kagi and explore the best video search results in c/kagi@lemmy.ml
[–] Atemu@lemmy.ml 3 points 5 months ago

I don't often search for videos but I did attempt it recently and it was already better YT did by itself. Perhaps that was mostly because it didn't attempt to shove extremely irrelevant shorts down my throat though but that's already feature enough tbh.

I guess they're spending so much time on the share feature because it's basically free marketing.

Unfortunately though it seems there's a bug since this update where changing a search doesn't actually apply it most of the time when you hit enter or click the button.

I need resources and pointers on how I can write an implementation of Vulkan that supports my older Radeon card: in c/linux@lemmy.ml
[–] Atemu@lemmy.ml 8 points 5 months ago

Someone started working on a Vulkan driver for TeraScale GPUs a few years ago:

https://gitlab.freedesktop.org/Triang3l/mesa/-/tree/Terakan

I believe it can run some demos add even works on windows.

OpenZFS 2.3.0 released in c/linux@lemmy.ml
[–] Atemu@lemmy.ml 2 points 5 months ago

Oracle ZFS is so obscure by now that it's irrelevant.

As usual with Oracle products, it's just a means to squeeze poorly led companies.

Experiences with different gearing on a 6-speed Brompton? in c/bicycles@lemmy.ca
[–] Atemu@lemmy.ml 2 points 5 months ago (1 children)

I tried to relate the limited niche where having closer together gearing makes a noticeable difference

You appear to be misunderstanding. This isn't about making gearing be closer together, this is about increasing the range of the gearing by making the low end lower and only reducing the high end by a little.

If anything, the configurations I wrote about would make gear spacing less even as the default is quite nicely spaced.

What I need to know is whether the change in the low end is actually noticeable in an uphill scenario and by how much.

So I prefer to have as wide as my drivetrain supports. If I have any choice, I prefer a tighter set of low gears and a bailout final cassette cog.

It's the same for me I think. I'd prefer some variety of low gears for uphills and some variety for relatively flat ground. I don't very much care what's in between as long as it's not too far apart.

When I start riding, I usually use one of the lower gears for half a turn and then immediately switch the hub from 64% to 100% (skipping the gear in between) which is a jump from 2.64m to 4.14m or 3.25m to 5.10m and then usually up to 5th gear (6.49m) for a bit and then the 6th gear when conditions allow.

I wouldn’t worry about the total, and would start with the widest cassette that will work with your current setup. Then I would only change the front chainring if you still feel a lack of top speed.

This again appears to be a misunderstanding: This is a 6-speed Brompton.

6-speed here means 6 gears total, including the hub.

The gearing is as follows:

  • Hub with 3 fixed ratios (64%, 100%, 157%)
  • Derailleur between two sprockets that can be equipped with a maximum of 17 teeth due to size constraints
  • One chainring (no derailleur)

I get to choose the two sprockets and the chainring. That's it; there is no wider cassette that physically fits this frame.

The reason for changing the chainring is merely to shift the gearing down which isn't possible by changing the sprockets because a sprocket larger than about 17T will physically not fit. Again, this is a Brompton with tiny 16" wheels that folds down to suitcase size.

7
Kagi Search Changelog Dec 5, 2024 - Kagi for Teams, end-of-year community event (kagi.com)
 

Kagi for Teams

We're excited to announce Kagi for Teams, bringing our unmatched search quality and AI tools to organizations worldwide. Whether you're leading a research team, running a startup, or managing enterprise knowledge workers, you can now equip your entire organization with ad-free search and AI capabilities that respect both your time and privacy.

Visit kagi.com/teams to get started.

End of year community event on December 20th

As we conclude a remarkable year, we invite you to join our End-of-Year Community Event 2024 on December 20th at 09:00 PST. This 90-minute session will feature a "Year in Review" presentation followed by a Q&A session with our community.

  • The event will be hosted as a Zoom webinar. You can register in advance for a reminder or join the webinar on the day of the event

  • Please submit and upvote questions in advance for the Q&A portion of the event

We look forward to sharing this special event with you. See you on December 20th!

Kagi Search

We've introduced a debug tool for everyone helping localize Kagi into as many languages possible and contributing Kagi translations. This toggle is located at the bottom of your Settings > General page and displays string IDs across the UI, providing better context for translations.

We grant official contributor status to our translators, providing access to early products and features. Thank you to all who have contributed.

Improvements and Bug Fixes

Assistant

  • 'searching with kagi' in Assistant #5552 @Thibaultmol
  • Kagi Assistant fails to parse pdfs which render in viewers and other libraries support #5052 @tboby
  • Latex block is not correctly rendered in Kagi Assistant #5483 @oxlvlnle
  • When asking for markdown formatting advice, it does not display the markdown code block at all #5390 @IsaacThoman
  • Unclear max characters in custom assistant context #5526 @jvo
  • Unable to upload files on Kagi Assistanct macOS Web App #5280 @dreifach
  • Assistant fails to summarize YouTube video #5421 @azdanov
  • Assistant can't access website #4809 @azdanov
  • Add exact citation text tooltip to Quick Answer citations #4309 @Prostagma

Kagi for Android

We're just under 1,000 installs away from being eligible for inclusion in the Android Choice Screen. Help us reach this milestone by downloading the Kagi Android app and sharing it with your friends and family!
You can download the app here: Kagi Android App.

An iOS app is also in development, stay tuned for updates!

With this release you can now hold the Kagi Android icon to add shortcuts for Assistant, Translate, Smallweb, or Universal Summarizer directly to your home screen ( #5014 @Thibaultmol)

  • Location Permission not available for android app #5313 @1j4lzsjs
  • We've tweaked a few things to ensure password managers work in the Kagi Android app
  • When you select text or a URL, you now can (a) Summarize with Kagi, (b) Discuss with Kagi Assistant, or (c) Translate with Kagi
  • Mobile app flashes yellow on launch #5147 @Jesal
    Plus we fixed several other bugs and improved performance for a better mobile experience!

Kagi Translate

  • Translate as you type for Ultimate members
  • Instant translation without page reloads
  • Added language search to Kagi Translate, no more scrolling through the list

Visit translate.kagi.com to try Kagi Translate!

This week on social media

Join the growing Kagi community online! Follow us and use #Kagi to share your experience and connect with fellow users.

Here is this week's featured social media mention:

17
Release scrcpy v3.0 · Genymobile/scrcpy (github.com)
 

scrcpy v3.0

Changes since v2.7:

  • Add virtual display feature (#5370, #5506, #1887, #4528, #5137)
  • Launch Android app on start (#5370)
  • Add OpenGL filters (#5455)
  • Add --capture-orientation to replace --lock-video-orientation (which was broken on Android 14) (#4011, #4426, #5455)
  • Fix --crop on Android 14 (#4162, #5387, #5455)
  • Handle virtual display rotation (#5428, #5455)
  • Add --angle to apply a custom rotation (#4135, #4345, #4658, #5455)
  • Add --screen-off-timeout (#5447)
  • Adapt "turn screen off" for Android 15 (#3927, #5418)
  • Add shortcut Ctrl+Shift+click-and-move for horizontal tilt (#5317)
  • Add shortcut MOD+Shift+r to reset video capture/encoding (#5432)
  • Forward Alt and Super with SDK Keyboard (#5318, #5322)
  • Add more details to --list-encoders output (#5416)
  • Add option to disable virtual display system decorations (#5494)
  • Fix --time-limit overflow on Windows (#5355)
  • Fix "does not match caller's uid 2000" error (#4639, #5476)
  • Accept filenames containing ':' when recording (#5487, #5499)
  • Disable mouse by default if no video playback (#5410)
  • Rename --display-buffer to --video-buffer (#5403, #5420)
  • Listen to display changed events (#5415, #161, #1918, #4152, #5362)
  • Adapt server debugging for Android >= 11 (#5346, #5466)
  • Upgrade FFmpeg to 7.1 (#5332)
  • Upgrade SDL to 2.30.9
  • Upgrade platform-tools (adb) to 35.0.2
  • Build releases via GitHub Actions (#5306, #4490)
  • Release static builds for Linux and macOS (#5515, #1733, #3235, #4489, #5327)
  • Various technical fixes

Highlights

Virtual display

By default, scrcpy mirrors the device screen.

With this new feature (#5370), it is now possible to mirror a new virtual display, with a custom size:

scrcpy --new-display=1920x1080
scrcpy --new-display=1920x1080/420  # force 420 dpi
scrcpy --new-display         # use the main display size and density
scrcpy --new-display=/240    # use the main display size and 240 dpi

On some devices, a launcher is available in the virtual display.

When no launcher is available, the virtual display is empty. In that case, you must start an Android app.

For example:

scrcpy --new-display=1920x1080 --start-app=org.videolan.vlc

To list the Android apps installed on the device:

scrcpy --list-apps

For convenience, you can also select an app by its name using a ? prefix:

scrcpy --start-app=?firefox

However, retrieving app names may take some time (sometimes several seconds), so passing the package name is recommended.

On-device OpenGL filters

Scrcpy can now transform the captured video stream before encoding by applying OpenGL filters directly on the device. This has made it possible to fix several issues and implement new features, as described below (more details in #5455).

Crop

The --crop option was broken for devices running Android >= 14 (#4162). It has been reimplemented using OpenGL filters internally.

Its usage remains the same:

scrcpy --crop=800:600:100:100

It now also works for camera and virtual displays.

Capture orientation

The --lock-video-orientation option was broken for devices running Android >= 14 (#4011).

It has been replaced by a more general option --capture-orientation, implemented using OpenGL filters:

scrcpy --capture-orientation=0
scrcpy --capture-orientation=90       # 90° clockwise
scrcpy --capture-orientation=180      # 180°
scrcpy --capture-orientation=270      # 270° clockwise
scrcpy --capture-orientation=flip0    # hflip
scrcpy --capture-orientation=flip90   # hflip + 90° clockwise
scrcpy --capture-orientation=flip180  # hflip + 180°
scrcpy --capture-orientation=flip270  # hflip + 270° clockwise

The capture orientation can be locked by using a @ prefix, so that a physical device rotation does not change the captured video orientation:

scrcpy --capture-orientation=@         # locked to the initial orientation
scrcpy --capture-orientation=@0        # locked to 0°
scrcpy --capture-orientation=@90       # locked to 90° clockwise
scrcpy --capture-orientation=@180      # locked to 180°
scrcpy --capture-orientation=@270      # locked to 270° clockwise
scrcpy --capture-orientation=@flip0    # locked to hflip
scrcpy --capture-orientation=@flip90   # locked to hflip + 90° clockwise
scrcpy --capture-orientation=@flip180  # locked to hflip + 180°
scrcpy --capture-orientation=@flip270  # locked to hflip + 270° clockwise

Now, it also works for camera (fixing #4426) and virtual displays.

Custom rotation

A new option --angle allows to rotate the content by a custom angle. Combined with --crop, this is especially useful for mirroring the Meta Quest 3 (#4135, #4345, #4658).

Virtual display rotation

The new virtual display feature initially could not rotate. The rotation has been implemented using OpenGL filters.

(That is what triggered the development of OpenGL filters.)

Like previously, the current app can be rotated by MOD+r (shortcuts).

Screen off timeout

The existing option --stay-awake only keeps the device awake *while it is plugged in, meaning it typically does not work over TCP/IP.

A new option, --screen-off-timeout, modifies the screen-off timeout setting while scrcpy is running and restores it on exit:

scrcpy --screen-off-timeout=300  # 300 seconds (5 minutes)

Static builds

For convenience, static builds are now provided for Linux and macOS (#5515).

More targets might be added in the future.

This is still experimental for now, so if you encounter problems, please report them.

Features you might have missed

If you haven't tried scrcpy in a while, here are some features introduced in the 2.x versions that you might have missed (check the release notes to each version for more details):

94
Release scrcpy v3.0 · Genymobile/scrcpy (github.com)
 

scrcpy v3.0

Changes since v2.7:

  • Add virtual display feature (#5370, #5506, #1887, #4528, #5137)
  • Launch Android app on start (#5370)
  • Add OpenGL filters (#5455)
  • Add --capture-orientation to replace --lock-video-orientation (which was broken on Android 14) (#4011, #4426, #5455)
  • Fix --crop on Android 14 (#4162, #5387, #5455)
  • Handle virtual display rotation (#5428, #5455)
  • Add --angle to apply a custom rotation (#4135, #4345, #4658, #5455)
  • Add --screen-off-timeout (#5447)
  • Adapt "turn screen off" for Android 15 (#3927, #5418)
  • Add shortcut Ctrl+Shift+click-and-move for horizontal tilt (#5317)
  • Add shortcut MOD+Shift+r to reset video capture/encoding (#5432)
  • Forward Alt and Super with SDK Keyboard (#5318, #5322)
  • Add more details to --list-encoders output (#5416)
  • Add option to disable virtual display system decorations (#5494)
  • Fix --time-limit overflow on Windows (#5355)
  • Fix "does not match caller's uid 2000" error (#4639, #5476)
  • Accept filenames containing ':' when recording (#5487, #5499)
  • Disable mouse by default if no video playback (#5410)
  • Rename --display-buffer to --video-buffer (#5403, #5420)
  • Listen to display changed events (#5415, #161, #1918, #4152, #5362)
  • Adapt server debugging for Android >= 11 (#5346, #5466)
  • Upgrade FFmpeg to 7.1 (#5332)
  • Upgrade SDL to 2.30.9
  • Upgrade platform-tools (adb) to 35.0.2
  • Build releases via GitHub Actions (#5306, #4490)
  • Release static builds for Linux and macOS (#5515, #1733, #3235, #4489, #5327)
  • Various technical fixes

Highlights

Virtual display

By default, scrcpy mirrors the device screen.

With this new feature (#5370), it is now possible to mirror a new virtual display, with a custom size:

scrcpy --new-display=1920x1080
scrcpy --new-display=1920x1080/420  # force 420 dpi
scrcpy --new-display         # use the main display size and density
scrcpy --new-display=/240    # use the main display size and 240 dpi

On some devices, a launcher is available in the virtual display.

When no launcher is available, the virtual display is empty. In that case, you must start an Android app.

For example:

scrcpy --new-display=1920x1080 --start-app=org.videolan.vlc

To list the Android apps installed on the device:

scrcpy --list-apps

For convenience, you can also select an app by its name using a ? prefix:

scrcpy --start-app=?firefox

However, retrieving app names may take some time (sometimes several seconds), so passing the package name is recommended.

On-device OpenGL filters

Scrcpy can now transform the captured video stream before encoding by applying OpenGL filters directly on the device. This has made it possible to fix several issues and implement new features, as described below (more details in #5455).

Crop

The --crop option was broken for devices running Android >= 14 (#4162). It has been reimplemented using OpenGL filters internally.

Its usage remains the same:

scrcpy --crop=800:600:100:100

It now also works for camera and virtual displays.

Capture orientation

The --lock-video-orientation option was broken for devices running Android >= 14 (#4011).

It has been replaced by a more general option --capture-orientation, implemented using OpenGL filters:

scrcpy --capture-orientation=0
scrcpy --capture-orientation=90       # 90° clockwise
scrcpy --capture-orientation=180      # 180°
scrcpy --capture-orientation=270      # 270° clockwise
scrcpy --capture-orientation=flip0    # hflip
scrcpy --capture-orientation=flip90   # hflip + 90° clockwise
scrcpy --capture-orientation=flip180  # hflip + 180°
scrcpy --capture-orientation=flip270  # hflip + 270° clockwise

The capture orientation can be locked by using a @ prefix, so that a physical device rotation does not change the captured video orientation:

scrcpy --capture-orientation=@         # locked to the initial orientation
scrcpy --capture-orientation=@0        # locked to 0°
scrcpy --capture-orientation=@90       # locked to 90° clockwise
scrcpy --capture-orientation=@180      # locked to 180°
scrcpy --capture-orientation=@270      # locked to 270° clockwise
scrcpy --capture-orientation=@flip0    # locked to hflip
scrcpy --capture-orientation=@flip90   # locked to hflip + 90° clockwise
scrcpy --capture-orientation=@flip180  # locked to hflip + 180°
scrcpy --capture-orientation=@flip270  # locked to hflip + 270° clockwise

Now, it also works for camera (fixing #4426) and virtual displays.

Custom rotation

A new option --angle allows to rotate the content by a custom angle. Combined with --crop, this is especially useful for mirroring the Meta Quest 3 (#4135, #4345, #4658).

Virtual display rotation

The new virtual display feature initially could not rotate. The rotation has been implemented using OpenGL filters.

(That is what triggered the development of OpenGL filters.)

Like previously, the current app can be rotated by MOD+r (shortcuts).

Screen off timeout

The existing option --stay-awake only keeps the device awake *while it is plugged in, meaning it typically does not work over TCP/IP.

A new option, --screen-off-timeout, modifies the screen-off timeout setting while scrcpy is running and restores it on exit:

scrcpy --screen-off-timeout=300  # 300 seconds (5 minutes)

Static builds

For convenience, static builds are now provided for Linux and macOS (#5515).

More targets might be added in the future.

This is still experimental for now, so if you encounter problems, please report them.

Features you might have missed

If you haven't tried scrcpy in a while, here are some features introduced in the 2.x versions that you might have missed (check the release notes to each version for more details):

8
Kagi Search Changelog Nov 19th, 2024 - Enhanced Image Search & Open Sourcing FastFeedParser (kagi.com)
 

Image search becomes even better !

We're excited to roll out major upgrades to our image search. This release includes:

  • Our image search became even better with the inclusion of two more sources: Yandex Image Search (widely recognized as one of best image search services) and Openverse (vast collection of openly licensed images). Kagi is doing the hard work so that you don't have to.

  • Enhanced generative AI image detection and flagging (first version of which we launched last month)

  • A revamped preview pane with included reverse image search functionality

With this we believe we can say that Kagi has the most powerful image search on the web.

FastFeedParser - high performance library for processing feeds

We open sourced FastFeedParser, a high performance RSS, Atom and RDF parser in Python.

This library powers Kagi Small Web and a few other initiatives at Kagi and is 10x-100x faster and more efficient at parsing feeds than existing alternatives.

FastFeedParser joins over a dozen Kagi open-source software projects.

Improvements and Bug Fixes

Kagi Translate

Two weeks ago we launched Kagi Translate to raving reviews and great reception.

We have a number of improvements and more is scheduled.

  • Added PWA manifest so you can add Kagi Translate your home screen while we are developing the app
  • Switch language button also switches text
  • Fixed parsing for some websites in Translate @kdh8219
  • Fixed unicode/Japanese issues @Kate-Karui
  • Support for bangs/translating with just URL params @christophe
  • Skip translating code blocks @imlonghao
  • Fix: character counter
  • Fix: clicked links on a translated page do not lead anywhere
  • Fix: links not working on translated pages
  • Fix: Translate auth in Android app
  • Fix: Prоblеmѕ whеn іt dеtесtѕ thе ѕаmе lаnguаgе аѕ tаrgеt

Kagi Search

The Assistant

This week on social media

Connect with us on social media! Tag our account or use #Kagi to share your thoughts and join the conversation.

Here is this week's featured social media mention:

31
Release v0.6.0 · ilya-zlobintsev/LACT (github.com)
 

This is a big release, adding several new major features:

  • Nvidia support! LACT now works with Nvidia GPUs for all of the core functionality (monitoring, clocks configuration, power limits and fan control). It uses the NVML library, so unlike the Nvidia control panel it doesn't rely on X11 extensions and works under Wayland.
  • Multiple profiles for configuration. Currently it is not possible to switch them automatically, but they are configurable through the UI or the unix socket.
  • Clocks configuration now works on AMD IGPUs (at least RDNA2). Previously it was not parsed properly due to lack of VRAM settings.
  • Zero RPM mode settings on RDNA3. Currently this needs a linux-next to be used, and the functionality is expected to land in kernel 6.13. But this resolves a long-standing issue with RDNA3 that made the fan always disabled below a certain temperature, even if using a custom curve.

There are many other improvements as well, such as better looking and more efficient plots rendering in the historical charts window (thanks to @In-line ) and a Fedora COPR repository providing LACT packages (currently in testing).

Nvidia showcase:
image image

Full list of changes:

🚀 Features

  • Add support for multiple settings profiles (#327)
  • Show dialog when attempting to reconnect to daemon
  • Include device info and stats responses in debug snapshot
  • Improve plot rendering, use supersampling and do it in a background thread
  • [breaking] Add initial Nvidia support (#388)
  • Implement clocks control on Nvidia (#398)
  • Add special case for invalid throttle mask
  • Add snapshot command to CLI
  • Add RDNA3 zero RPM setting (#393)

🐛 Bug Fixes

  • Getting pci info in snapshot
  • Retry reading p-states if the value is nonsensical
  • Increase retry intervals when evaluating GPUs at start
  • Make throttling flags ellipsized to avoid massively oversized window (#402)
  • Deduplicate throttle status bits
  • Update amdgpu-sysfs with iGPU fixes, add steam deck quirk (#407)
  • Fedora spec non-default builds (#410)

🚜 Refactor

  • Make info page a relm component (#404)
  • Drop redundant ClockSettings structure in the ui

📚 Documentation

  • Update issue template to mention common RDNA3 problems
  • Fix issue template yaml
  • Move description to label in issue template

⚙️ Miscellaneous Tasks

  • Bump version
  • Update docs, enforce minimum rust version
  • Set codegen-units=1 to decrease binary size in release (#390)
  • Include service log in debug snapshot
  • Drop old bench feature
  • Bump dependencies
  • Bump version
  • Remove unused Cargo features (#405)

Developer

  • Automatically create release on tag push
  • Trigger workflow on tag push
  • Bump workflow rust version
  • Add debug builds to makefile
  • Skip building signed packages if signing secret is not found
  • Don't run rust checks on master pushes, only PRs

Packaging

  • Add libdrm to debian dependencies
  • Add fedora 41 package (#399)
  • Generate Spec Files for COPR on Release Publish (#406)
  • Drop invalid copr trigger check
20
Release v0.6.0 · ilya-zlobintsev/LACT (github.com)
 

This is a big release, adding several new major features:

  • Nvidia support! LACT now works with Nvidia GPUs for all of the core functionality (monitoring, clocks configuration, power limits and fan control). It uses the NVML library, so unlike the Nvidia control panel it doesn't rely on X11 extensions and works under Wayland.
  • Multiple profiles for configuration. Currently it is not possible to switch them automatically, but they are configurable through the UI or the unix socket.
  • Clocks configuration now works on AMD IGPUs (at least RDNA2). Previously it was not parsed properly due to lack of VRAM settings.
  • Zero RPM mode settings on RDNA3. Currently this needs a linux-next to be used, and the functionality is expected to land in kernel 6.13. But this resolves a long-standing issue with RDNA3 that made the fan always disabled below a certain temperature, even if using a custom curve.

There are many other improvements as well, such as better looking and more efficient plots rendering in the historical charts window (thanks to @In-line ) and a Fedora COPR repository providing LACT packages (currently in testing).

Nvidia showcase:
image image

Full list of changes:

🚀 Features

  • Add support for multiple settings profiles (#327)
  • Show dialog when attempting to reconnect to daemon
  • Include device info and stats responses in debug snapshot
  • Improve plot rendering, use supersampling and do it in a background thread
  • [breaking] Add initial Nvidia support (#388)
  • Implement clocks control on Nvidia (#398)
  • Add special case for invalid throttle mask
  • Add snapshot command to CLI
  • Add RDNA3 zero RPM setting (#393)

🐛 Bug Fixes

  • Getting pci info in snapshot
  • Retry reading p-states if the value is nonsensical
  • Increase retry intervals when evaluating GPUs at start
  • Make throttling flags ellipsized to avoid massively oversized window (#402)
  • Deduplicate throttle status bits
  • Update amdgpu-sysfs with iGPU fixes, add steam deck quirk (#407)
  • Fedora spec non-default builds (#410)

🚜 Refactor

  • Make info page a relm component (#404)
  • Drop redundant ClockSettings structure in the ui

📚 Documentation

  • Update issue template to mention common RDNA3 problems
  • Fix issue template yaml
  • Move description to label in issue template

⚙️ Miscellaneous Tasks

  • Bump version
  • Update docs, enforce minimum rust version
  • Set codegen-units=1 to decrease binary size in release (#390)
  • Include service log in debug snapshot
  • Drop old bench feature
  • Bump dependencies
  • Bump version
  • Remove unused Cargo features (#405)

Developer

  • Automatically create release on tag push
  • Trigger workflow on tag push
  • Bump workflow rust version
  • Add debug builds to makefile
  • Skip building signed packages if signing secret is not found
  • Don't run rust checks on master pushes, only PRs

Packaging

  • Add libdrm to debian dependencies
  • Add fedora 41 package (#399)
  • Generate Spec Files for COPR on Release Publish (#406)
  • Drop invalid copr trigger check
37
DXVK Version 2.5 (github.com)
 

Memory managment

Resource and memory management were completely rewritten in order to use allocated video memory more efficiently:

  • Reduced fragmentation may reduce peak memory usage in games such as God of War by up to 1 GiB in extreme cases.
  • Memory defragmentation is now performed periodically to return some unused memory back to the system. The goal is not to reduce VRAM usage at all costs; instead this is done conservatively if the system is under memory pressure, or if a significant amount of allocated memory is unused. Keeping some unused memory is useful to quickly service subsequent allocations.

Note: Defragmentation is currently disabled on Intel's ANV driver, see #4434. The dxvk.enableMemoryDefrag config option can be set to enable or disable this feature via the the Configuration file.

Driver support

While technically not required, the new memory management works best on drivers that support both VK_EXT_memory_budget and VK_KHR_maintenance5. The Driver Support page was updated accordingly.

D3D8 / D3D9

Software cursor

Support for emulated cursors was implemented for the D3D9 cursor API, which allows games to set an arbitrary image as the mouse cursor. This fixes an issue in Dungeon Siege 2 (#3020) and makes the cursor appear correctly in Act of War and various older D3D8 games. (PR #4302)

Bildschirmfoto-693

Sampler pool

Unreal Engine 3 games using D3D9 have a quirk in that they pass a seemingly uninitialized value as the mipmap LOD bias. In order to avoid creating more Vulkan sampler objects than the driver supports, previous versions of DXVK would round the LOD bias to a multiple of 0.5, which could introduce visual inaccuracies. As a more correct soluition, DXVK will now destroy unused Vulkan samplers on the fly and use the correct LOD bias.

Note: The aforementioned workaround was never needed or used in the D3D11 implementation, it only affected D3D9.

Bug fixes and Improvements

  • On Nvidia driver version 565.57.01 and newer, strict float emulation is enabled by default for improved correctness. Games for which this option was already enabled may see a small performance uplift on this driver.
  • Made various changes to potentially improve performace on certain mobile GPUs. (includes PR #4358)
  • Display modes are now ordered by refresh rate to be more consistent with wined3d and fix issues with some games picking the wrong display mode.
  • Fixed a large number of wine test failures.
  • Ascension to the Throne: Fixed old regression that would cause parts of the ground to render black. (#4338, PR #4341)
  • Command & Conquer: Generals: Fixed performance issue caused by a missing D3D8 entry point. (PR #4342)
  • King's Bounty: Warriors of the North: Fixed water rendering issue. (#4344, PR #4350)
  • Tomb Raider: Legend: Fixed flickering geometry with strict float emulation. (#4319, PR #4442)
  • Rayman 3: Fixed a regression that caused rendering issues. (#4422, PR #4423)

D3D11 / DXGI

Resource management changes

In order to reduce system memory pressure and improve stability in 32-bit games, creating, uploading and discarding resources is now throttled if the amount of temporary staging memory allocations exceed a certain threshold. This fixes crashes in Total War: Rome II and a number of other games. Additionally, large DYNAMIC textures commonly used for video playback will no longer use a staging buffer.

The d3d11.maxDynamicImageBufferSize and d3d11.maxImplicitDiscardSize options were removed accordingly; affected games such as Total War: Warhammer III and Ryse: Son of Rome should now perform well by default, without excessive memory usage.

Note: These changes negatively affect CPU-bound performance in a number of games, including Shadow Warrior 2.

Bug fixes and Improvements

  • SEQUENTIAL swap effects are now implemented for DXGI swap chains, which allows games to read previously presented backbuffers. This fixes an issue wherein savegame thumbnails would appear black in certain visual novels. (https://github.com/ValveSoftware/Proton/issues/7017)
  • Devirtualized some D3D11 method calls to improve compatibility with Special K.
  • Fixed incorrect shader code generation for EvaluateAttributeSnapped.
  • Lock contention is reduced in certain games that use Deferred Contexts for rendering. This may improve performance on older CPUs in Sekiro: Shadows Die Twice and some other games.
  • Call of Duty: Modern Warfare 2 Campaign Remastered: Fixed a possible GPU hang. (#3884)
  • Diablo 4: Work around an issue where the game does not start if an integrated GPU is exposed.
  • The Sims 4: Work around a use-after-free bug in the game's D3D11 renderer for real this time. (#4360)
  • Vindictus: Work around potential rendering issues caused by uninitialized constant buffer data. (#4405, #4406)
  • Yakuza 0 and Yakuza Kiwami: Fixed a regression introduced in DXVK 2.4.1 that would cause these games to lock up on start. (PR #4297)

Miscellaneous changes

  • An SDL3 backend was added for dxvk-native. (PR #4326, #4404)
  • Fixed an issue introduced in DXVK 2.4.1 which would lead to error messages about failed buffer creation.
  • Fixed a long-standing issue where overlapping occlusion queries would lead to incorrect Vulkan usage. (#2698)
  • Fixed a rare issue wherein timestamp queries would not be tracked correctly and could read incorrect data.
  • Fixed various other issues that led to Vulkan validation errors in games such as Dishonored 2, Tales of Arise and The Sims 4.
  • Fixed various issues with MSVC builds. (PR #4444)
  • Disabled a workaround for boken render target clears on Nvidia drivers prior to version 560.28.03 on unaffected drivers.
  • If supported, VK_EXT_pageable_device_local_memory is now used to enable better driver-side memory management.
13
Kagi Translate - We speak your language | Kagi Blog (blog.kagi.com)
 

Today, we’re introducing Kagi Translate. It’s not revolutionary - it’s simply a better translation service.

Our combination of advanced language models and precise output selection delivers translations that surpass existing solutions, including Google Translate and DeepL.

Here’s a comparison table for main features:

Feature Google Translate DeepL Kagi Translate
Quality Average High Very High
Webpage translation Yes No Yes (most)
Languages supported 243 33 244

*Quality ratings based on internal testing and user feedback
*Language count as of November 2024

For quick translations, documents, or daily browsing, the difference is clear in the first sentence.

Try it:

Try Kagi Translate with any text →

Translate this blog post into Spanish → (note the simple URL structure)

Using Kagi Translate

Add translate.kagi.com/ before any URL for instant translation. No apps needed. Access 244 languages with zero tracking. Install our browser bookmarklet for quick access.

KagiTranslate

Visit translate.kagi.com for direct use.

We will be bringing Kagi Translate soon inside Kagi Search as a widget for instant translation inside search results.

Kagi Translate is free for everyone. If you’re not a logged in Kagi user, you’ll encounter a simple captcha to prevent automated abuse - a small step that helps us maintain quality while keeping the service free. Kagi members get direct access without captchas, integrating seamlessly with their existing workflow.

Limitations

We do not translate dynamically created content (eg. pages where content is loaded with JavaScript) or paywalled pages.

Kagi Translate uses a combination of LLMs, selecting and optimizing the best output for each task. While this creates immensey powerful translation capabilities, it can occasionally lead to quirks that we’re actively working to resolve.

If you encounter issues or want to suggest improvements (or just want to share your most ridiculous Google Translate fail), please send us feedback. This is our first release and expect many improvements down the road.

Next

This isn’t just about better translation. It’s about raising standards in everyday tools. We believe that privacy and quality can coexist, that powerful tools don’t need to track their users, and that the best technology should simply work without compromises for the user.

Kagi Translate joins our suite of tools (‘treats’): Small Web, Universal Summarizer, and FastGPT alongside Kagi Search and Orion Browser.

Transform your internet experience - become a Kagi member. Access the world’s most powerful search engine and help create a future where digital tools serve their users – not the interest of third parties or advertisers.

4
Kagi Search Changelog Nov 7th, 2024 - Announcing Kagi Translate (kagi.com)
 

Announcing Kagi Translate

Never get lost in translation again. Today, we launch Kagi Translate, offering superior translations across 244 languages.

Key features:

  • Higher quality translations than Google Translate and DeepL
  • Zero tracking, no apps needed
  • Free for everyone (Kagi members get captcha-free access)

Try it now at translate.kagi.com or read the announcement post.

Kagi on mobile

We've added search buttons to our homepage to make it easier for you to choose your search type on mobile:

Install Kagi for Android and help us reach 5,000 installs needed for Kagi to submit application for Android choice screen.

Kagi iOS app is currently pending Apple review.

What else are we working on?

We are currently working on Kagi for Teams plan. This will allow you to bring your entire team or organization to Kagi. We'll have two options available: Professional and Ultimate tier, with fair and flexible pricing (inactive team members do not pay). We expect to launch in two weeks. Let us know if you would like to test this earlier by emailing support@kagi.com.

Improvements and bug fixes

Bangs

This release includes several new bangs and a significant cleanup of older ones. You can read the full changelog here. These changes were driven by our community, and we appreciate all contributions to our open source Bangs repo!
Here's a preview of our latest additions:

  • !attack: search site:attack.mitre.org
  • !jsr: jsr.io
  • !fast: moved to FastGPT
  • !javadoc: Java 23 API docs, docs.oracle.com/en/java/javase/23/docs/api/search
  • !startech: startech.com
  • dropout: dropout.tv

Kagi in the wild

Here is this week's featured social media mention:

Tag our account or use #Kagi when mentioning us in your posts!

67
VMware Workstation Shifting From Proprietary Code To Using Upstream KVM (www.phoronix.com)
4
Kagi Search Changelog Oct 24th, 2024 - Safer Video Search for Kids and Custom Assistant Bangs (kagi.com)
 

Leveling up our infrastructure

This Sunday at 6am UTC, we're making a step forward on our production infrastructure.

After years of faithful service, our original database server is being replaced with significantly more powerful hardware.

Expected downtime: 10 minutes

Protecting young minds: Enhanced video safety for families

Your children deserve better than clickbait and shock value. We're making it happen with advanced video controls.

Family account owners can now shape a safer, cleaner video experience for family members:

Authentic thumbnails

  • Replace misleading clickbait with actual video screenshots
  • See what you're really getting before clicking
  • End the bait-and-switch

Clean video titles

  • Choose between title case or lowercase formatting
  • Create a consistent, distraction-free experience
  • Focus on content, not hype

Example (click to enlarge):

To access these options, navigate to: Settings > Parental Controls (section: Video Search Settings) or click here.

Why this matters

Recent research confirms a disturbing truth: children's video searches frequently expose them to inappropriate content, violence, and frightening images. We believe our children deserve better. Kagi's new parental controls help parents better manage the video content their children are exposed to, reducing the risk of exposure to inappropriate content and creating a safer online experience for them.

Help us protect more young minds - share your thoughts on making this protection available more broadly to all plan types. In case you wonder why we did not make this option enabled by default - video thumbnails and titles serve as a marketing tools for content creators, and changing them unilaterally would introduce us as a biased intermediary on a matter that is still in the air. This could have a negative impact for publishers and potentially conflict with our mission to "humanize the web". It is a delicate issue, and this is why we had propagated the control over this to the user level, as with all personalization features in Kagi.

Custom Assistant Bangs

Launch your Custom Assistant instantly from anywhere with a Bang shortcut. Simply set your preferred command and you're ready to go.

This seamless integration means your Assistant is always just a keystroke away, whether you're researching, writing, or exploring new ideas.

Improvements and bug fixes

  • We fixed many issues causing interruptions with the Assistant. please let us know if you see any further issues.
  • Standalone bang shortcut ignores snap #5083 @tuesday
  • Timer shown for unrelated query #4103 @azdanov
  • Duplicate video results #4306 @loloriz
  • Z-index on icon covers tooltip #4849 @bebowilson
  • Custom bangs that override builtin bangs no longer work #5148 @avkiselev
  • Focus address field after clicking reverse image search button #4906 @tuesday
  • Override the ai downranking if you are searching ai images #5082 @Thibaultmol
  • Quick answer weird code block formatting #4770 @timo
  • Background for Advanced search in dark mode is too light #4586 @eirk
  • Keep focus on the search field upon accepting suggestion #4973 @xdc
  • Pricing page translation typo #4596 @Albi
  • !gflights incorrect target #5132 @Connor
  • Untimely redirect when typing a verse #5107 @X145678908765
  • Assistant: Option to use Shift+Enter to send prompt instead of just Enter #2121 @Value7609
  • Enhancement Request: Customizable Multiple AI Assistant Prompts with User-Defined !bang Commands #2183 @ZarK
  • Assistant input text box stubbornly places itself under the keyboard #4902 @gunslingerfry
  • New Assistant - Touch Issues on Mobile (Dynamic Viewport Resizing, Covering Sources) #4835 @silvenga
  • Microphone on assistant doesn't work #5105 @sleepysnooze
  • Assistant web search gets stuck #5025 @azdanov
  • Typo in the FAQ #5079 @duck

Join the Kagi revolution in the wild!

Here are all the cool places you can find us at:

Use #Kagi when mentioning us in your posts! Which brings us to this week's featured post from social media:

We also have a Kagi Community Discord server where you can join our community for real-time discussion about the product and chat with other Kagi users. There is also /r/SearchKagi on Reddit - steadily growing unofficial community.

Thank you for being a vital part of our journey - your support inspires us every day, and we can’t wait to see where this adventure takes us next! 🙏

244
Bitwarden update: sdk-internal now GPL, sdk/sdk-secrets to remain proprietary but not used in clients (github.com)
 

@brjsp thanks again for submitting the concern here. We have made some adjustments to how the SDK code is organized and packaged to allow you to build and run the app with only GPL/OSI licenses included. The sdk-internal package references in the clients now come from a new sdk-internal repository, which follows the licensing model we have historically used for all of our clients (see LICENSE_FAQ.md for more info). The sdk-internal reference only uses GPL licenses at this time. If the reference were to include Bitwarden License code in the future, we will provide a way to produce multiple build variants of the client, similar to what we do with web vault client builds.

The original sdk repository will be renamed to sdk-secrets, and retains its existing Bitwarden SDK License structure for our Secrets Manager business products. The sdk-secrets repository and packages will no longer be referenced from the client apps, since that code is not used there.

This appears at least okay on the surface. The clients' dependency on sdk-internal didn't change but that's okay now because they have licensed sdk-internal as GPL.

The sdk-secrets will remain proprietary but that's a separate product (Secrets Manager) and will apparently not be used in the regular clients. Who knows for how long though because, if you read carefully, they didn't promise that it will not be used in the future.

The fact that they had ever intended to make parts of the client proprietary without telling anyone and attempted to subvert the GPL while doing so still remains utterly unacceptable. They didn't even attempt to apologise for that.

Bitwarden has now landed itself in the category of software that I would rather move away from and cannot wholeheartedly recommend anymore. That's pretty sad.

view more: ‹ prev next ›