713 karma · joined June 22, 2023
There's no reason Aristotle or Veratad should see who the underlying requestor is. Yoti should receive the verification request, strip the context, make the request - that's it. The fact that it isn't structured that way and they are tagging on additional metadata suggests per-query economics, which creates a direct incentive to route more verifications through more parties, exactly backwards from data minimization. I'm not going to call it a rev share, but the architecture is consistent with one.
Ran gemma-4-26B-A4B-it-GGUF:Q4_K_M just fine with llama.cpp though. First time in a long time that I have been impressed by a local model. Both speed (~38t/s) and quality are very nice.
Two months later it was CVE after CVE.
All SaaS-built MCP servers should cover the entirety their existing API functionality. I know it sounds like a lot but I really don't think it is an unreasonable expectation.
A fun, brightly colored, relatively inexpensive, Windows-less laptop that you can use for doing your taxes while watching a movie has appeal. The performance isn't that important, so long as it is as responsive as the owner's phone.
Absolutely terrible products to work with both from a user and developer standpoint, but once they are up and running they are built like tanks.
You get the tiling without the config that comes with Hyprland, with the added option of toggling between tiled or floating. Settings are minimal but they are slowly adding more when there is enough demand. IDE-style theming is done at system-level so that applications match.
Another reason they do not allow it is because if something is popular Amazon will make their own private label version.
Completely irresponsible behavior.