What a weird situation. I suppose it’s nice those workarounds exist, even if they’re not ideal.
What a weird situation. I suppose it’s nice those workarounds exist, even if they’re not ideal.
Interesting! I assume it involves a smart plug and an automation script that monitors battery level?
Wow, Graphene really doesn’t have charging limits?
I assume this is the discussion you referred to, and I think it broke my trust in the project.
Edit: As far as I can tell, many of the frustrating parts of that thread are from random posters and not devs. I’m still annoyed that such a basic feature is considered controversial.
I expected to roll my eyes at this article but it’s actually quite compelling and well written. The Kagi website’s lack of nuanced privacy discussion already turned me off, and now I’m just going to pretend the service doesn’t exist.
I won’t be using these features, but I’m not sure there’s cause for concern. The implementation seems very sensible and legitimately privacy-centric. The LLM runs locally and is meant as an very basic email proofreader. The crypto wallet is a likely an extension of the password management tech they’ve already developed, with transaction features that some people care about.
I can see why some people want these features, and I’m glad there are new alternatives.