pavelmelnichuk

thank god I'm not the only one, pulling my hair out hitting ctrl+z ... Happy Friday I guess

The way we’re handling it is basically to treat provider/cache affinity as part of the routing decision.

On the first request in a conversation, we pick the model/provider based on the request, and then keep that route sticky for the rest of that conversation. So we’re not bouncing a large context between providers every turn and constantly blowing away the cache. If that provider fails and we have to fail over, then yeah, the next provider has to prefill the context again. There’s no real way around that.

If you need to handle a separate task mid-conversation, the cleaner pattern with Smart Groups is to spin up a sub-agent with its own context. That request gets evaluated separately, and then that route stays sticky for that task too.

Also, smart routing is only one part of Relay. You don’t actually need to use dynamic routing at all to get value from the rest of the gateway, but it is a cool offering.

Hey everyone, I'm here to answer questions all day if anyone needs anything or wants to know more about how I trained the classifier, also you can find docs at the website: anchorshell.com

You can create a randomly generated cookie of sorts instead of doing anything with a users' credentials. The supposed accomplished task and end goal would be the same, and yet, people would feel more comfortable.

Your claim that you are using an irreversible hash is not comforting.

Your forced data collection is also not comforting.

The question is where is the line?

Say I have sensitive or proprietary information on my laptop that is in an encrypted drive. Do I have to unlock my laptop, or do I have to unlock each encrypted file itself?

Yes, we process data visually much faster than the ten bits per second example

Your ellipsis suggests to are disagreeing with the original comment, else what you wrote is just a truism. The point of the original comment was that it was authorized by default as intended by design, and thus not a "hack."

Everyone in the west always forgets thats Jews were not the only ones that were victimized by the Nazis, and I feel that this is too often misrepresented from the general knowledge pool of most people in society.

More soviets died there than Jews, and in fact more Non-Jews died there than Jews. Why does everyone ignore that?

Number of Deaths Jews: up to 6 million Soviet civilians: around 7 million Soviet prisoners of war: around 3 million Non-Jewish Polish civilians: around 1.8 million Serb civilians: 312,000 People with disabilities: up to 250,000 Roma (Gypsies): 196,000–220,000 Jehovah's Witnesses: Around 1,900 Repeat criminal offenders: at least 70,000

https://www.ushmm.org/wlc/en/article.php?ModuleId=10008193

> Fat bar at the top ... scroll out of the view as you scroll into content

I think you have been drinking the punch at your lunch. That bar is still a problem and should not be there. There is a native back button, and there is no need for that bar. It lowers conversions for everyone's websites and increases everyones bounce rates.

Of course there is no problem with everything else google has implemented in terms of speeding up the web. That's great. It was a major achievement and a lot of good engineering went in to the caching, rendering, and image resizing and optimization machine that is AMP.

Your meeting should have been about hijacking the ui.

> I did not bring this up because I forgot :)

You punked out [0]

[0] https://www.google.com/webhp?sourceid=chrome-instant&ion=1&e...

This comment has the funny smell of a, "you too," [0] argument fallacy.

[0] https://en.wikipedia.org/wiki/Tu_quoque

What is to stop them from counting your traffic now, if you use aws that is?

nah it's not bad. Sometimes you just need to reinstall the same audio kernels, etc (depending on your hardware). There are many guides to find compatible hardware