eriner_

8 ms·

1.
by eriner_ 3y ago
Ah, that's what you're referring to. As I mentioned in a comment on the previous thread (which I now see you commented on two days ago), we didn't want to require phone numbers for verification and went the email-only route i
2.
by eriner_ 3y ago
Can you be specific and less vague? I don't understand what the issue is.
3.
LLM Sandboxing: Lessons Learned(blog.forcesunseen.com)
2 points by eriner_ 3y ago|5 comments
4.
by eriner_ 4y ago
Sorry to hear that, that's our fault I'm sure. (There's a reason many services require non-VOIP phone verification and we didn't want to go that route, this is an unintended consequence). I know you're likely not in
5.
Show HN: Doublespeak.chat, a text-based AI escape game(doublespeak.chat)
8 points by eriner_ 4y ago|4 comments
6.
by eriner_ 4y ago
Even if it reproduces (proportionally) small sections of code it's been trained on verbatim, its function is transformative and will likely be deemed fair use. This lawsuit is going nowhere other than the HN front page.
7.
by eriner_ 4y ago
> On the whole there is a lot of good stuff, but I worry about the ability for it to stay an open standard. Today Google has dominant browser market share with Chrome, so they get to dictate new web standards just by building them into C
8.
GraphQL Security Testing Without a Schema(blog.forcesunseen.com)
2 points by eriner_ 4y ago|0 comments
9.
by eriner_ 4y ago
I use zsh and have the following alias (rather, function): ``` cp () { rsync -avhW --progress --inplace ${@} } ``` If I ever need to use the `cp` binary, I execute `=cp`, which evaluates to `/bin/cp`.
10.
by eriner_ 4y ago
I felt like prepending the domain was a reasonable request so I've added that as a checkbox. Thanks for the feedback! Regarding the versioning, perhaps that could be manual editing of the email? or using a different "v2" salt
11.
Show HN: Blame.email – client-side one-way email generator(blame.email)
8 points by eriner_ 4y ago|7 comments
12.
by eriner_ 4y ago
Correct! This is why I explicitly said the following in the blog post I linked above: > Once the application hits “readiness” status (as determined by health endpoints or the load balancer), the secrets volume should be unmounted and mad
13.
by eriner_ 4y ago
Arbitrary file read vulnerabilities are extremely common.
14.
by eriner_ 4y ago
I agree completely. Storing secrets in environment variables is wrong: https://blog.forcesunseen.com/stop-storing-secrets-in-enviro... Even unsetting environment variables leaves them in /proc/self/environ. T
15.
by eriner_ 4y ago
Sure, value for value. I could form a business entity, open a PO box, create an <insert payment processor here> account, and accept value from those who use the service. People could pay whatever the service is worth to them. Some are
16.
by eriner_ 4y ago
Agreed, running your own node gives you true ownership of your data. Those that can, should. For those that can't, community servers.
17.
by eriner_ 4y ago
I run one of the larger Mastodon servers in the fediverse, and as far as I know the largest non-cloud hosted Mastodon instance. Here's a ten-post thread I wrote about my experiences scaling this self-hosted instance: https:/&#x2F