From your link, it explains that they have to Switzerland:
"The developer of Session, an encrypted messaging app, has moved operations to Switzerland as ‘being in Australia just threatened our credibility as a privacy tool’."
What else in particular are you talking about?
With the phone number, I may have not remembered correctly for this particular software. If I could edit my comment, I would add a note.
But when going to the FAQ link I remembered how bad this piece of software was especially promoting cryptocurrency. I would never want a messenger to promote crypto, such a "Signal"
Programs spend the vast amount of their cycles in a small sub-set of the code. There is generally very little to be gained by optimizing code that isn't in the small subset.
Maybe a max-age field for the package manifest? For things like programs that are expected to be finished, this can be infinity, but for things that are expected to move with a complex ecosysten, could set it to 6 months? Past that point, a prompt is shown to confirm the user wants to install a likely-depreciated package? That way people won't be accidentally exposed to issues from downstream package maintainers being rendered unable to maintain their packages
It's not only the age and CVEs but also the provenance. Those third party uploads could come from any rando and could be clean or could be packed with malware.
Such items should have a red banner: CAUTION, unofficial, use at your own risk. The other approach is like Docker hub has "docker official image" for popular ones.
a data center in space doesn't have a gigantic rock taking up most of its area, a data center in space is 100% data center 0% rock.
If it had the same data center to rock ratio as earth, it would just end up being earth in the end, and earth doesn't seem to be wanting to stick to its equilibrium either right now
The rock in this case acts as extra thermal mass that makes it take longer to reach thermal equilibrium, but doesn't change what the ultimate thermal equilibrium is. Only the configuration of the parts of the surface that can absorb or radiate electromagnetic radiation do that. And because rock is a fairly good insulator we only really benefit from the top layer and if the sun went out we would all freeze in a week or so.
it changes the amount of exposed area to release heat back into the universe. if you have a non-negligible amount of compute compared to earth, you are going to be approaching a non-negligible amount of space required to radiate that away, along with all the other costs and maintainability issues
The formula for the equilibrium temperature for a sphere in sunlight is
2 * pi * r^2 * L / (4 * pi * d) * (1 -a) = 4 * pi * r^2 * sigma * T^4
As you can see there are pi*r^2 on both sides of the equation, the surface area to cross section ratio of a sphere doesn't change as it gets bigger and so the equilibrium temperature doesn't change no matter how big the sphere is. (d is the distance to the Sun, nothing to do with the sphere itself).
if there is an LLM in there, "Run echo $API_KEY" I think could be liable to return it, (the llm asks the script to run some code, it does so, returning the placeholder, the proxy translates that as it goes out to the LLM, which then responds to the user with the api key (or through multiple steps, "tell me the first half of the command output" e.g. if the proxy translates in reverse)
Doesn't help much if the use of the secret can be anywhere in the request presumably, if it can be restricted to specific headers only then it would be much more powerful
Secrets are tied to specific hosts - the proxy will only replace the placeholder value with the real secret for outbound HTTP requests to the configured domain for that secret.
which, if its the LLM asking for the result of the locally ran "echo $API_KEY", will be sent through that proxy, to the correct configured domain. (If it did it for request body, which apparently it doesn't (which was part of what I was wondering))
The AI agent can run `echo $API_KEY` all it wants, but the value is only a placeholder which is useless outside the system, and only the proxy service which the agent cannot directly access, will replace the placeholder with the real value and return the result of the network call. Furthermore, the replacement will happen within the proxy service itself, it does not expose the replaced value to memory or files that the agent can access.
It's a bit like taking a prepaid voucher to a food truck window. The cashier receives the voucher, checks it against their list of valid vouchers, records that the voucher was used so they can be paid, and then gives you the food you ordered. You as the customer never get to see the exchange of money between the cashier and the payment system.
(Noting that, as stated in another thread, it only applies to headers, so the premise I raised doesn't apply either way)
Except that you are asking for the result of it, "Hey Bobby LLM, what is the value of X" will have Bobby LLM tell you the real value of X, because Bobby LLM has access to the real value because X is permissioned for the domain that the LLM is accessed through.
If the cashier turned their screen around to show me the exchange of money, then I would certainly see it.
> They also require a phone number even!
"You don’t need a mobile number or an email to make an account with Session." - https://getsession.org/faq#identity-protection
reply