Hacker Newsnew | past | comments | ask | show | jobs | submit | anhner's commentslogin

Oh no, what if they put on Christmas music playlist in February? the horror!

There should exist something between "don't allow anything without unlocking phone first" and "leave the phone unlocked for anyone to access", like "allow certain voice commands to be available to anyone even with phone locked"


Playing music doesn’t require unlocking though, at least not from the Music app. If YouTube requires an unlock that’s actually a setting YouTube sets in their SiriKit configuration.

For reading messages, IIRC it depends on whether you have text notification previews enabled on the lock screen (they don’t document this anywhere that I can see.) The logic is that if you block people from seeing your texts from the lock screen without unlocking your device, Siri should be blocked from reading them too.

Edit: Nope, you’re right. I just enabled notification previews for Messages on the lock screen and Siri still requires an unlock. That’s a bug. One of many, many, many Siri bugs that just sort of pile up over time.


Can it not recognize my voice? I had to record the pronunciation of 100 words when I setup my new iPhone - isn’t there a voice signature pattern that could be the key to unlock?

It certainly should have been a feature up until now. However, I think at this point anyone can clone your voice and bypass it.

But as a user I want to be able to give it permission to run selected commands even with the phone locked. Like I don't care if someone searches google for something or puts a song via spotify. If I don't hide notifications when locked, what does it matter that someone who has my phone reads them or listens to them?


But you understand why if I don't care about that, I should be able to run it, right?

I understand why you'd want to do it.

Oddly enough I also understand Apple telling you, good luck, find someones platform that will allow that, that's not us.


you should look into using subagents, which each have their own context window and don't pollute the main one

and yet, there are obviously some companies that are better than others.

It offers a GUI for easier configuration and management of models, and it allows you to store/load models as .gguf something ollama doesn't do (it stores the models across multiple files - and yes, I know you can load a .gguf in ollama but it still makes a copy in its weird format so now I need to either have a duplicate on my drive or delete my original .gguf)

Thanks for the insights. I'm not familiar with .gguf. What's the advantage of that format?

.gguf is the native format of llama.cpp and is widely used for quantized models (models with reduced float accuracy to reduce memory requirements).

llama.cpp is the actual engine running the llms, ollama is a wrapper around it.


> llama.cpp is the actual engine running the llms, ollama is a wrapper around it.

How far did they get with their own inference engine? I seem to recall for the launch of Gemma (or some other model), they also launched their own Golang backend (I think), but never heard anything more about it. I'm guessing they'll always use llama.cpp for anything before that, but did they continue iterating on their own backend and how is it today?


> properties that no natural fabric can offer

like polluting every inch of the Earth with microplastics!


> We have clothes and materials like gortex now that blocks rain and snow no handmade jacket could ever hope to perform at the same level to be lightweight AND dry.

At the cost of massive environmental, animal and human health.


Sure, let's all ditch linux and macOS as well since they're not the most popular...

You wrongly assume that you are left with the SaaS product after paying for it for 2 years. For the one time payment, you will still have the software 2 years and more down the road.

Here's what I said:

> So let's say average subscription time

It could be anything from month to decades depending on the subscription. And the price should be accordingly (risk based)adjusted for the same revenue.


> important webshit to build

hackernews: where a large portion of programmers are considered inferior because of the domain they work in (the domain where hackernews also lives)


It’s more that tired experience has taught that of the various disciplines, web devs are the most likely to have a shaky-at-best understanding of fundamentals, and thus do silly things like assume network calls will never fail, or store everything in JSON blobs and then wonder why their queries are slow.

I’ve also worked with some awesome web devs, to be fair.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: