Customers should be able to choose where to repair their device, or even be able to repair it themselves. Just because it's an "official" repair shop doesn't mean its the best and the safest. Louis Rossmann has been saying this for years.
923 karma · joined July 6, 2018
Customers should be able to choose where to repair their device, or even be able to repair it themselves. Just because it's an "official" repair shop doesn't mean its the best and the safest. Louis Rossmann has been saying this for years.
She does not support the current Iranian government, and neither do most of the people in Iran, according to her. But publicly expressing disagreement in Iran could have you disappear. That's why people are afraid to protest and speak out.
Regarding sanctions, it's not that hard to find and buy products from Iran. At least in the EU. What happens is neighboring countries import raw material from Iran, then put a label "Made in Pakistan", for example, and sell it. But those who know, can easily find and buy things like Iranian rice and spices.
I have encountered this problem numerous times, now. It really makes me believe that the models do not really understand the topic, even the basics but just try to predict the text.
One recent example was me asking the model to fix my docker-compose file. In it, there's the `network: host` for the `build` part. The model kept assuming that the container would be running with the host network and kept asking me to remove it as a way to fix my issue, even though it wouldn't do anything for the container that is running. Because container runs on `custom_net` network only. The model was obsessed with it and kept telling me to remove it until I explicitly told that it is not, and cannot be the issue.
``` services:
app:
build:
network: host
networks:
custom_net:
...
```Regarding security, it depends on how you set up your containers. If you just run them all with default settings - the root user; and give them all the permissions, then yeah, quite insecure. But if you spend an extra minute and create a new non-root user for each container and restrict the permissions then it's quite secure. There are plenty of docker hardening tutorials.
Regarding ease of setup, it took me a while to learn docker. Setting up first containers took very long time. But now, it's quick and easy. I have templates for the docker compose file and I know how to solve all the common issues.
Regarding ease of management, it's very easy. Most of my containers is setup once and forget. Upgrading an app just requires changing the version in the docker-compose file.
For nearly 50 years theorists believed that if solving a problem takes t steps, it should also need roughly t bits of memory: 100 steps - 100bits. To be exact t/log(t).
Ryan Williams found that any problem solvable in time t needs only about sqrt(t) bits of memory: a 100-step computation could be compressed and solved with something on the order of 10 bits.
I'm very interested in how they've implemented Google Analytics. No external JS is loaded, just 9KB of packed JS embedded implementing a minimal call... and then it is being sent to their own script analytics4.php which acts like MITM. Does anyone know the name of the plugin or package they are using?
The only true private DNS server is the one you own. It should be a recursive DNS server configured with DNS root zone and DNSSEC. So it would first contact one of the root DNS servers (obtained from ICANN), validate the authenticity of the response ensure it is not tampered with using DNSSEC, and then proceed to call the next server in the chain until the query is fully resolved. Such DNS server would bypass all censorships.
Also nice is that more and more root servers already support DoT meaning that the request and response would be encrypted preventing intermediaries like your ISP from seeing the data.
As a last resort, your DNS server can be hosted outside of the country on a server and then you'd connect to it over DoT or DoH.
female + age = male
My guess is it's due to the requirement to comply with EU law about USB-C. But proper USB-C requires active circuitry but manufacturers don't add it to save a few cents.
And then there are a bunch of nuances that don't follow logic. You just need to learn about them. For example, word "you" is always considered informal, a bit intimate and a bit rude in spoken Japanese, it can be used in formal written Japanese.
Because as I understand it, transmitting a signal is the main power drain. If you transmit with less power it would mean a lesser range and lower signal quality. So Apple can't just have their phone transmit a signal with less power...
It took me a very long time to figure out how to configure my docker containers on my home server to have global IPv6 addresses. But I did it, and it taught me a lot about IPv6. I would personally prefer for the internet to be IPv6 only. It would make certain things much easier like firewall rules, IP whitelisting, and no more stupid CGNAT.
I'm also looking into using S3 glacier for my server backups. It appears to be the cheapest option.
The demand for Nvidia GPUs should now go up. Now anyone can run a GPT-like model by themselves. It's a prime time for businesses to start investing and setting up on-prem infra for that. I know some have been avoiding ChatGPT due to legal concerns and sensitive data.
The best way to handle this would be to talk to her and convince her to not use ChatGPT...
It took me some time initially to figure things out and I had to learn some things. But now it's a breeze. Once I had reverse proxy and automatic certificate renewal in place it has been working ever since then without me having to do anything. Adding a new service like Immisch or Jellyfin takes me an hour or less. Which can be quicker, but I adjust every docker compose to my setup and make it more secure. E.g. I create a new non-root user for each service. Basically I have the whole setup figured out; I have notes and checklists for the new services I add. I don't need to figure out things anymore and in 95% of the cases things just work.
Updating existing services takes minutes: just increment the version in the compose file and rebuild.
For my setup, I use macvlan as opposed to the default docker bridge network. So, the `ports: - "8000:5000"` docker compose config is being ignored. Instead, each docker container gets its own unique IP and MAC address I assign to it. It can then use any port it wants. Thanks to this, on my home network, I can access any container I want by IP. And any container can access any other container. I then add some restrictions for security purposes on the host machine using nftables.
For reverse proxy, I use Nginx Proxy Manager which is a simplified GUI around Nginx. I'm slowly moving to just using Nginx.
For the database, I run multiple instances of Postgres and MySQL and I don't see any issues. They take an insignificant amount of resources compared to the applications. If the application is not in use, its database instance is not being used as well.
An MIT-educated neurosurgeon quit his job after realizing surgeries weren’t addressing the root cause of patients’ problems. He observed that the outcome of surgeries would vary greatly: for some it would help, for others a bit and for others, it would not help at all even though he performed them perfectly every time. Some patients even called before the surgery to say that they were okay and no longer needed surgery.
So he started asking patients questions and after 9 years he concluded that patients who got better and healed did the following (at 19:42 in the video): low salt diet; mostly plant-based diet; did things that would cause sweat: exercise, sauna, or living in hot weather; did not smoke; drank little to no alcohol; had good social support: family, friends, etc; slept 8 hours a day; were not stressed or managed to release it back, e.g. meditate.
Then he talks about the moral dilemma. If he helps patients to truly heal by sharing what he has learned, he and the hospital would not make money.