Atemu

joined 5 years ago
MODERATOR OF
[–] Atemu@lemmy.ml 1 points 6 months ago (2 children)

Well then it sounds like it works just fine but your chosen value isn't stable.

[–] Atemu@lemmy.ml 3 points 6 months ago

Friggin Emoji Speak lmao.

I highly recommend you try to translate some news article to emoji speak; it's awful/great:

https://translate.kagi.com/Emoji%20Speak/https://www.theregister.com/2025/01/10/german_router_maker_avm_lgpl

I just had a browse through the languages to find the novelty ones and was quite surprised to see how long the list has gotten. It can translate to friggin Welsh and can even TTS it. I don't speak Welsh but it sounded entirely incomprehensible, so it must be quite accurate.
It can TTS all the languages in fact; even Elvish. Quite impressive honestly and it's getting to the point where Kagi translate could be a part of the subscription that holds significant value.

The purposes I most use translation services for is to look up singular words in English because I forgot the term in my mother tongue but Kagi isn't very good at that yet; classic dictionary service still beat it by a long shot.
It'd be great if Kagi could at least show alternative translations like Deepl does; I sometimes use that service.

Translating some entire article in an unfamiliar language though, that's where I can really see myself relying on it.

I didn't know I'd like to see them build it but I'd love to see this fleshed out further now that they have.

[–] Atemu@lemmy.ml 1 points 6 months ago

You can also just do the initial import on a NAS. It might take a day perhaps but, honestly, does that matter?

[–] Atemu@lemmy.ml 2 points 6 months ago

I'd suspect the bots would just try again with a masked user agent when they receive a 403.

I think the best strategy would be to feed the bots shit that looks like real content.

[–] Atemu@lemmy.ml 3 points 6 months ago* (last edited 6 months ago)

VR is pain enough as is; adding a Laptop with weird GPU setups into the mix is going to be even more pain.

Oh, this is the Linux gaming community. Multiply the pain by 10.

[–] Atemu@lemmy.ml 7 points 6 months ago (1 children)

The originals remain untouched.

It is possible to override existing commands with aliases though. This is useful for setting flags by default. I have alias ls='ls --color' for instance such that whenever I run ls, it actually runs ls --color, providing colourful output.

Note that aliases are only a concept within your command line shell though. Any other program running ls internally won't have the flag added and wouldn't be able to use any of the other aliases either (not that it would know about them).

It's very easy to program your own "proper" commands though on Linux. If you had some procedure where you execute multiple commands in some order with some arguments that may depend on the outputs of previous commands, you could write all that as a shell script, give it some custom name, put it in your $PATH and run it like any other command.

[–] Atemu@lemmy.ml 8 points 6 months ago (3 children)

You could make aliases that are easier to remember for you.

If you e.g. had trouble remembering that mv does a rename, you could alias rename=mv. Ideally just put whatever you would have googled in "linux command to x" as the alias.

That's the power of Linux; you can tweak everything to your preferences and needs.

[–] Atemu@lemmy.ml 2 points 6 months ago (1 children)

There's nothing further I can tell you. You'll need to figure out which parts those sensors correspond to to draw any sort of conclusion.

I'd recommend you try the out-of-tree driver I linked. You can just rmmod the normal one and insmod the custom one at runtime.

[–] Atemu@lemmy.ml 6 points 6 months ago

The web version works without an account? That'd be news to me.

[–] Atemu@lemmy.ml 4 points 6 months ago (3 children)

First of all you need to figure out which sensor this even is. On my nct6687, there's a sensor on the PCIe slot that is constantly >90° and that appears to be totally normal.

Could you post the output of sensors?

Here is how it looks like on my machine:

