169 karma · joined September 7, 2023
Prompt engineering is an example of this. A clever prompt by a domain expert can prime an LLM interaction to yield better information to the recipient in a way that the recipient themselves could not have produced on their own.
1. https://en.wikipedia.org/wiki/Index_Librorum_Prohibitorum
Any solution that you build is going to be more complicated and less secure than IAM. In IAM, your workload/server can have an identity. The software running on the server is issued temporary credentials as needed, and only has access to resources linked to the role. How do you do this without identity and access management? Roll your own because IAM is too crazy?
If they're not doing that, and their 1 server is talking to AWS resources, it means its using superadmin credentials. If that 1 server is compromised, can you see why that would be a bad idea?
This sticks out to me. IAM isn't crazy, and having access controls in place is going to be the very first thing you want to do when you bring someone else on board. Maybe you're not there yet, but it would be a wise time investment to understand how these work, to the point where they don't feel confusing.
I am anticipating a huge collapse in the OSS ecosystem as the people who drive them say "fuck it" and walk away for more important things.
Edit>> It appears to be the state.
>Artificial womb technology and the significance of birth: why gestatelings are not newborns (or fetuses)[2]
In this abstract[3], she argues that a new classification is needed to determine what can and can't be done with each "entity", because it will impact the freedoms of women. How does a fetus in an artificial womb impact the freedoms of a woman?
1. https://www.durham.ac.uk/staff/elizabeth-c-romanis/#publicat... 2. https://jme.bmj.com/content/45/11/728 3. https://academic.oup.com/medlaw/article/28/1/93/5510054?logi...
Is this an attempt to nullify all existing laws that use the word "fetus"?
>A cloned database view is some representation of your database that has been post-processed to only contain data that the user is allowed to see. This representation would typically be in the form of a separate user-specific sqlite database file. Because the cloned database only contains data that is theirs, a user may issue any query against it, and there is no risk to data security. And if a malicious user was able to issue a DDL statement, it would only affect their cloned database.
Maybe there is a better word than "cloned database view." Replica doesn't feel quite right though.
The author touches on 2 issues that are tangential to this problem, restricting unauthorized data, and mutations, both of which are not really easily solvable with the cloned database solution.
However, the underlying theme of skipping the API is extremely compelling. So much code, both FE and BE, are just to serve as an elaborate interface to the database. Simplifying this will be a huge gain in software maintenance. But the challenge is to do it safely.
1. https://docs.heimdallm.ai/en/main/blog/posts/safe-sql-execut...
Not sure where you live, but where I've lived, they form camps, do drugs in the open, scream at people, and vandalize their surroundings. They make a good environment hostile to everyone. That's what most people are angry about.
But 50% of the 2FA options you listed do not require a mobile device. Security key and TOTP app. TOTP apps are free. Try authy.