If AI was reliable, maybe. MAYBE. But guess what? It turns out that “advanced autocomplete” does a shitty job of most things, and I bet false positives will be numerous.
If AI was reliable, maybe. MAYBE. But guess what? It turns out that “advanced autocomplete” does a shitty job of most things, and I bet false positives will be numerous.
Lmk if you find out. Maybe something with… lasers?
Why not leave it open? Haha, I’m just finding this thread a month later and would like a shirt…
Hell yeah now Linux and I both will panic in style
Similar structure, yes, but this is the important part:
Swiss foundations and their board of trustees are legally obligated to act in accordance with the purpose for which they were established
So, just like the Louvre museum in Paris and the Luxor casino in Las Vegas have similar structures, pointing this out doesn’t really contribute much to the discussion.
For all I know, OpenAI’s purpose is to create Skynet and kill all humans. But Proton’s is:
Our legally binding purpose is to further the advancement of privacy, freedom, and democracy around the world.
What a time to be alive
I can’t watch. Plz
You ‘pute 64 bits, whaddya get?
Just ‘nother load for your instruction set
Satoshi don’t call me cuz I can’t go
I sold my soul to the crypto bros
Yeah, what the hell? I didn’t watch the video but one time use pads are crypto 101 first day of class kinda thing.
More or less, yes, but they only work in specific, emulated test environments unless you play Apple’s game and get them verified and signed and eventually in the App Store. The latest EU/GDPR stuff might change this a bit, though.
Yeah, I’d assumed it would respect the —metric=false flag when building with docker run, but docker-compose is ostensibly supported and easier to work with. I was able to successfully change other configuration options (such as setting the db to use MySQL instead of the default SQLite) using the docker-compose ‘command’ block, but the metric flag specifically was ignored. It’s entirely possible that this is a bug and not an intentional attempt to hoover up user data. Either way, data collection should be opt-in by default (by law, imo).
I thought I’d give this a shot, but the metrics/data collection flag was turned on by default and when I added a command to my docker-compose to turn them off, it was ignored. Then, I created an account and looked for a way to turn them off in the settings and there was none. You expect people interested in self-hosting OSS to be cool with sending data out of their network every time the server is started, a memo is created, a comment is created, a webhook is dispatched, a resource or a user is created?! Also, the metrics are collected by a 3rd party with their own ToS that could change at any time?
Holy hell, hard pass. I’d rather use a piece of paper.
Been following this for a while! I’m getting one!