nct6687-isa-0a20
Adapter: ISA adapter
+12V:           12.26 V  (min = +12.14 V, max = +12.46 V)
+5V:             5.06 V  (min =  +5.00 V, max =  +5.08 V)
+3.3V:           0.00 V  (min =  +0.00 V, max =  +3.40 V)
CPU Soc:         1.02 V  (min =  +1.02 V, max =  +1.04 V)
CPU Vcore:       1.27 V  (min =  +0.91 V, max =  +1.40 V)
CPU 1P8:         0.00 V  (min =  +0.00 V, max =  +0.00 V)
CPU VDDP:        0.00 V  (min =  +0.00 V, max =  +0.00 V)
DRAM:            1.11 V  (min =  +1.10 V, max =  +1.11 V)
Chipset:       202.00 mV (min =  +0.18 V, max =  +0.36 V)
CPU SA:          1.08 V  (min =  +0.61 V, max =  +1.14 V)
Voltage #2:      1.55 V  (min =  +1.53 V, max =  +1.57 V)
AVCC3:           3.39 V  (min =  +3.32 V, max =  +3.40 V)
AVSB:            0.00 V  (min =  +0.00 V, max =  +3.40 V)
VBat:            0.00 V  (min =  +0.00 V, max =  +2.04 V)
CPU Fan:        730 RPM  (min =  718 RPM, max = 1488 RPM)
Pump Fan:         0 RPM  (min =    0 RPM, max =    0 RPM)
System Fan #1:    0 RPM  (min =    0 RPM, max =    0 RPM)
System Fan #2:  490 RPM  (min =  421 RPM, max =  913 RPM)
System Fan #3:    0 RPM  (min =    0 RPM, max =    0 RPM)
System Fan #4:  472 RPM  (min =  458 RPM, max =  939 RPM)
System Fan #5:    0 RPM  (min =    0 RPM, max =    0 RPM)
System Fan #6:    0 RPM  (min =    0 RPM, max =    0 RPM)
CPU:            +37.0°C  (low  = +30.0°C, high = +90.0°C)
System:         +25.0°C  (low  = +22.0°C, high = +48.0°C)
VRM MOS:        +22.0°C  (low  = +20.5°C, high = +66.0°C)
PCH:            +21.5°C  (low  = +18.5°C, high = +49.0°C)
CPU Socket:     +21.0°C  (low  = +19.0°C, high = +56.5°C)
PCIe x1:        +92.0°C  (low  = +76.5°C, high = +97.0°C)
M2_1:            +0.0°C  (low  =  +0.0°C, high =  +0.0°C)

Note that I use the https://github.com/Fred78290/nct6687d/ kernel module though. The upstream one doesn't label many temps.

[–] Atemu@lemmy.ml 1 points 6 months ago

I wouldn't go ARM unless you really like tinkering with stuff.

I bought a used Celeron J4105-based system years ago for <100€ and it's doing just fine. The N100 is its successor that should be better in every way.

Don't be afraid to buy cheap used hardware. Especially things like RAM or cases that don't really ever break in normal usage.

Two 4TB HDDs for 120€ each is a rip-off. That's twice what you pay per GB in high capacity drives. Even in the lower capacity segment you can do much better such as 6TB for 100€.

If you have proper (tested!) backups and don't have any specific uptime requirements, you don't need RAID. I'd recommend getting one 16TB-20TB drive then. That would only cost you as much as those two overpriced 4TB drives.

[–] Atemu@lemmy.ml 10 points 6 months ago

I generally prefer to not get shit in my mouth at all but you do you.

 

@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.

 

@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-secret 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.

 

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

I recently switched from a MBP to a Framework 16 as my primary laptop and one thing I immediately noticed was that I was unable to stop kinetic scrolls in Firefox by laying my fingers onto the touchpad. It'd just slide by unimpeded. You could work around this by counter-scrolling a little rather than holding still which is how I've been coping with it but it's suboptimal to say the least.
(As are many things in the Linux touchpad experience. Linux desktop developers really ought to use a macbook for a little to get a sense for how to do this properly.)

This was caused by Firefox' use of GDK3 to implement its windowing and input needs which does not support hold gestures.

GDK4 does support them but, as I understand it, a port of Firefox to GDK4 would be a ton of work and there isn't really much desire for it as GDK4 doesn't offer many real advantages over GDK3 as Firefox doesn't use classical GTK widgets or anything and only really uses it for basic input/output primitives.

A backport to handle hold gestures in GDK3 too was attempted but, in classic GNOME fashion, it was rejected.

The implementation now somehow gets events from the touchpad directly via wayland somehow from what I could gather but if it works, it works.

You can try this out in the latest nightly builds.

 

I recently switched from a MBP to a Framework 16 as my primary laptop and one thing I immediately noticed was that I was unable to stop kinetic scrolls in Firefox by laying my fingers onto the touchpad. It'd just slide by unimpeded. You could work around this by counter-scrolling a little rather than holding still which is how I've been coping with it but it's suboptimal to say the least.
(As are many things in the Linux touchpad experience. Linux desktop developers really ought to use a macbook for a little to get a sense for how to do this properly.)

This was caused by Firefox' use of GDK3 to implement its windowing and input needs which does not support hold gestures.

GDK4 does support them but, as I understand it, a port of Firefox to GDK4 would be a ton of work and there isn't really much desire for it as GDK4 doesn't offer many real advantages over GDK3 as Firefox doesn't use classical GTK widgets or anything and only really uses it for basic input/output primitives.

A backport to handle hold gestures in GDK3 too was attempted but, in classic GNOME fashion, it was rejected.

The implementation now somehow gets events from the touchpad directly via wayland somehow from what I could gather but if it works, it works.

You can try this out in the latest nightly builds.

 

Better image search with AI-generated images detection

Last week we got quite clear and direct feedback that we need to do something about AI-generated images that started creeping up in the image search.

You asked for it and we delivered!

We are enhancing our image search with a new ranking algorithm and an AI image filter. These updates prioritise authentic, human-created images and downrank AI-generated content. Users can also opt to exclude AI-generated images entirely.

Learn more about Kagi's AI image filter here: https://help.kagi.com/kagi/features/exclude-ai-images.html

We will continue actively improving this feature based on your feedback.

Improvements and bug fixes

The Assistant

  • We've enhanced the Assistant mobile experience with several updates, including improvements to the thread view and header navigation
  • Kagi Assistant v2 mobile threads menu #4725 @frin
  • Kagi assistant gpt LLM not working #5055 @ash
  • Assistant Tooltips are Hard to Click #5037 @silvenga

Celebrating Our Community

At Kagi, we’re all about community, and nothing has made us prouder than seeing the incredible photos our members are sharing online of their Kagi swag! Whether you’ve posted a picture of your free t-shirt or a sticker proudly displayed on your laptop, we want to take a moment to say thank you. Your support means the world to us.

The story:

We were thrilled to celebrate our first big milestone: reaching 20,000 loyal members who’ve stuck with us through this adventure. To show our appreciation, we've sent out free t-shirts and sticker packs to those first 20,000 supporters. Earlier this month, these members started receiving their packages and excitedly shared photos across various socials. Here’s a snapshot of just a few:

For anyone who missed out, don’t worry! You can head over to the Kagi Store and snag your first-edition Doggo t-shirt. We’ve got four fantastic designs, each one representing our determination to build a better, more ethical and more human web.

Help us reach our next milestone: 50,000 members

As we gear up to reach 50,000 members, we’d love your help in spreading the word!

We don't rely on ads to drive our growth; instead, we depend entirely on word-of-mouth marketing and community recommendations. This grassroots approach means that every conversation you have about Kagi, every post you share showcasing your swag, and every mention you make to friends and family has a real impact. Your enthusiasm helps us reach new members who share our vision for a better web. Let’s make our next milestone one to remember.

Where to find and tag us on the social web:

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.

