urams

Look at some of these "surveillance tools" that they are marketing to "oppressive regimes". Their website brags about these deeply oppressive surveillance features:

- Identifying material threats to your workforce - Integration with Concur and your HRIS

Look at some of the "oppressive regimes" they sell to, such as the evil Amnesty International: https://imgur.com/a/U4Zef3x

Comment · 1 month ago

Your 4D chess model of their thinking is that the risk they run of mentioning a direct competitor, that their potential customers would also be considering, is so great that the value of that comparison is dwarfed by the costs of the risk, so they don't do it. This is some next level strategic thinking.

I have to wonder, though, why doesn't Palantir mention them? https://www.google.com/search?q=site%3Apalantir.com+samdesk

They seem to mention actual competitors: https://www.google.com/search?q=site%3Apalantir.com+c3

Given your 4D chess logic, they really should be mentioning all their competitors to poison their wells.

Comment · 1 month ago

If by "overlapping and very related methods" you mean "use any form of data analysis whatsoever" then, yup, they are basically the same company.

Comment · 1 month ago

Weird that they don't compare themselves to Palantir then!

https://imgur.com/a/eKAQKSN

Comment · 1 month ago

"Palantir-like"

I guess you've chosen to do the editorializing for the writers in lieu of their presence here.

Comment · 1 month ago

> I'm a paid Gemini subscriber via Workspace Standard accounts and yet I also only have access to 3.6.

Same and I have found it extremely annoying. I actually really like the Gemini models for question/answer stuff and reach for it before Claude (the other model family I have purchased) but it's getting long in the tooth at this point and I'm finding my Gemini usage shrinking to nearly 0.

Comment · 2 months ago

  You are right that this is hard from a prompt alone, but for a slightly stranger
  reason than the obvious one. The model never sees columns. It sees tokens, and a
  token can be one character or nine, so "make this line 80 wide" asks it to run a
  hidden tally over pieces it cannot count by looking at them. Any slip early in a
  line compounds, and there is no backspace key to reach for once it is committed.
  That said, the failure is not total. A model can lean on a learned feel for line
  length, pick shorter or longer synonyms to land close to the target, and rewrite
  a sentence when it overshoots. It will not be perfect every time, but it lands a
  lot more often than pure chance would suggest. The sampling trick you mention is
  the real fix: mask each token that would push a line past the limit, and force a
  newline the moment the count hits the mark. That converts a fuzzy instruction to
  a hard constraint with zero training. Fine tuning helps too, but mostly sharpens
  the same internal counter rather than replacing it. This reply is a small proof;
  if any line here is off by one, feel free to consider your point demonstrated...