If you need a mic for podcasting, go with a USB condenser mic. Decent ones starting at 50 bucks.
The SM58 was a shitty mic when it came out and still is today. It’s popularity comes purely from price and reliability.
No self respecting audio engineer would ever use it to record anything.
Took me a while too. I personally learn a lot in discussions, so it took me a really long time that most people don’t.
They identify with their believes and will never let go, no matter what they hear, unless something else has already shaken their believes.
Some of the plebs think that on twitter there is more discussion to be had, because it’s only bitcoin maxis here. Which of course isn’t true.
Es ist eben keine Esoterik. Denn wenn Geld ein normales Gut wäre, das die doppelte Koinzidenz der Wünsche löst, würden die Leute nicht daraus flüchten, wenn es an Wert verliert, sie würden mehr davon kaufen.
Fällt dir nicht auf, dass sich Geld spiegelbildlich zu allen anderen Gütern verhält?
Das glaube ich dir nicht.
Du willst garantiert keine Einsen und Nullen in der Time Chain besitzen, um sie zu konsumieren oder als Produktionsmittel einzusetzen.
Du erwartest dass Bitcoin deine Kaufkraft in die Zukunft transportiert und evtl potenziert.
The principle is the same. It doesn’t matter whether it’s radio bouncing of the ionosphere or light being refracted by the different areas of air, with more and less water vapor.
The formulas are the same, because both are electromagnetic waves.
#[0] this is by the way not the first paid feature I suggested to you. Damus can be your Ikigai. The world needs it, you love it, you are good at it and at least I will certainly happily pay you for it.
#[1]
A feature suggestion to solve this:
Let us zap vote on features an build only what we pay you enough for.
My job was to build devices that take these into account 🤷
I’m against any non-bug fix updates to core at this point.
Nobody knows if Monero is centralized or how many coins exist. It’s the ultimate “trust me bro” coin.
You can see it, in the photo. But light behaves like an electromagnetic wave. Any CB amateur radio operator can demonstrate to you, how his waves get refracted by the atmosphere and how different wheater conditions will enable him to sometimes communicate with people much farther away than he should be.
If you expose a port in a docker container, it is open on the host.
If the port is eg 80 for a Webserver that’s fine.
If it’s a control port port then that’s asking for trouble.
Many container projects used to open all ports the application uses, for convenience of newbies, so they can just say “docker run container” without any options.
The usual purpose for containers is to be deployed via compose, swarm or Kubernetes, which can open all the ports.
As I mentioned docker can overwrite firewall rules.
I had cases of finding a port open to the internet even though my compose had port specifications that didn’t include it and the port was blocked in ufw.
So the best practice is to never use expose in a Dockerfile, use the deployment to handle the port openings and in general keep as much of the ports closed.
Docker has internal Networking between containers and reverse Proxies are also usually a better option for routing traffic from the web to your container.
Never looked into them deeply. They are more transparent than Umbrel, but they also use the expose command in Dockerfiles.
I am at a point where this is for my use, I will discard it.
So crazy that probably 90% of docker containers have ports exposed by default.
A mystery why you’d do that unless it is a port meant to be open to the internet, which most ports aren’t.
You can always open a port in compose or when running the container, if needed. But just opening all ports to the host is crazy, especially if maybe someone else may use your container.
Not with Umbrel. You’d need to rebuild the docker containers and since 0.5 they redid everything.
There is no documentation and no Dockerfiles that I can find.
You could achieve partial improvements by changing the docker-compose.yml
But if you run a big node in the home, I’d use Rasbibolt and definitely not on a RaspberriePi.
I am currently working on a guide for running a node redundantly on more than one computer.
I got blocked by Darth Bitcoin for pointing this out.
He said „just install ufw” which is important, but since docker overwrites the firewall rules, it is not enough.
You can control Lightning only if you have ssh access (Raspibolt has a guide how to secure ssh access) or via thunderhub, which is pretty secure and has 2FA option as well.
In my Setup I closed all the ports to direct access besides Lightning and that only because currently for a not yet clear to me reason the caddy reverse proxy and LND didn’t play nicely.