As we move forward, we want to reiterate our commitment to continuously improving Kagi for all our members. Your feedback and engagement are invaluable as we strive to create an even better experience. 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!

 

Josef Bacik who was working on this said:

I fixed up all your review comments, but yes we don't care about this internally anymore so it's been de-prioritized. I have to rebase onto the new stuff, re-run tests, fix any bugs that may have creeped in, but the current code addressed all of your comments. Once I get time to get back to this you'll have a new version in your inbox, but that may be some time.

(Note: This was back in April.)

 

Hello, Kagi Fans!

We know it's been a few weeks since our last update, and there's a good reason for that. The entire company took a break from the usual routine to fly to Barcelona, Spain, for our annual retreat - a chance to reenergize and refocus for the exciting journey ahead.

But don’t worry, it wasn’t all fun and no work. In fact, we’ve got a pretty exciting update for you today. The retreat gave us fresh inspiration, and we’re ready to bring some of those new ideas to life starting right now.

Launching the official Kagi Android app

We're delighted to announce the launch of the official Kagi Android app! This marks an important milestone in our mission to make Kagi Search more accessible and encourage more people to try it out.

https://play.google.com/store/apps/details?id=com.kagi.search

The app allows users to begin using Kagi Search immediately right from the first launch (no account needed!). For those with existing subscriptions, signing in is seamless, enabling access to all Kagi features.

Additionally, the app includes native homescreen widgets, providing one-click access to search directly from your homescreen.

If you use an Android device, go check it out! We've simplified the process of sharing Kagi with your network.

Additionally, a recent EU ruling presents a significant opportunity for Kagi. Google is now required to include any search engine that meets specific criteria, such as having an app with over 5,000 installs, in the default list for Android and Chrome — install the app today and help us meet the criteria!

Stay tuned for more exciting updates coming soon!

Introducing Snaps

Snaps are an innovative search operator that allows for site-specific searches directly from the search bar. By simply typing @ followed by the designated site bang, you can limit your search results to a specific website. For example, to search on Reddit or HackerNews, you can enter:

  • @r winter boots which translates to winter boots site:www.reddit.com
  • and @hn vim emacs to vim emacs site:news.ycombinator.com

