On the flip side, can you imagine being stranded on the ISS, and watching the ship that could have taken you home gone down safely?

Damned if you do, damned if you don’t. They’re holding up amazingly well, I don’t envy the astronauts right now.

Or better yet, let her keep her gmail. Don’t force any lab instability on to others… especially email. One lost important email (even if not your fault) and you’ll never hear the end of it.

You guys have cubicles? I thought we’ve done away with that and mandated all offices to be deprived of walls and dividers since the 2010s in favor of open office floor plans? Someone get the office manager on the line.

Very much as expected… fragmented, incomplete, and highly dependent on carrier. Google’s non standard E2EE extension will likely only work if messages are routed through their servers, which based on the observations here, even from the Android side it doesn’t seems to be routed through Google. Larger file means better quality pictures via green bubbles, anyone who’s sent/received a garbage and cares enough knows to send via third party messaging apps anyway, so nothing life changing here.

Let’s see if Apple applies pressure and push everyone to use Google’s servers for E2EE as they move towards iOS 18, but other than that… I’m still inclined to think the down play during keynote is apt.

Locks can happen by registrar (I.e.: ninjala, cloudflare, namecheap etc.) or registry (I.e.: gen.xyz, identity digital, verisign, etc.).

Typically, registry locks cannot be resolved through your registrar, and the registrant may need to work with the registry to see about resolving the problem. This could be complicated with Whois privacy as you may not be considered the registrant of the domain.

In all cases, most registries do not take domain suspensions lightly, and generally tend to lock only on legal issues. Check your Whois record’s EPP status codes to get hints as to what may be happening.

That’s a drop in the pond in the grand scheme of things. You just out source that out to rights management companies and absolve yourself from that obligation behind safe harbour. This is basically what they’re doing in this department. They’ve built Content ID for digital finger printing, and then invented an entire market for rights management companies on both sides of the equation.

On the other hand, 500 hours of video footage got uploaded to YouTube every minute per YouTube in 2022 (pdf warning). 30 minutes of video game content (compresses better), just the 720p variant using avc1 codec is about 443MB of space. Never mind all the other transcodes or higher bitrates. So say 800MB per hour of 720p content; 500 hours of content per minute means 400GB of disk space requirement, per minute; 500TB of disk space per day.

That’s just video uploaded to YouTube. I don’t even know how much is being watched regularly, but even if we assume at least one view per video, that’s 500TB of bandwidth in and then 500TB of bandwidth out per day.

Good luck scaling that on public budget.

At least from the nerd side of Lemmy, communities pertaining to technology, self-hosting, etc. — which I’d imagine to be the larger drivers due to how complicated it is to join compared to a traditional centralized setup (see also same hurdle for mastodon vs Twitter; which doesn’t gain adoption until Thread and BlueSky started to attract the less technical users), I’m seeing troubling signs of slowing down and shrinking.

If people actually want Lemmy in these areas to grow, it is important to be a lot more inclusive, and understand when to not participate in order to foster better community growth.

What I mean on the inclusive side is those FOSS advocates need to back off with the “You don’t understand FOSS, and go make your own instance” comments so other users don’t just bounce right off and leave after being bored with nothing to interact with.

What I mean by understand when not to participate is literally don’t participate in niche communities that doesn’t apply to you. So many Android users commenting irrelevant anti-Apple sentiments in Apple Enthusiasts community, for example. This is driving away actual users who are interested in discussions.

The charts don’t lie. Lemmy is shrinking, not growing. After getting a new lease on life with 0.19 due to what is essentially clever accounting, the community is still slowing down/shrinking. And for the nerdier side of the userbase, unless the community by and large start to interact more inclusively, the whole thing is sadly going to be just a small blip that’ll soon fizzle out.

Security when you’re on untrusted network. I can trust Google to snoop my banking data and update the spending power info on my ad profile, I can’t trust the random dude in trench coat also using the public wifi when I am traveling out of my roaming coverage.

I joke of course, but the security aspect is still valid.

Security.

Cloudflare handles a very large amount of traffic and sees many different types of attacks (thinks CSRF, injections, etc.). It is unlikely that you or me will be individually targeted, but drive-bys are a thing, and thanks to the amount of traffic they monitor, the WAF will more likely block out anything and patch before I’m able to update my apps on 0 days.

Also, while WAF is a paid feature, other free features, such as free DDOS attack protection, help prevent other attacks.

It’s a trade off, sure; they’re technically MITM’ing your traffic, but frankly, I don’t care. Much like no one cares to target/attack me individually, they aren’t going to look at my content individually.

Additionally, it also makes accessing things much easier. Also, it is much more likely I’d find a SME using Cloudflare than some janky custom self hosted tunnel setup. So from a using homelab as a learning for professional experience point of view, it is much more applicable as well.

Being barefoot could potentially introduce extra risk of contamination from shedding skin cells; this may or may not matter depending on which part of the plant they’re working at. In clean room environments, people usually wear special clothing that prevent cross contamination; these include special coat, hair netting, and extra layer of covering around the shoes. But if the said employee works in the office on administrative tasks, far away from clean areas of production, who cares?

Multiple compose file, each in their own directory for a stack of services. Running Lemmy? It goes to ~/compose_home/lemmy, with binds for image resized and database as folders inside that directory. Running website? It goes to ~/compose_home/example.com, with its static files, api, and database binds all as folders inside that. Etc etc. Use gateway reverse proxy (I prefer Traefik but each to their own) and have each stack join the network to expose only what you’d need.

Back up is easy, snapshot the volume bind (stop any service individually as needed); moving server for specific stack is easy, just move the directory over to a new system (update gateway info if required); upgrading is easy, just upgrade individual stack and off to the races.

Pulling all stacks into a single compose for the system as a whole is nuts. You lose all the flexibility and gain… nothing?

At $80 a pop, might get more oomph from an older optiplex if electricity cost isn’t too big of a concern?