milkjug

“Listen, you gotta ease up on all that porn man …”

On StackOverflow: “never mind, figured it out.”

Yo she alright but does she even know how to exit vim

Thank you for sharing this. I learn something new everyday, much appreciated.

#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.

Ah, the ol’ Brainfuck, aka the new PHP of 2034.

Probably done in jest, but this reads like the 100,000,000th “agree?” bullshit post on LinkedIn.

Dude’s training for his spelling bee. Let’s not over_react_.

Only if your bits touch.

Those are I’m charging my laser eyes before she attacks. RIP OP.

Sauce: Have three of these monsters just planning my death and bidding their time.

That’s not the kind of ball-fondling I had in mind.

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.

Real Men™ compile from source!

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.