This feature was made possible thanks to the contribution of our user @tuesday ( #1231) on Kagifeedback!

This will work with any bang that Kagi support, including custom bangs you define. Kagi Bangs are open source, we welcome your contributions!

Universal Summarizer for Chrome

Universal Summarizer is one of the most-loved Kagi treats. The extension is now available for Chrome - Download it here!

We had to split it out of Kagi Search extension for Chrome due to rules of the Chrome store. Kagi Universal Summarizer is available to Firefox users via Kagi Search for Firefox and is natively built into the Orion browser.

The Assistant - 30 day update

It's been 30 days since we launched the Assistant, and we're excited to share a range of new updates with you.

Upload functionality:
We're excited to announce that you can now upload a variety of local files directly to the Assistant! This new feature allows you to add multiple files in a single prompt. Here's a list of supported file types:

  • Text files: .txt, .md
  • Rich text documents: .pdf, .docx, .pptx
  • Tabular data files: .json, .csv, .xlsx, ...
  • Images: .jpeg, .png, .webp, ...
  • Audio files: .mp3, .wav, .m4a, ...

Additionally, you can add a URL to have its contents summarised or to pose questions about it.

Stop button
We've introduced a Stop button that allows users to immediately halt the Assistant's streaming output.

Mobile improvements
And also made several enhancements to our mobile experience, and there's even more on the way!

Plus many other Assistant improvements

  • Give assistant a PWA manifest #4734 @Thibaultmol
  • Add Stop button for AI assistants #4034 @andrew-rivera
  • Multiline assistant queries on mobile #4693 @fxgn
  • Added Llama405b model to the list of available models in the Assistant
  • Assistant v2 Text Input Form increases with use #4799 @DaJonas
  • Session Link for Kagi Assistant #4772 @melomac
  • Assistant V2 initial prompt text field doesn't scroll #4739 @Thibaultmol
  • Kagi Assistant UI Issues #4729 @emptyjar
  • Browsing to https://kagi.com/assistant when not logged in results in 404 #4765 @cmart
  • [firefox] text box in assistant text box can display funny at wrap point #4002 @sbeckeriv
  • Universal summarizer can't find transcript: yet finds transcript for slightly different URL edition #4451 @leftium
  • Assistant history vanishes temporarily after branching #4686 @Value7609
  • Assistant v2. Custom LLM settings not persistent. #4672 @flokerama
  • New Assistant Beta looks bad in Safari #4675 @Rudotel
  • Assistant does not respect lens when searching #4756 @double
  • Assistant - Broked Fonts #4837 @silvenga
  • Assistant not respecting multiple lines. #4764 @tombert
  • Opus 3 interacting poorly with internet access #4804 @artemvmin
  • Assistant (V2): make the 'send' button in the chat gray as long as the llm is still 'typing' #4738 @Thibaultmol
  • Claude models are confused about internet access in Assistant with Web Access #4843 @Nashwan
  • Model name is intersecting the assistant answer on mobile #4694 @fxgn
  • Completely innacurate assistant context #4667 @tinkling6961
  • Assistant - Inconsistant "New Tab" Behavior #4909 @silvenga
  • New Assistant - Asking to Search #4794 @silvenga
  • New Kagi Assistant has lost the ability to parse line breaks #4778 @orb
  • Impossible to copy the code while the response is still being displayede #4848 @kfbme
  • Assistant.v2 firefox issues with scrolling to bottom #4662 @zut
  • Assisant 'internet=off' is ignored #4965 @Thibaultmol
  • The buttons on the bottom of a thread (copy, regenerate, info) shouldn't be inactive depending on how far you scrolled #4831 @chris_20017
  • Assistant v2 Text Input Form increases with use #4799 @DaJonas
  • An unknown error has occured in assistant #4988 @oNco
  • Assistant mode adding redundant newlines on paste #4845 @pravinxor
  • Code font is giant on phone for assistant #4797 @tombert
  • Universal Summarizer dropdown values unreadable in Dark mode #4749 @Christoph
  • Assistant V2beta character display error #4673 @OxygenX
  • Assistant thread UI buttons on Firefox mobile don't work #4805 @tinkling6961
  • Paste an image in research assistant to chat about it #4028 @hadario
  • The Assistant input box isn't cleared when submitting a prompt using the microphone if the device keyboard has been used #4923 @laiz
  • Copy the search prompt to the assistant prompt when "The Assistant" button is clicked on the search page #5005 @webwalrus

Search improvements and bug fixes

 

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

Write is a handwriting app that works on a lot of platforms including Linux which cannot be said about most handwritten note-taking applications.

More information and demo: https://github.com/styluslabs/Write/

I've used it for uni on a Linux tablet/convertible and it worked really quite well and has some nice convenient features for note-taking.

The UI looks like it's from android 4.something though ^^'

What I really appreciate about it is that its storage format are plain SVG(Z) which are extremely compatible. All you need to view your scribbles is an SVG viewer (i.e. a web browser) which basically every computer with a GUI has. Their website is in fact mostly just the output of their own app.

 

Write is a handwriting app that works on a lot of platforms including Linux which cannot be said about most handwritten note-taking applications.

More information and demo: https://github.com/styluslabs/Write/

I've used it for uni on a Linux tablet/convertible and it worked really quite well and has some nice convenient features for note-taking.

The UI looks like it's from android 4.something though ^^'

What I really appreciate about it is that its storage format are plain SVG(Z) which are extremely compatible. All you need to view your scribbles is an SVG viewer (i.e. a web browser) which basically every computer with a GUI has. Their website is in fact mostly just the output of their own app.

 

Match starts at 27:15

view more: ‹ prev next ›