Way ahead of ya burp
Way ahead of ya burp
I’m very surprised at you getting mass downvoted.
Their current plight goes all the way back to the 70s, where they literally got everything they wanted.
The Shah deposed, check. Carter humiliated and out of office, check. Religious oligarchy / theocracy / Islamic fundamentalism and Khomeini in power, check. Reagan elected, check. The US embarrassed and shamed, check.
Nothing good it seems come out of getting involved in the affairs of the Middle East.
I expect any actual progress in this matter to feature heavily in a forceful response by the Chinese. If you follow geopolitics, China will be effectively hemmed in by Vietnam, Philippines, Taiwan, Korea and Japan. Their Navy, merchant vessels and trade routes will be under significant existential treat. My bet is that this will strengthen their resolve to take Taiwan by force to ensure that shipping lanes remain open. Otherwise, I wouldn’t put it past them to form a formal alliance with Russia and North Korea to secure a northern breakout.
I’m not a lawyer nor geopolitical analyst but I recall that regardless of the actual merits of the claim, China or any country must insist on disputing territorial ownership, so as not to tacitly concede that it does not belong to them. The actual resolution of the dispute might not be as relevant as the mere presence of a dispute itself. Not sure if this is still the right take, happy to be corrected by someone more knowledgeable.
This is classical confirmation bias + Dunning Kruger at work. People like to think they know the facts and are hesitant to admit they might have erroneous information. It’s likely those that sprout misinformation would scroll right past over our discourse and see the next misinformed post and go “AH HA! I was right!”
I had to scroll too damned far down to find this.
#1 - I don’t know, have you tried making VAAPI work on your browsers? Assuming you are using DEs and not running command line servers.
Hey buddy, happy to help! You certainly can, you’ll just have to generate an app password for your Google account, it’s pretty simple and guide here (https://support.google.com/accounts/answer/185833?hl=en) is easy to follow.
A quick note if you haven’t done it before, the app password is generated in place of your actual Google account password. It is intended for single-app use, and bypasses multi-factor authentication on your Google account.
Risky click of the day, but turns out its benign and family-friendly. Thanks for sharing.
80, 443 for HTTP/S, and 587 for a VPN service. Reason being that I travel frequently, and often have to connect through a bunch of different networks, Airport WiFi, mobile roaming, hotel WiFi, etc. and you never know the kinds of network restrictions they impose on their pipes.
80 and 443 is least likely to be dropped, while 587 is a common SMTP port that could make it through most networks.
I’m running all my microservices on a couple of repurposed NUC5i5RYKs, running Ubuntu Server 22.04 (I know I know) and Docker. They’ve been absolutely rock steady thus far, though not quite as overkill as I like all my computers to be. But I got them in 2015 and they’ve held up more than admirably.
I have found my kin here I see.
Greek god names, Mission code names, uncommon colors, famous mountains, depending on the type of devices. I must have a hundred different ones by now.
Thanks for that! Reading through the Lemmy docs gave me some head-scratching moments too. However, I’m more than grateful to the creators and its a monumental undertaking, so I give them a huge deal of credit.
If you have any tips or suggestions on how to host it better on Docker, let me know too, always happy to tweak and improve my setup and learn as I go along.
Cheers, took me a few attempts (gave up a couple of times early on, but came back determined to finish this) to get it up and running. Let me know how it goes and if this works.
+1 for this, I have an active subscription with Bitwarden, for US$10 a year it’s worth many times that in the value and utility it provides me. I considered self-hosting the service but I decided to just stick with the cloud version since they likely have better resilience than my homelab. It’d suck if my home network is down for whatever reason and I need urgent access to my vault without a local copy within reach.
I haven’t had the deployment use case to get into k8s, but it is always something on my bucket list to pick up. I’d try my hand at it when the opportunity arises. There’s not much to go on but some google-fu turned out this guide: https://codeberg.org/jlh/lemmy-k8s, seems to be fairly digestable on first look.
See the Problem Statement section.
Thanks for asking! I think this is more or less an architectural choice, and I was vaguely adhering to the microservice design philosophy. While spinning up duplicate services for each container that requires it has its advantages in terms of isolation and what not, I wanted to:
Hence, all of my docker containers are deduped and reused whenever possible, and follow my own notations and conventions, as well as static and opiniated networking. It has been a really fun journey so far, but I’m also a glutton for punishment and sleep-less nights ;p
As if all that is not depressing on its own, there just a little less than half of the world that believe it’s a hoax. While they’re being cooked alive. And continue to vote for politicians that perpetuate the idea it’s a hoax.